Fedora Migration Paths and Tools Project Update: October 2020

This is the first in a series of monthly blog posts that will provide updates on the IMLS-funded Fedora Migration Paths and Tools: a Pilot Project. The first phase of the project began in September with kick-off meetings for each pilot partner: the University of Virginia and Whitman College. These meetings established roles and responsibilities for the pilots, goals and deliverables, and timelines to accomplish the work. Following the meetings we established project infrastructure, including publicly-accessible GitHub project boards.

GitHub project board

The project plan for each pilot is available on the wiki: University of Virginia and Whitman College. These plans will be updated as work progresses and goals are met. Relevant project deliverables will be shared publicly as they are completed.

This month, the University of Virginia pilot will focus on working with a sample of their Fedora 3 content to document data models and metadata and make decisions with regard to mappings. An initial test migration will be conducted to determine what changes will need to be made in order to accomplish the complete migration. They are also setting up a new cloud-based Fedora 6.x instance using fcrepo-docker and the newly-created fcrepo-aws-deployer. These tools can be used by others interested in setting up a Fedora instance using Docker and AWS. At the same time, the grant team is working on a validation tool that will compare Fedora 3 data with migrated Fedora 6 data to ensure completeness and integrity of the migration.

The Whitman College team is focused on metadata this month, both in terms of remediation and mapping. Scope, goals, and a timeline for these activities has been established, and deliverables will be shared with the community for feedback as they are completed. The team is also working on a detailed set of functional requirements, which will be used to conduct a gap analysis and prioritize and development efforts that might be needed. This list of functional requirements will be shared once it has been completed.

Stay tuned for future blog posts as we make progress on this project. All relevant resources can be found linked off the project landing page. Please contact David Wilcox with any questions or feedback.