1 / 16

IASSIST 2006 May 23 - 26 Ann Arbor, MI Ronald C. Jantz Rutgers University Libraries

RU tgers CO mmunity RE pository (RUcore). A FEDORA-based Institutional Repository To Support Multidisciplinary Collections. IASSIST 2006 May 23 - 26 Ann Arbor, MI Ronald C. Jantz Rutgers University Libraries. http://rucore.libraries.rutgers.edu. RUcore Objectives.

ilyssa
Download Presentation

IASSIST 2006 May 23 - 26 Ann Arbor, MI Ronald C. Jantz Rutgers University Libraries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RUtgers COmmunity REpository (RUcore) A FEDORA-based Institutional Repository To Support Multidisciplinary Collections IASSIST 2006 May 23 - 26 Ann Arbor, MI Ronald C. Jantz Rutgers University Libraries May 23 - 26, 2006

  2. http://rucore.libraries.rutgers.edu

  3. RUcore Objectives • To provide seamless, perpetual access to digital collections -- our resources and the resources of others. • To develop a flexible framework of “core” capabilities providing the enabling infrastructure, interoperability, and sustainability. • To create an information architecture which will support multidisciplinary collections. May 23 - 26, 2006

  4. Institutional Repositories • Institutional Repository • “. . . a set of services that a university offers to the members of its community for the management and dissemination of digital materials created by the institution and its community members.” – Clifford Lynch • Types of Materials Deposited in Repositories* • Theses/Dissertations • Pre-prints/post-prints • Digital images • Assets from Special Collections • Technical reports/working papers • Data sets * Lynch, C & Lippincott, J. (2005). Institutional repository deployment in the United States as of early 2005, D-Lib Magazine, 11, (9), available at: http://www.dlib.org/dlib/september05/lynch/09lynch.html May 23 - 26, 2006

  5. Workflow Management System XML RUcore - How it Works User Input RUCORE Portal Metadata and Archival masters NJ Digital Highway E-Journals Dissertations User, Collection, & Preservation Services Fedora Repository Service Digital Object Repository (Fedora) Digital Object Ingest

  6. Information Architecture – The Collection, the Digital Object, and Metadata • In its most general sense, a digital collection is simply a grouping of objects according to some criteria. • Types of digital collections in Rucore • Explicit – A digital collection whose object membership is specified explicitly within the descriptive metadata. • Dynamic – A digital collection of objects which are grouped according to user specified criteria. May 23 - 26, 2006

  7. Grant Project (NJDH) New Jersey Historical Society N2 N1 N3 O1 M1 B1 P2 P1 O1 O2 Roosevelt The Collection Architecture RUCORE Rutgers University Libraries Rutgers University Eagleton Archive E-journals General Collections Special Collections Solid line – explicit membership Dashed line – dynamic membership

  8. The Digital Object • The digital object is the basic unit of management, encapsulating all essential information about the “document” to be disseminated and preserved, including: • Descriptive metadata (based on MODS*), administrative and event-based migration metadata • Byte streams in both presentation and archival formats (non-proprietary, infrastructure independent forms) • Persistent IDs and digital signatures • Software for dynamic behavior * Metadata Object Description Schema May 23 - 26, 2006

  9. Book Object Persistent ID Special Behaviors Metadata Data streams SMAP1 – StrMap (TOC) DJVU1- presentation PDF1 - presentation Administrative XML1 – OCR text ARCH1- Archival master (tiffs of each page) Digital Object Architecture - Examples Opinion Poll Persistent ID Descriptive Special Behaviors Technical Metadata Source Rights Data streams Digital Prov. SMAP1 – StrMap SPSS1- presentation PDF1 – questionnaire ARCH1- Archival master May 23 - 26, 2006

  10. Data in a Multidisciplinary Repository • Data Characteristics: • Born-digital, no corresponding physical artifact • Specialized metadata standards – DDI, FGDC, etc. • Large – gigabytes ranging to terabytes • Life cycle changes – versions, editions, re-purposing, etc. • Many contributors, spread over wide-area network • Users from many different disciplines May 23 - 26, 2006

  11. Workflow Management System XML A Domain Specific Collection within an IR(An Approach for DDI) RUcore Portal (MODS) DDI-based User Input <var name> <catgry> DDI Portal FGDC Portal <catValu> <txt> Collection & Preservation Services Fedora Repository Service Metadata Templates Managed Preserved Digital Object Ingest Fedora Repository

  12. Continuing Directions(for Rutgers University Libraries) • Multidisciplinary Collections • Provide faculty repository services (focus on data) • Mapping to different metadata standards • Institutional Repository • Support Fedora Preservation Services Working Group • Develop a trusted repository – seek certification • Develop partnerships – sharing data and software May 23 - 26, 2006

  13. RUcore Open Source Software AREA Software/Tool/Technology • Portal & user interface PHP/MySql (by RUL) • Journal & Dissertations Open Journal System (PKP) • Search Engine (full text) Amberfish (Etymon Systems) • Workflow Management PHP/MySql (by RUL) • Management Services PHP/MySql (by RUL) • Handles/persistent IDs CNRI Handle server • Digital library framework Fedora • OS/Webserver Unix-Linux/Apache May 23 - 26, 2006

  14. A Trusted Repository • is one “. . .that establishes methodologies for system evaluation that meet community expectations of trustworthiness”* • Capabilities for a Trusted Repository (from Fedora Working Group) • Signature/Checksum creation and validation • Object format validation • Content model validation • Audit trails and versioning • Event logging and alerting for preservation services • Enable Repository static/active states • History service of major repository events • *RLG (2001). Attributes of a Trusted Digital Repository: Meeting the Needs of Research Resources. Mountain View, CA. May 23 - 26, 2006

  15. Handout – URLs(IASSIST 2006) Rutgers University Libraries • Rutgers University Community Repository at http://rucore.libraries.rutgers.edu • The New Jersey Digital Highway (funded by IMLS) at http://www.njdigitalhighway.org • The Eagleton Poll Archive at http://www.scc.rutgers.edu/eagleton/ • RUL published e-journals • “Pragmatic Case Studies in Psychotherapy” at http://pcsp.libraries.rutgers.edu • “Electronic Journal of Boundary Elemetns” at http://ejbe.libraries.rutgers.edu • “Journal of Rutgers University Libraries” at http://jrul.libraries.rutgers.edu Fedora • Fedora - developed by the University of Virginia and Cornell (grant funded by Mellon) at http://www.fedora.info • The Annual Fedora Users’ Conference (June 19-20) at http://www.lib.virginia.edu/digital/fedoraconf/ May 23 - 26, 2006 R. Jantz – IASSIST 2006

More Related