Avalon's Batch Ingest feature provides a method of building one or more media objects 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.
An Ingest Package is the combination of content and metadata that make up a single batch.
The package must be uploaded somewhere within the
batch subdirectory of the Avalon dropbox. It can either be at the root of the batch directory, or in any subdirectory thereof. The following is a very simple Package that has been uploaded:
Manifest File Format
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
The first row specifies the names of the metadata fields supplied in the following rows. Main Title, Creator, and Date Created are required. Support for additional fields is already coded in, but will be finalized and documented in a subsequent sprint. 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.
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.