Row 1, Column B contains the submitter's email address (or username, depending on how your system is set up) to be used for notifications and exceptions). The submitter's email or user name must be listed as a manager, editor, or depositor for the collection in which this batch is deposited in the Avalon dropbox.
Row 2 specifies the names of the metadata fields supplied in the following rows. Main Title, Creator, Date Issued, and File are required. These fields are shown in bold in the Excel example file. Each subsequent row represents a single media item to be created. Metadata values are specified first, followed by a list of content files to be attached to each item. Note: Make sure none of the field names in row 2 have leading or trailing blanks, or the field names will not be recognized by Avalon and will report an error.
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 F in the above example).
- Required field. 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 F in the above example).
- Label, Offset, and Skip Transcoding can be listed in any order following the file they are describing. Absolute Location can only be used following Skip Transcoding if Skip Transcoding is included and its value is set to "yes".
- Label is used for display in single item views. Recommended use is to reflect the content captured in digitized media files (such as the Part 1 and Part 2 of the piece performed or titles of songs).
- Only repeatable following a file entry.
- Editable after ingest in "Label" field of Manage Files page
- Offset is used to set the thumbnail and poster image for the display in search/browse results and single item views. Must be entered between 00:00:00.000 and length of file. Enter offset time in a format consistent with this format (hh.mm.ss.sss).
- Only repeatable following an additional file.
- Default is 2 seconds into playback.
- Only applicable to video files. Audio files have a default thumbnail, offset will be ignored.
- If a record contains multiple files, the first offset listed will set the thumbnail and poster image for the Avalon record.
- Editable after ingest in "Poster Offset" field of Manage Files page or on the item preview page.
- Skip Transcoding
- Skip Transcoding is used if a pre-encoded derivative of the file is what is being uploaded to Avalon instead of the master version of the file. This presumes that the derivative(s) match the requirements explained in Avalon Derivatives. Master file location information should be included for complete object ingest. See Absolute Location (below) for further information.
- Only repeatable following a file entry.
- Valid values: “yes” or “no”
- Absolute Location
- Absolute Location is used with Skip Transcoding to indicate the location of the master version of a video or audio file when the file uploaded to Avalon is a pre-encoded derivative.
- Only repeatable following Skip Transcoding if Skip Transcoding is included and its value is set to “yes”.
- If Skip Transcoding is set to “no” or not included, Absolute Location will be ignored.
- Absolute Location should be the full URI path of the server housing the master version of the file.
Batch Processing Notes
The batch ingest process will verify Each batch will generate 2 emails to the user listed at the top of the manifest.
Once Avalon detects the presence of an unprocessed manifest file, it will first verify that the metadata columns are recognizable, that the required columns are present and have values in them, and 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.
If the package is incomplete or in error, it will not be skipped and returned to on a subsequent pass.Each batch will generate 2 emails to the email address listed at the top of the manifest.processed and an error file will be generated in the same directory as the manifest file (e.g., batch_manifest.xlsx.error). The error file will contain details of what was missing, and will email the same information to the user specified in the manifest.
To re-run a successfully completed batch, remove the *.processed file from the batch directory (e.g., batch_manifest.xlsx.processed).