1 / 23

DSPACE for Digital Repositories:

One Platform, Two Stories. DSPACE for Digital Repositories:. Once upon a time…. Willamette University. Oregon State University. …there were two libraries…. …with two digital repositories. Academic Commons. ScholarsArchive@OSU. Institutional Repositories: A Definition.

vincentstevens
Download Presentation

DSPACE for Digital Repositories:

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. One Platform, Two Stories DSPACEfor Digital Repositories:

  2. Once upon a time…

  3. Willamette University Oregon State University …there were two libraries…

  4. …with two digital repositories. Academic Commons ScholarsArchive@OSU

  5. Institutional Repositories: A Definition Broadly defined, an Institutional Repository is a service that … • Collects digital content produced by an institution • Provides a variety of access levels to content • Preserves content over time • Supports stable, reliable Web access over time • Enables discovery of content by various audiences • Integrates with other services (external repositories, authoring tools, web sites)

  6. Let’s see… Should we go with XMLUI or JSPUI?

  7. OSUL's First Collections

  8. WU First Collections Moveable Type (1993-2003) Undergraduate theses (currently 1500 and growing)

  9. Technical Considerations • More complex to install and support than some options; easier than others • Easier: CONTENTdm • More complicated: Fedora • Out-of –the-box interface that is modestly customizable and XML user interface that is highly customizable given the right skill set (css, xslt) • Support for a growing number of protocols (OAI-PMH, SWORD, Dublin Core, METS, MODS, SRW/U)

  10. Technical Considerations (continued) • Handle service provides stable URLs that do not change if the resource is renamed or relocated • Monitoring of file integrity, item provenance, repository history • File format registry • Robust authorization system and support for external authentication protocols • Regular software releases (current release 1.5.1, a 2.0 development branch is underway)

  11. Customizations OSU Libraries Customizations Front-end Web Server (2) Application Server (2) Database Server (1)

  12. Linking from Catalog to ScholarsArchive

  13. ETD Template Oregon Explorer Template

  14. Willamette University Customizations Front-end Web Server (1) Application Server (1) Database Server (1)

  15. XMLUI Design LDAP Authorization by employee_type

  16. DSpace Advantages • Submission process that can be customized and used by departments outside the library • Handle server provides stable URL • Fine-grained authorization for item access and collection maintenance roles • Standards-based development and an active international developer community • DSpace Foundation facilitates forward-thinking, collaborative development work • SWORD supports integration with other systems (e.g.: Open Journal Systems e-journal publishing software) • Can be used to archive a wide variety of digital object types • User interface can be used out-of-the-box or customized andshared (e.g.: improved support for image browsing) • Application code can be modified and shared • Commercial support is available if you need it

  17. COAS Home Page ScholarsArchive Community Page

  18. Progress Buttons Verify Screen Ability to Save Submission Ability to Restrict Access

  19. DSpace Disadvantages • Many customizations are not possible without the appropriate technical skills • Relatively complex to install and administer • Native support for image browsing is poor,but the XMLUI can help with this • DSpace 2.0 will introduce moremodularity, but modifying the current code basecan add significant complexity to upgrades • The authorization system is powerful butrelatively difficult to use in its current incarnation • Contracting for hosted DSpace from a vendorsolves support issues but may limit how DSpace is usedat your institution • Not easy to integrate with external tools andWeb sites

  20. No Technical Support • Disconnect Between • Developers and Users • Developers Answer to • Employers/Institutions • Customizations Can • Wreak Havoc

  21. DSpace Statistics

  22. What Excites Us About the Future?

  23. The End Michael Spalti, Head of Library Systems Division Willamette University mspalti@willamette.edu Sue Kunda, Digital Production Librarian Oregon State University sue.kunda@oregonstate.edu

More Related