With the completion of the third Import/Export sprint we are now in a position to ask our stakeholders to test and verify the Phase 2 requirements.
Specifically, the Import/Export utility is capable of round-tripping Fedora resources from one repository into a second, initially empty repository, or into an existing repository to an empty container, based on the ldp:contains predicate or based on a user-provided membership predicate. It is also capable of exporting and importing BagIt bags based on a default BagIt Profile, or an APTrust BagIt Profile. BagIt tag files are configurable with a user supplied configuration. Therefore, you should be able to create resources in a Fedora repository, export those resources as RDF and Binaries to the filesystem, then re-import them.
This foundational work supports use cases including:
- Migration from one version of Fedora to another
- Persistence of Fedora resources to disk as standard RDF and Binaries for preservation
- Repository and Object-level disaster recovery
- Transfer between Fedora and external preservation systems, such as APTrust
Testing and verification of the Import/Export utility requires three elements:
- The Import/Export utility
- A running Fedora repository (4.7.0 one-click-run download)
- Data in the repository to export then re-import
Instructions on how to use the utility are outlined in the utility README, and the Import and Export Tools Administrator Guide.
Although we encourage you to create your own data to test the utility; you can also use one of the datasets created by the sprint team. If you have questions on how to use these datasets, please do not hesitate to ask.
We would like to finalize sign-off on the Phase 2 requirements from Import/Export stakeholders prior to moving further on additional Phase 2 external systems, and moving on to Phase 3. It would be helpful if you completed your testing by January 31, 2017. Feedback can be provided by creating a child page here using the example template. Andrew Woods has created the first one, which can also be used as a template.
In the course of your testing, please let us know if there are any issues with the documentation or the utility by creating a JIRA ticket with the "Component" field set to "f4-import-export". Existing issues can be found here. If you need help or a hand with creating issues, please do not hesitate to ask.
