Deconstructing and Reconstructing a Repository – Strategies for Nimble Rebuilding
The University of Cincinnati Libraries has been relying for 5 years on a DSpace institutional repository (http://drc.libraries.uc.edu, now at over 560,000 records, and maintained by OH-Tech and OhioLINK.
We have experienced four migrations from server home (shared infrastructure to the cloud and back again), version of DSpace, and database (from PostGreSQL to Oracle). During the course of those migrations I came to understand DSpace export and import capabilities, how our handles worked, and what we could expect when large amounts of records were physically moved to different disk storage, and databases and collections were exported and imported.
The OhioLINK community determined in January of 2013 that maintaining over thirty institutional instances of DSpace was not sustainable for its future; at the same time the University of Cincinnati Libraries determined that we had larger goals for data management and e-science, for the digital humanities and for our university born-digital records, all of which we hoped a broader repository service could encompass. OhioLINK asked it’s member libraries to migrate content away from the existing DRCs by December 2013. In February and March of 2013 the University of Cincinnati Libraries began to put together a development team and a plan, and began to evaluate our choices for a next generation open source repository. This 24x7 presentation will outline our process for determining the platform and the migration plan for the next generation repository at the University of Cincinnati Libraries.
Attachment | Size |
---|---|
Deconstructing and Reconstructing a Repository.pdf | 130.64 KB |