repository interoperability n.
Skip this Video
Loading SlideShow in 5 Seconds..
Repository Interoperability PowerPoint Presentation
Download Presentation
Repository Interoperability

Loading in 2 Seconds...

play fullscreen
1 / 13

Repository Interoperability - PowerPoint PPT Presentation

  • Uploaded on

Repository Interoperability. Interoperability and Preservation with the Hub and Spoke (HandS). Matt Cordial, Tom Habing, Bill Ingram, Robert Manaster University of Illinois Urbana-Champaign cordial;thabing;wingram2; Key Ideas.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

Repository Interoperability

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Repository Interoperability Interoperability and Preservation with the Hub and Spoke (HandS) Matt Cordial, Tom Habing, Bill Ingram, Robert Manaster University of Illinois Urbana-Champaign cordial;thabing;wingram2;

    2. Key Ideas • Interoperability is useful in its own right, but it is also important for preservation • Out-of-the-box repository interoperability is low • Institutions commonly rely on multiple repositories • Repository support for emerging preservation standards is low • Repositories change over time

    3. The Essentials • Extensible METS profile • Repository specific processing and transformation utilities • Java API for local integration and extensibility • Apache XML Beans • Dissemination/Submission Web-service • RESTful

    4. METS Profiles • Non-prescriptive in regards to structure or file formats • Intended to overlay other profiles which specify case-specific needs (i.e. web captures) • PREMIS • MODS • Must conform to the DLF Aquifer profile • File-format specific technical metadata • MIX, VIDEOMD, AUDIOMD, others as appropriate

    5. Master METS + Snapshots

    6. LRCRUD • Packages usable by a repository’s native ingestion routines • REST Web-Service • Client integrated into processing workflow • DSpace, EPrints, and others in the next year • Specification and API to create service for other repository systems • Similar to SWORD (Simple Web-service Offering Repository Deposit)

    7. Client submits a GET request to LRCRUD service for a specific item • Service calls the native DSpace dissemination routine • Service receives the output from the dissemination, creates a header file, and adds both the header file and the disseminated content to a zip-file • Service returns a zip-file containing the package to the client

    8. Create stub record • Client issues a POST request to LRCRUD specifying “where” to create the record (e.g. communities or collections) if needed • LRCRUD calls the native Fedora creation routine • Fedora supplies LRCRUD with the ID for the newly created record • LRCRUD responds to the client with an HTTP 201 “Created” message and returns the ID in the Location: header • Upload and ingest the item • Client issues a PUT request to LRCRUD to replace the package identified by the URI. The entity body of the request must contain the zip-file containing the package to be ingested. • LRCRUD unpacks the files and calls the native Fedora ingestion routine. • Fedora tells LRCRUD that ingestion was successful • LRCRUD responds to the client with an HTTP 204 “No Content” message indicating that the request was successful.

    9. Other Technologies • Open Archives InitiativeObject Reuse and Exchange •

    10. More Information Open Source Code: LRCRUD Service Specification: METS Profiles: Generic - Web Capture - Java API Documentation (Javadoc): Project Web Site

    11. Questions? Tom Habing