[Dspace-general] Week 3: Good Repository Software

[Dorothea Salo]

Apologies for the lateness. We're finally getting 1.5 in shape to roll
out, and I'm just a little stressed about that.

REPOSITORY MIGRATION

Work is underway to enable wholesale repository migration between
platforms via OAI-ORE. The winning entry in the hackfest at Open
Repositories 2008 nearly managed an entire migration between DSpace
and Fedora.

ONE CHANGE

Asked what the one change would be that would advance DSpace furthest
toward the ideal repository system, these possibilities came up (in
rough rank by interest):

* file versioning
* embargoes
* eliminating the need for server restarts
* authority control
* API to the repository layer
* multiple instances of DSpace run from a single codebase
* componentization of DSpace

EMBARGOES

Bram Luyten shared this video of their DSpace embargo function:
<http://screencast.com/t/hinfBuq3fU> Elliot Metsger shared
<http://wiki.dspace.org/index.php/User:Emetsger:Embargo>, and its FAQ
at <http://maven.mse.jhu.edu/embargo/faq.html>

A more nuanced implementation of OAI-PMH would be helpful to several
chatters. There was general agreement that withdrawn and embargoed
items should not export metadata via OAI-PMH. The ability to have
OAI-PMH only disseminate items designated as "full-text" (or otherwise
complete) was also desired.

Embargoed items should not come up in browses or searches, of course,
nor should they be crawlable by search engines. However, some items
can be halfway-private: metadata can be available (including via
OAI-PMH), but the files should not be downloadable. Access Control
Lists were raised as one potential solution.


Dorothea

-- 
Dorothea Salo dsalo at library.wisc.edu
Digital Repository Librarian AIM: mindsatuw
University of Wisconsin
Rm 218, Memorial Library
(608) 262-5493