The manifest file is a spreadsheet (
ods) containing the metadata for the objects to be created, as well as the names of the content files that make up each object. In this case, the manifest file is named
|1||Michael's First Test Batchfirstname.lastname@example.org|
|2||Main Title||Creator||Date Created|
|3||Test Object 1||Klein, Michael B.||2012||content/file_1.mp3||content/file_2.mp4|
|4||Test Object 2||Northwestern||1951||content/file_3.mp4|
Row 1, Column A contains a reference name for the batch.
Row 1, Column B contains the submitter's email address (to be used for notifications and exceptions).
Row 2 specifies the names of the metadata fields supplied in the following rows. Main Title, Creator, and Date Created are required. 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 Multivalued fields are specified by multiple columns with the same header, e.g.:
|1||Michael's Second Test Batchemail@example.com|
|2||Main Title||Creator||Date Created||Topical Subject||Topical Subject|
|3||Nachos: A Memoir||Klein, Michael B.||2012-12-22||Meat||Cheese||tasty_tasty_nachos.mp4|
Supported Field Names (required fields in bold)
In addition to the descriptive fields, there is one supported operational field, Publish (default: false), which, if true, will cause the newly ingested media object to be published immediately after ingest.