DigiTool Migration Workflow: Difference between revisions
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
=Processing= | =Processing= | ||
#Open Rosetta Deposit Processor | #Open Rosetta Deposit Processor | ||
#If the migration deposit DOES NOT require a complex structMap: | #If the migration deposit DOES '''NOT''' require a complex structMap: | ||
#*[[DigiTool_Migration#DigiTool_Migration]] | #*[[DigiTool_Migration#DigiTool_Migration | Processor Migration Workflow]] | ||
#If the migration deposit '''DOES''' require a complex structMap: | |||
#*[[DigiTool_Migration#DigiTool_Migration_-_Complex | Processor Migration Workflow - Complex]] | |||
=Rosetta Ingest= | =Rosetta Ingest= | ||
=Quality Assurance (QA)= | =Quality Assurance (QA)= | ||
Revision as of 16:22, 15 August 2018
Developed by Kevin Powell in 2018 to migrate Center for Jewish History assets from DigiTool to Rosetta.
Requirements
- Access to Export Digital Entities job in DigiTool for at least 1 admin unit
- Access to Digital Entities export folder
- /storage6/bigstreams6/dtl-export
- Access to at least one of the partners' Rosetta submission folders
- /storage1/operational_shared/submissions/[PARTNER_CODE]
Export from DigiTool
- Make sure you are connected to the correct Admin Unit
- Start Export Digital Entities Job
- Monitor the Export job
- Save Export job log once job is complete
- Move DigiTool export to Rosetta server
Processing
- Open Rosetta Deposit Processor
- If the migration deposit DOES NOT require a complex structMap:
- If the migration deposit DOES require a complex structMap: