Avalon's batch ingest feature provides a method of building one or more media objects items at a time from uploaded content and metadata outside the user interface. A batch ingest is started by uploading an ingest package consisting of one manifest file and zero or more content files to the Avalon dropbox. For your convenience there is a demo ingest package available to download and import into test systems. Follow the instructions below to ensure a succesful batch upload.
The manifest file is a spreadsheet (
ods) containing the metadata for the objects items to be created, as well as the names of the content files that make up each objectitem. In this case, the manifest file is named
batch_manifest.xlsx. See batch_manifest_template_R2.xlsx for an Excel example file. Required fields are in bold.
|1||Michael's First Test Batchemail@example.com|
|2||Main Title||Creator||Date Issued||Collection||File||Label||File||Label|
|3||Test Object item 1||Klein, Michael B.||2012||Northwestern Video Collection||content/file_1.mp3||Part 1||content/file_2.mp4||Part 2|
|4||Test Object item 2||Northwestern||1951||Northwestern Video Collection||content/file_3.mp4|
Row 2 specifies the names of the metadata fields supplied in the following rows. Main Title, Creator, Date Issued, Collection and File are required. These fields are shown in bold in the Excel example file. Each subsequent row represents a single media object item to be created. Metadata values are specified first, followed by a list of content files to be attached to each objectitem.
Content files listed in the manifest file must have the correct path noted for where those files are located in the Avalon dropbox, relative to the manifest file. Additionally, all content files must include a file extension. If necessary, include any directories or subdirectories (note the paths listed in columns D and E in the above example).