DigiTool Migration Workflow: Difference between revisions

From CJH Wiki
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] = Date format. E.g. 20180403
##**[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

  1. Make sure you are connected to the correct Admin Unit
    • DigiTool → Connect To
  2. Start Export Digital Entities Job
    1. Management → Maintenance → Submit New Job
    2. Choose Export Digital Entities from list
    3. Search for collection and/or objects to be migrated
    4. Click Next
    5. 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.
      • Add sequential number to end of folder name if this is the one of multiple exports with the same name
    6. Set Format to “Digital Entities”
    7. Select the “Include Streams” and “Export Related Objects” boxes
    8. Click Next
    9. Click Confirm


  1. Monitor the Export job
  2. Save Export job log once job is complete
  3. Move DigiTool export to Rosetta server

Processing

  1. Open Rosetta Deposit Processor
  2. If the migration deposit DOES NOT require a complex structMap:
  3. If the migration deposit DOES require a complex structMap:

Rosetta Ingest

Quality Assurance (QA)