[Import/Export] Stakeholder feedback requested

62 views
Skip to first unread message

Nick Ruest

unread,
Sep 26, 2016, 5:06:17 PM9/26/16
to Esmé Cowles, Benjamin Armintor, Michael Durbin (md5wz), Joshua Westgard, Noh, Youn, Mark Jordan, Michael Giarlo, Jon Stroop, Karen Estlund, Jim Tuttle, Andrew Woods, fedora-c...@googlegroups.com
Hi all,

With the completion of the latest Import/Export sprint which took place
last week at Penn State,we are now in a position to ask our stakeholders
to test and verify the Phase 1 requirements[1]. Specifically, the
Import/Export utility is now capable of round-tripping Fedora resources
from one repository into a second, initially empty repository.
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

Note: There is one bug related to the restoration of pairtree resources
that is currently being worked; FCREPO-2240[2].

Testing and verification of the Import/Export utility requires three
elements:
* The Import/Export utility[3]
* A running Fedora repository (4.6.0 one-click-run download)[4]
* Data in the repository to export then re-import

Instructions on how to use the utility are outlined in the utility
README[5], and the Import and Export Tools Administrator Guide[6].

Although we encourage you to create your own data to test the utility;
you can also use one of the datasets[7] created by the sprint team.

We would like to finalize sign-off on the Phase 1 requirements from
Import/Export stakeholders prior to moving on to Phase 2. It would be
helpful if you completed your testing by Oct 31, 2016. In the course of
your testing, please let us know if their 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[8].

cheers!

-nruest

[1] https://wiki.duraspace.org/display/FF/Design+-+Import+-+Export
[2] https://jira.duraspace.org/browse/FCREPO-2240
[3]
https://github.com/fcrepo4-labs/fcrepo-import-export/releases/download/0.0.1-SNAPSHOT/fcrepo-import-export-0.0.1-SNAPSHOT.jar
[4]
https://github.com/fcrepo4/fcrepo4/releases/download/fcrepo-4.6.0/fcrepo-webapp-4.6.0-jetty-console.jar
[5]
https://github.com/fcrepo4-labs/fcrepo-import-export/blob/master/README.md
[6] https://wiki.duraspace.org/display/FEDORA4x/Import+and+Export+Tools
[7]
https://github.com/fcrepo4-labs/fcrepo-sample-dataset/tree/master/additional_datasets
[8]
https://jira.duraspace.org/issues/?jql=project%20%3D%20FCREPO%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22In%20Review%22%2C%20Received)%20AND%20component%20%3D%20f4-import-export

Nick Ruest

unread,
Oct 24, 2016, 5:53:54 PM10/24/16
to fedora-c...@googlegroups.com, esco...@princeton.edu, ba2...@columbia.edu, md...@virginia.edu, west...@umd.edu, youn...@yale.edu, mic...@psu.edu, jst...@princeton.edu, km...@psu.edu, jim.t...@duke.edu, Andrew Woods
Hi all,

Just a reminder that we have one week left for testing, and to provide
feedback.

cheers!

-nruest
Reply all
Reply to author
Forward
0 new messages