This brief report provides an update on each of the Fedora 4 Upgration Pilot projects.
Table of Contents | ||
---|---|---|
|
Columbia University
The fundamental questions behind the March Academic Commons/Fedora 4 pilot were:
...
- An outline of feature and data requirements for AC3
- A desktop pilot [1], built to migrate a small subset of data into a local Fedora 4
- A fork of Sufia [2] with preliminary implementations of PCDM Works and Files
- A fork of the fedora-migrate tool [3] that allows lookup of description on other Fedora objects
...
- Coordinate with LITO-SYS on deployed Fedora 4 infrastructure
- Implement browse lists
- Reproduce homepage, visual style and branding of AC in pilot
- Integrate May 2015 Sufia work into pilot
- Migrate data
- Resolve the issue of authorship/ownership for non-uni authors and multiple authors in support of user-management of deposited data
National Library of Wales
...
- A Newspaper title called Evening Express which is our largest newspaper with 187,331 objects
- A Journal Title called ‘Wales’ which has a sufficient number of rights issues for testing.
The upgration pilot page [4] is nearly complete, and a mapping for the Newspapers to PCDM [5] has been created.
A meeting will be organized to map born digital objects to PCDM.
...
University of New South Wales
The initial documentation phase of the upgration pilot is now complete. This included:
...
- Testing the use of an external triplestore for Fedora 4
- Coding a migration API that will be used to migrate objects from Fedora 3 to Fedora 4. Currently, the development work has focused on testing ingestion to Fedora 4 using the Fedora 4 API. This includes starting the transaction, creating containers, adding binary files, updating properties and committing the transaction.
- Reviewing the Fedora 3 to Fedora 4 object and datastream property mappings based on feedback
- Further investigating mapping the UNSWorks repository according to the Portland Common Data Model
York University
As the project entered the third month, work shifted to migration work, and we also a welcomed a new developer to the project, Jared Whiklo (University of Manitoba).
The upgration work was focused a couple parts. The first was collaborating with Mike Durbin (University of Virgina) on fcrepo4-labs/migration-utils [6].
migration-utils will support an upgration in this order:
...
The second part that the migration work focused on was data modeling [7]. Specifically, mapping fcrepo3 object properties to fcrepo4 container properties, fcrepo3 datastream properties to fcrepo4 file properties, mapping RELS-EXT properties, and bringing Islandora into compliance with the Portland Common Data Model [8]. This work was shared with the community via a Large Image Solution Pack example object modeled in Fedora 4.
Related to the migration work, was the Audit Service [9] design work. Nick participated in all of the Audit Service design meetings, and led a discussion around PROV and PREMIS ontology usage in the service. On March 30, a code sprint devoted to the Audit Service will begin, and it will be led by Esme Coles. That work is outlined here [10].
The migration work will most likely continue through April.
No Format |
---|
[1] https://github.com/cul/ac3_sufia [2] https://github.com/cul/sufia [3] https://github.com/cul/fedora-migrate [4] https://wiki.duraspace.org/display/FF/Upgration+Pilot+-+NLW [5] https://wiki.duraspace.org/pages/viewpage.action?pageId=68066807 [6] https://github.com/fcrepo4-labs/migration-utils [7] https://github.com/Islandora-Labs/islandora/blob/7.x-2.x/docs/technical-documentation/migration.md [8] https://wiki.duraspace.org/display/FF/Portland+Common+Data+Model [9] https://wiki.duraspace.org/display/FF/Design+-+Audit+Service [10] https://wiki.duraspace.org/display/FF/Audit+Service+Implementation+Proposal |