DigiTool Migration Workflow: Difference between revisions
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
##Set the Export directory | ##Set the Export directory | ||
##*'''[YYYYMMDD]-[PartnerCode]-[DescriptiveText]''' | ##*'''[YYYYMMDD]-[PartnerCode]-[DescriptiveText]''' | ||
##**[YYYYMMDD] | ##**[YYYYMMDD] is the date format. | ||
##***E.g. 20180403 | |||
##**Partner Codes | ##**Partner Codes | ||
##***AJH01 | ##***AJH01 |
Revision as of 16:39, 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
- Choose Export Digital Entities from list
- Search for collection and/or objects to be migrated
- Click Next
- Set the Export directory
- [YYYYMMDD]-[PartnerCode]-[DescriptiveText]
- [YYYYMMDD] is the date format.
- E.g. 20180403
- Partner Codes
- AJH01
- ASF01
- LBI01
- YIV01
- YUM01
- [DescriptiveText] can be call number, name of collection, a simple description, etc.
- [YYYYMMDD] is the date format.
- Add sequential number to end of folder name if this is the one of multiple exports with the same name
- [YYYYMMDD]-[PartnerCode]-[DescriptiveText]
- Set Format to “Digital Entities”
- Select the “Include Streams” and “Export Related Objects” boxes
- Click Next
- Click Confirm
- 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: