DigiTool Migration Workflow: Difference between revisions
Jump to navigation
Jump to search
Line 47: | Line 47: | ||
##Copy and paste contents of log into text document and save with the name of the export folder. | ##Copy and paste contents of log into text document and save with the name of the export folder. | ||
##*[YYYYMMDD]-[PartnerCode]-[DescriptiveText].txt | ##*[YYYYMMDD]-[PartnerCode]-[DescriptiveText].txt | ||
##*Save file on Rosetta server at /storage1/operational_shared/migration/migration_logs/dtl_logs | ##*Save file on Rosetta server at /storage1/operational_shared/submissions/migration/migration_logs/dtl_logs | ||
#'''Move DigiTool export to Rosetta server''' | #'''Move DigiTool export to Rosetta server''' | ||
#*/storage1/operational_shared/migration | #*/storage1/operational_shared/submissions/migration[PartnerCode] | ||
#*Be patient, this may take awhile! | #*Be patient, this may take awhile! | ||
#'''Write Migration Note in DigiTool''' | #'''Write Migration Note in DigiTool''' |
Revision as of 21:01, 15 August 2018
Developed by Kevin Powell in 2018 to migrate Center for Jewish History assets from DigiTool to Rosetta.
Requirements
- Mapped Network Drive to at least one of the partners' Rosetta submission folders
- 67.111.179.133
- /storage1/operational_shared/submissions/[PARTNER_CODE]
- Mapped Network Drive to DigiTool server
- 67.111.179.146
- /storage6/bigstreams6/dtl-export
- Access to the Export Digital Entities job in DigiTool for at least 1 admin unit
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
- [PartnerCode]
- AJH01
- ASF01
- LBI01
- YIV01
- YUM01
- [DescriptiveText] can be the 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
- Management → Maintenance → Monitor
- Save Export job log once job is complete
- Search for Job log
- Management → Maintenance → Jobs List
- Job Name = Export Digital Entities
- Admin Unit = Partner whose objects are being exported
- Job Status = Completed
- Management → Maintenance → Jobs List
- Click eye icon under “Action” on the far left
- In the pop up window, choose “Log”
- Click eye icon under “Action” on the far left
- Copy and paste contents of log into text document and save with the name of the export folder.
- [YYYYMMDD]-[PartnerCode]-[DescriptiveText].txt
- Save file on Rosetta server at /storage1/operational_shared/submissions/migration/migration_logs/dtl_logs
- Search for Job log
- Move DigiTool export to Rosetta server
- /storage1/operational_shared/submissions/migration[PartnerCode]
- Be patient, this may take awhile!
- Write Migration Note in DigiTool
- TBD
- Partition C
Processing
- Open Rosetta Deposit Processor
- If the migration deposit DOES NOT require a complex structMap:
- Processor Migration Workflow
- "CSV template"
- Current template version is available for download here.
- "Export Folder"
- /storage1/operational_shared/submissions/migration/[PartnerCode]/[YYYYMMDD]-[PartnerCode]-[DescriptiveText]
- If the migration deposit DOES require a complex structMap:
- Processor Migration Workflow - Complex
- "Export Folder"
- /storage1/operational_shared/submissions/migration/[PartnerCode]/[YYYYMMDD]-[PartnerCode]-[DescriptiveText]