Your SlideShare is downloading. ×
Biblio to Fedora Commons REST API
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Biblio to Fedora Commons REST API

1,486
views

Published on

This is a brief overview of how we'll use glue Biblio and Fedora Commons together for the Biodiversity Heritage Library. This binds together many pieces of the project and touches on how we'll use …

This is a brief overview of how we'll use glue Biblio and Fedora Commons together for the Biodiversity Heritage Library. This binds together many pieces of the project and touches on how we'll use Fedora Commons as a preservation layer for the corpus of BHL data.

Published in: Technology, Education

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,486
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
16
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Biblio to Fedora Commons REST API Chris Moyers March 30, 2009 CiteBank
  • 2. CiteBank, Biblio, and Fedora Commons
    • CiteBank is using Biblio for presentation layer.
      • Biblio and Drupal provide much in the way of content management.
    • CiteBank is using Fedora Commons is Preservation Layer.
      • In the event of disaster, Fedora will help make sense of massive body of content.
  • 3. Biblio
    • Stores records, (Bibliographic citations) in MySQL.
    • Allows users to attach files to Bibliographic citations. These could be PDFs, images, OCR text, etc.
    • Uploads reside in filesystem. Upload metadata is stored in MySQL.
  • 4. Fedora Commons
    • A Digital Object is a unit of storage in Fedora. A journal article could be a Digital Object, for example. Digital Objects contain Datastreams.
    Digital Object (stored as FOXML files in filesystem) Datastream 1 Datastream 2 Xml metadata URI Datastream n URI …
  • 5. Fedora Commons
    • Stores Digital Object metadata on filesystem as FOXML files.
    • Allows Externally Referenced datastreams, which simply point to files external to Fedora.
    • FOXML provides context for external files referenced within a datastream.
    • Has SOAP API (API-M) which allows programmatic ingestion, modification, and purging of digital objects and datastreams.
  • 6. Distributed Filesystem (DFS)
    • DFS will create redundant data across nodes.
    • Files are not stored on the DFS in a way that relates them. Due to Fedora and Drupal’s different ways of handling files.
    • Drupal files are in one place, and metadata used to bind them together are in another place (MySQL). FOXML files are in yet another place.
    • Consolidate filesystem paths?
    • In event of disaster, change of technology, we need to be able to retain and make sense of data.
  • 7. Why Yet Another REST API?
    • Biblio and Fedora are not integrated.
    • Islandora is a module for Drupal that interfaces with Fedora Commons.
      • Requires user to explicitly add content to Fedora
      • No direct tie-in with Biblio.
      • Adds complexity to Fedora Commons.
    • We need some way to bridge the gap.
  • 8. Goals of REST API
    • Get data from Biblio to Fedora in a fashion that is transparent to the end user.
    • Digital Objects must be self-describing.
    • Keep it as implementation-neutral as possible.
    • Provide some basic logging and recovery from failure.
    • Make something that can be contributed back to the community.
    • Keep it as simple as possible, both to maintain and to implement.
  • 9. Process Overview
  • 10. The REST API
    • Biblio provides the node ID for the citation.
    • The API then performs several steps:
      • Generate Fedora’s PID from the node ID provided by Biblio
      • Determine whether item exists in Fedora, uses SOAP API-M, API-A
      • Create Bibtex file for the citation. This is essentially a duplicate of the record Biblio creates within MySQL.
      • Add/Chg/Del digital object with its datastreams (including the Bibtex file)
      • Perform logging
  • 11. Recovery, Redundancy
    • DFS creates redundant copies of files.
    • Biblio records are replicated as Bibtex records in filesystem, and tied to PDFs, images, etc, with a Fedora Digital Object.
    • FOXML files from Fedora are stored on DFS.
    • Loosely coupled, technology independent, and redundant.
  • 12. Recovery, Redundancy (cont’d)
    • DFS allows for hardware failure. Uses commodity hardware.
    • Data kept in open formats. Not “hostage” to Drupal, Biblio, Fedora.
      • FOXML provides context for resources within datastreams
      • Bibtex datastreams provide comprehensive metadata for items in CiteBank.
      • Images, PDFs, etc, are bound to Bibtex records via FOXML.
    • Other key elements of a DR plan, such as off-site backups, also need to be considered.
  • 13. Future Steps for REST API
    • Contribute code…
      • To Islandora?
      • To Biblio?
      • As a separate Drupal module?

×