DigiTool Migration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=DigiTool Migration= | =DigiTool Migration= | ||
Used for migrating non-complex objects from DigiTool to Rosetta. | |||
===Requirements=== | ===Requirements=== | ||
:*'''CSV template''' | :*'''CSV template''' | ||
| Line 16: | Line 14: | ||
:*'''Submit''' | :*'''Submit''' | ||
::- The log will provide the path for the deposit folder. This folder can be copied to [ TBD ] for Rosetta | ::- The log will provide the path for the deposit folder. This folder can be copied to [ TBD ] for Rosetta migration. | ||
::- This process extracts the technical and administrative metadata exported by DigiTool and creates Metadata Update files. These files will be used to update the migrated objects' metadata once they're ingested into Rosetta. | ::- This process extracts the technical and administrative metadata exported by DigiTool and creates Metadata Update files. These files will be used to update the migrated objects' metadata once they're ingested into Rosetta. | ||
::- An example of a successful DigiTool Migration process log can be [[Media:Migration log.txt|viewed here]]. | ::- An example of a successful DigiTool Migration process log can be [[Media:Migration log.txt|viewed here]]. | ||
=DigiTool Migration - Complex= | =DigiTool Migration - Complex= | ||
Used for migrating complex objects from DigiTool to Rosetta. | |||
This process takes significantly longer than the other migration workflow. It creates METS files which includes technical, administrative, and structmap metadata. | |||
===Requirements=== | ===Requirements=== | ||
*An export folder from DigiTool that is organized into “digital_entities” and “streams” subfolders. | :*An export folder from DigiTool that is organized into “digital_entities” and “streams” subfolders. | ||
::- This organization is the default structure of DigiTool exports. | |||
===Process=== | ===Process=== | ||
*Supply path to export folder | :*'''Supply path to export folder''' | ||
*Submit | |||
[ | ::[[File:Migration complex.PNG|border]] | ||
:*'''Submit''' | |||
::- The log will provide the path for the deposit folders. These folders can be copied to [ TBD ] for Rosetta migration. | |||
::- An example of a successful DigiTool Migration process log can be [[Media:Migration complex log.txt|viewed here]]. | |||
Latest revision as of 15:24, 15 August 2018
DigiTool Migration
Used for migrating non-complex objects from DigiTool to Rosetta.
Requirements
- CSV template
- - Current template version is available for download here.
- An export folder from DigiTool that is organized into “digital_entities” and “streams” subfolders.
- - This organization is the default structure of DigiTool exports.
Process
- Supply path to CSV template
- Supply path to export folder
- Submit
- - The log will provide the path for the deposit folder. This folder can be copied to [ TBD ] for Rosetta migration.
- - This process extracts the technical and administrative metadata exported by DigiTool and creates Metadata Update files. These files will be used to update the migrated objects' metadata once they're ingested into Rosetta.
- - An example of a successful DigiTool Migration process log can be viewed here.
DigiTool Migration - Complex
Used for migrating complex objects from DigiTool to Rosetta. This process takes significantly longer than the other migration workflow. It creates METS files which includes technical, administrative, and structmap metadata.
Requirements
- An export folder from DigiTool that is organized into “digital_entities” and “streams” subfolders.
- - This organization is the default structure of DigiTool exports.
Process
- Supply path to export folder
- Submit
- - The log will provide the path for the deposit folders. These folders can be copied to [ TBD ] for Rosetta migration.
- - An example of a successful DigiTool Migration process log can be viewed here.