1 / 15

Fedora IR Pilot

Fedora IR Pilot. Digital Services Team Alliance Summer Meeting July 13, 2012. Why explore a pilot?. Virtually all institutions are interested in IR cost containment Almost 90% provide or plan to provide locally-held digitized content Significant majorities are interested in:

onslow
Télécharger la présentation

Fedora IR Pilot

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. Fedora IR Pilot Digital Services Team Alliance Summer Meeting July 13, 2012

  2. Why explore a pilot? • Virtually all institutions are interested in IR cost containment • Almost 90% provide or plan to provide locally-held digitized content • Significant majorities are interested in: • Hosted services • Aggregating content • Collaborative opportunities

  3. Why Fedora/Islandora? • In 2011, DST examined a number of IR options (DSpace, OJS, Eprints, Greenstone, Omeka, CONTENTdm, SimpleDL, BePress, Fedora/Islandora, Fedora/Hydra, IRPlus, Zentity, LASR) • Fedora had most flexible back end which would serve the greatest number of use cases • Islandora was the only viable front end for Fedora. Hydra is way too nascent and Fez is obsolete • Easy migration path

  4. Built in features • Institution specific branding • Browse and search functionality with facets that allow users to drill into topics • Easily harvested by Google • Make resources visible in WorldCat Local via OAI-PMH • Handles specialized content types • Thumbnails for images and documents • Zoom functionality provided for images

  5. Why partner with Colorado? • Setting up and maintaining Islandora is nontrivial • Colorado has expertise and the ability to support a production installation • Lack of depth of Fedora/Islandora knowledge in the Alliance

  6. Goals of pilot • Test the technology • Determine appropriate workflows • Develop migration strategy from other platforms • Model recurring fixed and overhead costs as well as staff time

  7. First the good news

  8. Goals of pilot Test the technology Determine appropriate workflows Develop migration strategy from other platforms Model recurring fixed and overhead costs as well as staff time

  9. But there were challenges

  10. Challenges Not enough institutions ready to move now to be financially viable Shared ILS initiative absorbs much energyTransitions in Digital Services Program and technical issues create support and functionality issue

  11. Recommendations Wait for the time being If we enter into a contract for a vendor on the Shared ILS initiative that offers a credible IR solution, explore the viability of that option before taking further action Those specifically interested in Islandora should monitor the UO/OSU joint project

  12. Questions?

More Related