Versions Compared

Old Version 30

changes.mady.by.user MM Hanke

Saved on

compared with

New Version 31

changes.mady.by.user MM Hanke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Place all media files directly into the batch job folder. Add a corresponding MODS XML file per media file. Each MODS XML documents MUST be named with a filename matching the corresponding media file object, followed by the suffix _METADATA (and the file name extension .xml):

  1. <filename>.tif
  2. <filename>_METADATA.xml

The DAMS will create one DAMS asset per media file, guessing the content model based on the file name extension. The media file will be stored as the asset's OBJ datastream, the corresponding MODS XML document will be stored as the asset's MODS datastream.

Option 3 - Media file objects and common metadata MODS XML file

Place all media files directly into the batch job folder. Add one MODS XML document named common_METADATA.xml containing common metadata that will be used for all assets created from this batch.

The DAMS will create one DAMS asset per media file, guessing the content model based on the file name extension. The media file will be stored as the asset's OBJ datastream, and each asset will store a copy of the common metadata MODS XML document in its MODS datastream.

Option 4 - XML only (create placeholder assets)

...

  • The <filename> portion CANNOT contain spaces, use underscore (_) instead.
  • It is recommended that the <filename> portion anticipates the filename of the media file object to be added later, but this is not a requirement. Media file objects added later with Method 5 (see below) are matched to their respective placeholder assets using a manifest file and the placeholder asset PIDs.
  • Use 2 (two) equal signs to connect the <filename> portion and the <CONTENTMODEL> portion of the XML document's filename.
  • The <CONTENTMODEL> portion of the filename must be one of the following options:
    • L-IMAGE (Large Image content model, for TIF or JPEG 2000 files; example filename: my_large_image23==L-IMAGE.xml)
    • AUDIO (Audio content model, typically for WAV or MP3 files; example filename: interview_part1==AUDIO.xml)
    • VIDEO (Video content model; example filename: episode012==VIDEO.xml)
    • PDF (PDF content model; example filename: my_pdf_file==PDF.xml)
    • BINARY (Binary content model; example filename: very_important_asset==BINARY.xml)

The DAMS will create one DAMS asset per MODS XML file, using the content model specified in the filename. Each asset will store the metadata contained in the MODS XML file in its MODS datastream. The OBJ datastream of each asset will contain a placeholder media file.

Option 5 - Add media file objects to placeholder assets

...

  • Each line of the info.txt manifest MUST contain the following information: <PID without namespace identifier>===<filename.ext>.
  • <PID without namespace identifier> is the part of a PID after the colon (UUID), e.g. 9ebf6ac8-1823-4bf4-8398-654b54090776 for PID utlarch:9ebf6ac8-1823-4bf4-8398-654b54090776.
  • Use 3 (three) equal signs to separate the UUID and the <filename>
  • The <filename> portion CANNOT contain spaces, use underscore (_) instead.

Sample info.txt

...

MultiExcerptNameBatch ingest upload and submit

Step 2: Upload batch job to Jscape

Multiexcerpt
MultiExcerptNameBatch ingest upload


Ensure you have a user account with the SFTP server Jscape by checking UT secrets vault stache for an entry named "<your name> JScape SFTP". Contact the UTL DAMS Management Team if you don't already have an account.


The Jscape web interface does not allow you to upload directories. We recommend using an SFTP client to connect and upload your batch submissions.

  1. Connect to jscape in SFTP client:


  2. Upload your batch job folder into the appropriate location in Jscape:

    1. TEST corresponds to running batch on dams-t01-rh7.lib.utexas.edu, PROD corresponds to running batch on dams.lib.utexas.edu

    2. Place your batch job folder in the appropriate top-level collection folder within the INGEST folder
      Example: /DAMS/TEST/INGEST/utlmisc/my_batch_job_folder (is what I would do for a batch upload to the miscellaneous collection on the DAMS Test Server).

      Any spaces in folder names must be represented by underscores (e.g. special_collection_1).


      We recommend naming your batch folder with your eid, a reference to the destination collection name in the DAMS, or anything else that will help you recognize the batch. In the example <my eid>_<what I am ingesting>, the folder name would be mm63978_EnPatufet1908-1911.


  3. Go over to the DAMS interface and submit your batch job to queue it to be run (see steps below).
  4. Note: Your batch job folder will be removed from the JScape server after seven days whether or not you have run the batch. Back up your batch requests in box or on your local machine. 

Step 3: Set up collection and submit form in DAMS interface

Multiexcerpt
MultiExcerptNamebatch ingest queue

  1. Navigate to or create the target sub-collection to receive batch ingested files in DAMS

  2. Locate and copy the target sub-collection PID to clipboard (namespace:UUID, e.g. utlarch:9ebf6ac8-1823-4bf4-8398-654b54090776)

  3. Navigate to the Batch Ingest form in the DAMS:
    1. Production system: https://dams.lib.utexas.edu/utdams/batch_queue
    2. Test system: https://dams-t01-rh7.lib.utexas.edu/utdams/batch_queue
  4. Select the DAMS Top-Level collection from the dropdown field
  5. Paste the PID of the target sub-collection into the form
  6. Enter the name of the folder on the Jscape/FTP server that contains the files to be ingested (e.g. mm63978_EnPatufet1908-1911)
  7. Click submit

The DAMS should indicate at the top of the form that the batch ingest job was queued.

You will get an email notification after your request for a batch ingest has been received and another notice once the batch ingest process has finished.

...