Fedora, Drupal, and Cloud Computing for a Low-Cost, Sustainable DAM Ari Davidow [email_address]
10 years+ of  audio and video oral histories 6TB Data
 
 
 
What if there  is a disaster?
<ul><li>Optical Media  </li></ul><ul><li>are not a preservation format </li></ul>Optical Media
How to get there? <ul><li>Jungle Disk - $20 / www.jungledisk.com </li></ul>
Digital Asset Mgmt <ul><li>Phase One </li></ul>
<ul><li>Open Source vs. Proprietary vs. DIY </li></ul><ul><li>All have advantages: </li></ul><ul><li>You need to consider ...
 
Admin Entryway to JWA’s WWII online Collection Project, based in Drupal
Administering a media object in Drupal. You will see similar metadata being gathered in our Fedora implementation
Control panel for Amazon Web Services
 
Agile Development
Agile Development <ul><li>Put usable tools in people’s hands quickly </li></ul><ul><li>Short, iterative programming cycles...
Issue Tracking www.redmine.org
Code Delivery <ul><li>Our current “let there be no ambiguity” method: </li></ul><ul><li>Finished code must be checked into...
Contents of a typical Oral History
Editing metadata for typical Oral History in our Fedora Repository
Repository Entryway
Next Projects <ul><li>OAI-ORE “media-show” tool </li></ul><ul><li>Integrate Oral Histories with existing exhibits as they ...
Upcoming SlideShare
Loading in …5
×

Ari Davidow, Fedora, Drupal, and Cloud Computing for a low-cost, sustainable DAM

2,652 views

Published on

A paper from Museums and the Web 2009
Digital asset management and digital preservation can require expensive, proprietary software and expensive servers. For a small, underfunded institution like the Jewish Women’s Archive, the answer lies in using open source technology, leveraging what we can do by collaborating extensively, supplemented by relatively inexpensive cloud computer services that let us explore and take chances without tying down our resources on expensive hardware.

The most important ingredient is probably Agile development – doing large scale development by biting off small chunks of useful development at a time, learning from what you have done, and then planning the next chunk of work, funded as you can. In this project we approached long-term Digital Asset Management by accomplishing just enough work with Fedora so that our most urgent assets could be ingested and managed. At the same time we directed development in Drupal, an open source content management system. so that as we develop our public web “face” we are also developing the common ways of working with data and displaying digital objects. Soon, Drupal, an excellent CMS which has no particular digital asset management affordances will be ready to serve as the front end to Fedora, an excellent Digital Repository Framework with enviable digital asset management hooks, but no interface of which to speak.

This paper also serves as a call to other interested archives to collaborate with us in future development.

Session: Technology Strategies [Technology]

Published in: Technology

Ari Davidow, Fedora, Drupal, and Cloud Computing for a low-cost, sustainable DAM

  1. 1. Fedora, Drupal, and Cloud Computing for a Low-Cost, Sustainable DAM Ari Davidow [email_address]
  2. 2. 10 years+ of audio and video oral histories 6TB Data
  3. 6. What if there is a disaster?
  4. 7. <ul><li>Optical Media </li></ul><ul><li>are not a preservation format </li></ul>Optical Media
  5. 8. How to get there? <ul><li>Jungle Disk - $20 / www.jungledisk.com </li></ul>
  6. 9. Digital Asset Mgmt <ul><li>Phase One </li></ul>
  7. 10. <ul><li>Open Source vs. Proprietary vs. DIY </li></ul><ul><li>All have advantages: </li></ul><ul><li>You need to consider your resources, </li></ul><ul><li>where you want to put them, </li></ul><ul><li>where your successor will wish you had put them </li></ul><ul><li>TANSTAAFL </li></ul><ul><li>(There Ain’t No Such Thing As A Free Lunch) </li></ul>
  8. 12. Admin Entryway to JWA’s WWII online Collection Project, based in Drupal
  9. 13. Administering a media object in Drupal. You will see similar metadata being gathered in our Fedora implementation
  10. 14. Control panel for Amazon Web Services
  11. 16. Agile Development
  12. 17. Agile Development <ul><li>Put usable tools in people’s hands quickly </li></ul><ul><li>Short, iterative programming cycles (usually, 4-6 weeks) </li></ul><ul><li>Use cards/whiteboard to note requests </li></ul><ul><li>When you have an acceptable set of cards that can be done in 4-6 weeks, you have your next cycle planned </li></ul>
  13. 18. Issue Tracking www.redmine.org
  14. 19. Code Delivery <ul><li>Our current “let there be no ambiguity” method: </li></ul><ul><li>Finished code must be checked into a repository </li></ul><ul><li>It must be documented in a wiki or other online doc tool </li></ul><ul><li>We must be able to check out the code, follow installation instructions, and successfully integrate/launch/run the application </li></ul>
  15. 20. Contents of a typical Oral History
  16. 21. Editing metadata for typical Oral History in our Fedora Repository
  17. 22. Repository Entryway
  18. 23. Next Projects <ul><li>OAI-ORE “media-show” tool </li></ul><ul><li>Integrate Oral Histories with existing exhibits as they are pulled into Drupal </li></ul><ul><li>UPEI Drupal module </li></ul><ul><li>Focus on search: Lucene/SOLR is cool, but we will have to do much to make it “ours” </li></ul><ul><li>DuraSpace? </li></ul><ul><li>Small Archives Fedora SIG – BOF breakfast on Friday </li></ul>

×