We're a small archive using DSpace to manage electronic records, currently planning an upgrade of our XMLUI DSpace instance. Our existing instance is accessible to the public web, but as part of this upgrade, we want to set up an internal, staff-only dark archive as well. The goal, for ease of use, would be to have the dark archive contain our entire collection, with the public instance containing the subset of items that we want to expose to the public web.
I'm considering setting up two DSpace instances: an internal (primary) instance restricted to a set of local IPs and an external (secondary) instance accessible to the public web. The primary instance would be where all manual staff interaction with the collections takes place. Items would be submitted and approved on the primary instance, and collections designated as public would be harvested at intervals by the secondary. (We'd migrate our existing data over to the primary instance.) This seems like a use case for the OAI-ORE harvester. Does this seem like the appropriate solution for what we'd like to do? Are any institutions currently doing something like this? Thanks -- Nicholas Webb Digital Archivist Icahn School of Medicine at Mount Sinai Box 1102 - One Gustave L. Levy Place New York, NY 10029-6574 (o) 212-241-7239 (f) 212-241-7864 (e) [email protected] ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
