Abstract
Indiana 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.
Highlights
When faced with the need to update digital repository software, the technical details of moving data from one system to another can be identified and outlined
For this case report, what began as a need to move from version 3 of the Fedora digital repository to Fedora 4 at Indiana University (IU) became an endeavor addressing collection management systems, online access services, legacy boutique sites associated with grant projects, and current community development efforts involving the Samvera software stack
Indiana University (IU) was an early adopter of the Fedora repository, serving in 2003 as one of the initial implementation partners on the project led by the University of Virginia and Cornell University
Summary
When faced with the need to update digital repository software, the technical details of moving data from one system to another can be identified and outlined. The entire ecosystem of digital collections must be considered in order to adjust for migrating to a new repository For this case report, what began as a need to move from version 3 of the Fedora digital repository to Fedora 4 at Indiana University (IU) became an endeavor addressing collection management systems, online access services, legacy boutique sites associated with grant projects, and current community development efforts involving the Samvera software stack. Publications 2019, 7, 16 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 This knowledge could be useful for repository developers looking for ways to ease the migration path, and repository managers and librarians aiming for a better understanding of what it means to migrate and what sorts of decisions are required
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
