DigiTool Migration Workflow: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 11: | Line 11: | ||
===Export from DigiTool=== | ===Export from DigiTool=== | ||
#Make sure you are connected to the correct Admin Unit | #'''Make sure you are connected to the correct Admin Unit''' | ||
#Start Export Digital Entities Job | #*DigiTool → Connect To | ||
#'''Start Export Digital Entities Job''' | |||
##Management → Maintenance → Submit New Job | |||
<ol style="list-style-type:lower-alpha"> | |||
<li>About the author</li> | |||
<li>Foreword to the first edition</li> | |||
<li>Foreword to the second edition</li> | |||
</ol> | |||
#Monitor the Export job | #Monitor the Export job | ||
#Save Export job log once job is complete | #Save Export job log once job is complete | ||
Revision as of 16:31, 15 August 2018
Developed by Kevin Powell in 2018 to migrate Center for Jewish History assets from DigiTool to Rosetta.
Workflow
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
- DigiTool → Connect To
- Start Export Digital Entities Job
- Management → Maintenance → Submit New Job
- About the author
- Foreword to the first edition
- Foreword to the second edition
- 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: