Guest welcome to the WA National Digital Newspaper Program Wiki

Washington State Library
Processors
Back
Digital object repository software

Modified on 2011/01/24 11:10 by lrobinson Categorized as Grant admin
{toc}
{| border="1px"
|+ '''Digital Object Repository Software Quick Comparison'''
| ''' '''
| '''open source'''
| '''GUI (admin, ingest, export, and editing)'''
| '''Windows OS'''
| '''parse METS'''
| '''batch uploads'''
| '''formats supported'''
| '''harvest capability'''
|-
| Greenstone || yes || yes, yes, yes, yes || yes || sort of ||  ||  ||     
|-
| ContentDM  || no  || yes, sort of, yes, yes || yes  || no ||  ||   ||  OAI-PMH
|-
| Fedora Commons || yes || yes, sort of, yes, sort of || yes || sort of ||   ||  ||  OAI-PMH
|-
| DSpace || yes ||    || yes ||  ||  ||   ||  
|- 
|}

==Greenstone==

* website: [http://www.greenstone.org/]

* spec sheet

* [http://www.netlibrary.com.offcampus.lib.washington.edu/Reader/|How to build a digital collection] Most irritating ebook ever, available through UW Libraries. It is basically the how-to manual for greenstone.
I failed to find much substance here.

* [http://www.greenstone.org/manuals/gsdl2/en/html/Chapter_understanding_the_collection-building_process.htm#Section_import_and_build_processes| Greenstone developer's handbook, chapter on import and build processes]

===News, reviews, and articles about Greenstone===
# [http://researchcommons.waikato.ac.nz/handle/10289/1331|Bainbridge, D., Osborn, W., Witten, I.H. & Nichols, D.M. (2006). Extending Greenstone for Institutional Repositories. In Digital Libraries: Achievements, Challenges and Opportunities, 9th International Conference on Asian Digital Libraries, ICADL 2006, Kyoto, Japan, November 27-30, 2006(pp. 303-312). Berlin: Springer.] Abstract: 	We examine the problem of designing a generalized system for building institutional repositories. Widely used schemes such as DSpace are tailored to a particular set of requirements: fixed metadata set; standard view when searching and browsing; pre-determined sequence for depositing items; built-in workflow for vetting new items. In contrast, Fedora builds in flexibility: institutional repositories are just one possible instantiation—however generality incurs a high overhead and uptake has been sluggish. This paper shows how existing components of the Greenstone software can be repurposed to provide a generalized institutional repository that falls between these extremes.

{top}

==CONTENTdm==

* website: [http://www.contentdm.org/]

* spec sheet:

===News, reviews, and articles about CONTENTdm===
# [http://blog.infomancy.net/labels/CONTENTdm.html|Infomancy.net] An interesting blog from a digital librarian POV about CONTENTdm. He makes it sound like CDM is far from straight forward and user-friendly.
# [#1|Reese and Banerjee, 2008] p. 60-69: CONTENTdm was designed to provided access to static images. It assumes that a librarian will be managing the collection and staff commitment to managing metadata is assumed. CONTENTdm allows for more granular control than DSpace. As of 2008 DSpace was not recommended by authors for management of serials (managing resources based on publication patterns). CONTENTdm has OCR and may be reasonably well suited for scanned books, newspapers, etc.
{top}
# [http://uwashington.worldcat.org/oclc/439186328|Arlitsch, K., & Jonsson, J. (2005). Aggregating distributed digital collections in the Mountain West Digital Library with the CONTENTdmTM multi-site server. Library Hi Tech. 23 (2), 220-232. ]

==Fedora Commons==

* website: [http://www.fedora-commons.org/]
* [http://duraspace.org/images/specsheet_Fedora.jpg|spec sheet]
* [http://www.fedora-commons.org/about/features|Features] 
* [http://www.fedora-commons.org/confluence/display/FCR30/Batch+Processing| Batch processing page]
** [http://uwashington.worldcat.org/oclc/450986755|Bainbridge, D. W., Ian H. (2009). A fedora librarian interface. ] A clearly-written article about using the Fedora Librarian Interface with Fedora. It is basically the Greenstone interface. Examples of ingest processes are described. Plug-in emphasized. Demonstrates how this interface is supposed to make it easier to ingest things for a less-technically inclined person.

===Capcity===
   "Store all types of content and its metadata," " Digital content of any type can be managed and maintained," Metadata about content in any format can be managed and maintained," "Scale to millions of objects," 

===Interface/ease of use===
"Metadata about content in any format can be managed and maintained"
"Web-based Administrator GUI (low-level object editing)"

===Access to contect===
 "Access data via Web APIs (REST/SOAP)," "Provide RDF search (SPARQL)"
 "Content Model Architecture (define "types" of objects by their content)"
" GSearch (fulltext) Search Service"
  "Multiple, customer driven front-ends."

===Security/stability issues===
      
"Rebuilder Utility (for disaster recovery and data migration),"
 "The entire repository can be rebuilt from the digital object and content files."
  " [http://en.wikipedia.org/wiki/Java_Message_Service|JMS messaging] (your apps can "listen" to repository events)"  

      "[http://www.openarchives.org/|OAI-PMH] Provider Service"
    

===News, reviews, and articles about Fedora Commons===
# [http://www.moore.org/newsitem.aspx?id=2172| Moore Foundation funding, 2007]
# [http://smartech.gatech.edu/handle/1853/28076| Discussion of DSpace/Fedora merger, 2009]
# From [#1|Reese and Banerjee, 2008], p. 60: Fedora's advantages are that it is very flexible (Fedora may interact with any application that can interact with SOAP messages), it is OAI compliant and can act as a "meta repository" that provides access to content maintained by others. It's disadvantage is that it requires technical knowledge to operate effectively; authors recommend this system only if content is complex.

{top}

==DSpace==

* website:[http://www.dspace.org/]
* [http://duraspace.org/images/specsheet_DSpace.jpg|spec sheet]

===News, Reviews and articles about DSpace===
# [#1|Reese and Banerjee, 2008], 60-69. Authors point out that DSpace was conceived of as a way for researchers to self-publish and manage their articles. This system is designed so that contributors are largely responsible for the content and organization of information in DSpace, and that the system is designed to support research papers and data more than images, video, etc. Also, as of 2008 DSpace was not well suited for managing serials.

==General works about Digital Repositories==

# [anchor|#1][http://www.informaworld.com/openurl?genre=issue&issn=0163-9374&volume=47&issue=3|Cataloging & Classification Quarterly, Volume 47 Issue 3 & 4 2009, Special issue on Metadata and Open Access Repositories] 
# [anchor|#2] [http://uwashington.worldcat.org/oclc/145732819|Reese, T., & Banerjee, K. (2008). Building digital libraries: A how-to-do-it manual. New York: Neal-Schuman.]
# [anchor|#3] [http://uwashington.worldcat.org/oclc/52886797|Rhyno, A. (2003). Using open source systems for digital libraries. Westport, Conn: Libraries Unlimited.]
{top}
# [anchor|#4] [http://archivemati.ca/2006/11/27/does-my-digital-archives-need-a-digital-repository-system/|archivemati.ca] Blog post on digital repository software from the archives perspective. Emphasized the actions and processes that surround the system rather than the software itself: "Their research project then shifted focus to produce an excellent set of Ingest and Maintain (storage) guidelines. In other words, it moved from the concept of a digital archives as a software application to the OAIS concept of an archival information system as a “an organization of people and systems that has accepted the responsibility to preserve information and make it available for a designated community.”"
ScrewTurn Wiki version 3.0.1.400. Some of the icons created by FamFamFam.
Guest welcome to the WA National Digital Newspaper Program Wiki

Home¶

Search NDNP Wiki:¶

Browse¶

Links¶

Digital object repository software
