Page tree

Versions Compared


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


The first row specifies the names of the metadata fields supplied in the following rows. Main TitleCreator, and Date Created are required. Support for additional fields is already coded in, but will be finalized and documented in a subsequent sprint. Each Each subsequent row represents a single MediaObject to be created. Metadata values are specified first, followed by a list of content files to be attached to each object. (It is important that the content file columns not have headers, or they will be misinterpreted as metadata.) Content filenames are relative to the location of the manifest file itself.

For multivalued fields, create multiple columns with the same header, e.g.

Main TitleCreatorDate CreatedTopical SubjectTopical Subject 
Nachos: A MemoirKlein, Michael B.2012-12-22MeatCheesetasty_tasty_nachos.mp4

Supported Field Names (required fields in bold)

  • Main Title
  • Alternative Title
  • Translated Title
  • Uniform Title
  • Creator
  • Contributor
  • Statement of Responsibility
  • Resource Type
  • Genre
  • Publisher
  • Place of Origin
  • Date Created
  • Date Issued
  • Copyright Date
  • Language Code
  • Language Text
  • Media Type
  • Abstract
  • Note
  • Topical Subject
  • Geographic Subject
  • Temporal Subject
  • Occupation Subject
  • Person Subject
  • Corporate Subject
  • Family Subject
  • Title Subject
  • Related Item ID
  • Identifier
  • Location URL

In addition to the descriptive fields, there is one operational field, Publish (default: false), which, if true, will cause the newly ingested media object to be published immediately after ingest.


The batch ingest process will verify that the package is complete (i.e., all content files specified in the manifest are present and not open by any other processes) before attempting to ingest it. If the package is incomplete, it will be skipped and returned to on a subsequent pass.