Because I have been on the team doing the SIL.org redesign, I have been looking at the Open Source landscape looking at what is available to connect Drupal with DSpace data stores. We are planning on making DSpace the back-end repository, with another CMS running the presentation and interactive layers. I found a module which parses DSpace's XML feeds in development. However, this is not the only thing that I am looking at. I am also looking at how we might deploy Omeka. Presenting the entire contents of a Digital Language and Culture Archive, and citations for their physical contents is no small task. In addition to past content there is also future content. That is to say archiving is also not devoid of publishing - so there is also the PKP project [sic redundant]. (SIL also currently has a publishing house, whose content need CSV or version control and editorial workflows, which interact with archiving and presentation functions.)
Wally Grotophorst has a really good reflection on Omeaka and DSpace, I am not sure that it is current but it does present the problem space quite well.[ref 1] Tom Scheinfeldt at Omeka also has a nice write up on why Omeka exists, titled "Omeka and It's peers". It is really important to understand Omeka's place in the eco system of content delivery to content consumers by qualified site administrators.[ref 2]
Dspace Mailing list discussion discussing some DSpace technologies for mixing with OAI-ORE and Fedora, Omeka, and Drupal.
- Wally Grotophorst. 4 March 2008. DSpace And Omeka. iNODE: The weblog of Digital Programs and Systems at George Mason University Libraries. http://timesync.gmu.edu/wordpress/?p=485 . [Accessed: 26 November 2011] [Link] ↩
- Tom Scheinfeldt. 21 September 2010. Omeka and It's peers. http://omeka.org/blog/2010/09/21/omeka-and-peers/ [Accessed: 26 November 2011] [Link] [Also Posted on Tom's Blog] ↩
- @Mire. 20 May 2010. What DSpace could learn from Omeka. http://www.facebook.com/notes/mire/what-dspace-could-learn-from-omeka/393758568767 . [Accessed: 26 November 2011] [Link] ↩