SOW: Content Migration Assistance

[jillpe]

Summary

SOW

SoftServ will provide migration assistance and monitor a planned data import into Hyku Commons. The import will consist of approximately 25,000 items containing 200GB of files. To prepare for SoftServ’s involvement in the process, Pitt will extract XML files from Eprints and process the data into a CSV format consistent with Hyku for Consortia’s documentation. After validating test sample imports for a preliminary data check, CSV and files will be handed off to SoftServ for import into a production tenant. The hand-off will consist of at least two deliveries, one with the state of the repository at the time of the start of the migration, and subsequent with the newly added repository items since the start of the migration.
SoftServ will initiate imports in large but manageable batches. Our team will handle errors, and communication with Pitt as necessary should they require assistance with errors or data updates for a successful import.
Incoming work is compatible with existing Hyku Commons work types and Bulkrax configurations. Aside from the separate Embargo work scoped #1006, the addition of metadata fields to the application is out of scope for this work.
The estimated time to complete this migration is 12 to 24 weeks, depending on the relative ease or complexity of the import and related errors.

Acceptance Criteria

• The 25,000 items have been migrated into Hyku Commons through a CSV format via Bulkrax

NOTE

❌ Blocked until Pals is on Valkyrie

[kirkkwang]

one with the state of the repository at the time of the start of the migration, and subsequent with the newly added repository items since the start of the migration.

@ndroark, we can use some clarification on this, how do we deliver the state of the repository before/after

[ndroark]

I'm not sure what is envisioned. @ctgraham, can you clarify?

[ctgraham]

Hi, @kirkkwang . We will share an export of the entire legacy repository at the start of the project, but the legacy repository will remain online for new submissions during the migration. Toward the close of the migration, we will share an export of just the newly added records from the legacy repository.