Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Note: this document is still under development; additional sections forthcoming.

Overview

If you are ingesting a collection that currently exists in the DAMS, you are well on your way to repository ingest! 

The DAMS ingest process includes the following steps, some of which will require assistance from the LTDS team:

  1. Preparation of object-level metadata spreadsheet, including filenames and file paths
  2. Preparation of collection-level metadata spreadsheet
  3. File transfer of all needed files, preserving the directory structure recorded in the DAMS file paths
  4. Curate bulk import process

Metadata Preparation

The following DAMS metadata fields are required for ingest into the repository:

  • Desc - Title
  • Desc - Holding Repository
  • Desc - Rights Statement
  • Desc - RightStatement.org Designation (URI)
  • Digital Object - Data Classification
  • Digital Object - Parent Identifier
  • Digital Object - Visibility
  • Desc - Type of Resource
  • Path

Additional DAMS fields are configured for bulk import through our spreadsheet-based ingest process. See the DAMS to Curate mapping for more information.

Reformatting DAMS-Exported Spreadsheets for Curate Ingest

As an initial step for bulk-ingest, you must export your collection’s metadata from the DAMS into a spreadsheet. The exported spreadsheet will require some additional reformatting to become ingest-ready. Note that many of the columns included in the initial DAMS export will not be used in the final ingest. For assistance with exporting or reformatting spreadsheets, contact LTDS or Metadata Services. See this example of a DAMS export which has been reformatted to be Curate-ingest ready.

  1. Make an extra copy of the exported spreadsheet DAMS with all of its data. It is recommended to retain the original DAMS export file in a shared drive location accessible to LTDS (e.g. Box or Onedrive) as well as the reformatted copy.
  2. Ensure that all spreadsheet columns are formatted as text (preventing Excel and other spreadsheet editors from reformatting date values).
  3. Hide or remove extraneous DAMS columns that are unnecessary for import.
    1. Ultimately, only a few columns exported from DAMS will be used by the importer. To make the spreadsheet easier to navigate, it is recommended to hide or delete these unused columns.
    2. See the DAMS to Curate Metadata Mapping document to review which columns are used by the bulk import tool.
  4. Reformat any date fields into Extended Date Time Format (EDTF):
    1. DAMS fields: 
      1. Desc - Date Created 
      2. Desc - Date Published 
      3. Rights - Copyright Date 
      4. Rights - Access Basis - Review Date 
      5. Rights - Digitization Basis - Review Date 
      6. Workflow - Date Digitized
  5. Consolidate the various LCNAF name entries into a new single column. Concatenate the values of the following DAMS fields into a single column, using pipes as delimiters.
    1. New column name: subject_names 
    2. DAMS fields: 
      1. Desc - Subject - Personal Name - LCNAF 
      2. Desc - Subject - Corporate Name - LCNAF 
      3. Desc - Subject - Meeting Name - LCNAF
  6. Concatenate the following DAMS identifier values into a new single column, using pipes as delimiters. Add a prefix to each identifier (e.g. “barcode:”, “dams:”, etc.  to distinguish between different types of local identifiers.
    1. New column name: other_identifiers
    2. DAMS fields: 
      1. Item ID  
      2. Desc - Legacy Identifier
  7. Make sure a value is populated in the Digital Object - Parent Identifier column. This identifier will be used for deduplication in the bulk import process.
  8. Make sure selected DAMS columns’ values are entered as URIs (instead of their equivalent text labels). 
    1. DAMS fields: 
      1. Desc - Type of Resource 
      2. Desc - RightsStatement.org Designation (URI)
  9. Rename the original DAMS column headers to use Curate’s fieldnames as the CSV headers.
    1. See the DAMS to Curate mapping to match DAMS headers to the CSV import headers.
    2. To assist with this process, it may be helpful to create a row beneath the original DAMS header row, add the new Curate field names as headers in the second row, and then delete the original DAMS header row once finished. 
  10. Review the spreadsheet columns again and delete any that will not be needed for import.
  11. Save the modified DAMS export as CSV (UTF-8 encoded).
    1. Upload the Curate-formatted CSV to Box or Onedrive.
    2. Upload the original, unmodified DAMS export CSV to Box or Onedrive.
  • No labels