The Ecosystem of Repository Migration

dc.contributor.authorHardesty, Juliet Louise
dc.contributor.authorHomenda, Nicholas Mark
dc.date.accessioned2025-02-20T15:49:19Z
dc.date.available2025-02-20T15:49:19Z
dc.date.issued2019-03-05
dc.description.abstractIndiana University was an early adopter of the Fedora repository, developing it as a home for heterogeneous digital library content from a variety of collections with unique content models. After joining the Hydra Project, now known as Samvera, in 2012, development progressed on a variety of applications that formed the foundation for digital library services using the Fedora 4 repository. These experiences have shaped migration planning to move from Fedora 3 to Fedora 4 for this large and inclusive set of digital content. Moving to Fedora 4 is not just a repository change; it is an ecosystem shift. End user interfaces for access, management systems for collection managers, and data structures are all impacted. This article shares what Indiana University has learned about migrating to Fedora 4 to help others work through their own migration considerations. This article is also meant to inspire the Fedora repository development community to offer ways to further ease migration work, sustaining Fedora users moving forward, and inviting new Fedora users to try the software and become involved in the community.
dc.identifier.citationHardesty, Juliet Louise, and Homenda, Nicholas Mark. "The Ecosystem of Repository Migration." Publications, vol. 7, 1, no. Selected Papers from Open Repositories 2018, 2019-03-05, https://doi.org/10.3390/publications7010016.
dc.identifier.issn2304-6775
dc.identifier.otherBRITE 5488
dc.identifier.urihttps://hdl.handle.net/2022/31614
dc.language.isoen
dc.relation.isversionofhttps://doi.org/10.3390/publications7010016
dc.relation.isversionofhttps://www.mdpi.com/2304-6775/7/1/16/pdf
dc.relation.journalPublications
dc.rightsThis work may be protected by copyright unless otherwise stated.
dc.titleThe Ecosystem of Repository Migration

Files

Can’t use the file because of accessibility barriers? Contact us