...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
- Bibliographic ID
MODS mapping: identifier
Not repeatable
Used to identify the original catalog record from which metadata was generated.
- Bibliographic ID Label
- MODS mapping: identifier@type
- Not repeatable
Identifies the type bibliographic ID supplied in the Bibliographic ID column. Valid types include "local", "oclc", lccn", and "other". If no bibliographic ID type is included, the type “Other” will be used as default. The value of "local" maps to "Catalog Key" in the Resources Description Form.
- Main Title
- MODS mapping: titleInfo/title
- Not repeatable
- Required field. Title is used for display in search results and single item views. Only the first 32 characters of a title are included in search results listings. Recommended use is to reflect the content captured in digitized media files (such as the title of the piece performed or a short description of the content of a home movie).
- Editable after ingest in "Title" field of Resource Description form.
- If title is not available or missing, create a title that describes something about the content of the item. This is necessary for identifying items in search results.
- Creator
- MODS mapping: name@usage="primary"/namePart (role/roleTerm set to "Creator")
- Repeatable
- No ability to specify Corporate Body in batch at this time
- Required field. Main contributors are the primary persons or bodies associated with the creation of the content. Main contributors will be included in search results display and aggregated for browsing access. At this time there is no ability to specify a main contributor as a corporate body. When possible, use the Library of Congress Name Authority File.
- Editable after ingest in "Main contributor(s)" field of Resource Description form.
- If creator is not available or missing, use the value "Unknown".
- Contributor
- MODS mapping: name/namePart (role/roleTerm set to "Contributor")
- Repeatable
- Contributors are persons or bodies associated with the item but not considered primary to the creation of its content. Examples of this would be performers in a band or opera, conductor, arranger, cinematographer, and choreographer. At this time this is no ability to specify a contributor as a corporate body. When possible, use the Library of Congress Name Authority File.
- Editable after ingest in "Contributor(s)" field of Resource Description form.
- Genre
- MODS mapping: genre
- Repeatable
- Genre can be used to categorize an item by form, style, or subject matter. For consistency and to allow for sorting and aggregating, use terms from the Open Metadata Registry labels for PBCore: pbcoreGenre.
- Editable after ingest in "Genre(s)" field of Resource Description form.
- Publisher
- MODS mapping: originInfo/publisher
- Repeatable
- Publisher of the content of the item.
- Editable after ingest in "Publisher(s)" field of Resource Description form.
- Date Created
- MODS mapping: originInfo/dateCreated@encoding=”edtf”
- Not repeatable
- Creation date should only be used if Date Issued is a re-issue date. Then Creation date would contain the original publication date. Enter date information in a format consistent with the options shown in Extended Date/Time Format (EDTF) 1.0.
- Editable after ingest in "Creation date" field of Resource Description form.
- Date Issued
- MODS mapping: originInfo/dateIssued@encoding=”edtf”
- Not repeatable
- Required field. Date should be the main publication date associated with the item to be used for sorting browse and search results. Enter date information in a format consistent with the options shown in Extended Date/Time Format (EDTF) 1.0.
- Editable after ingest in "Publication date" field of Resource Description form.
- If date issued is not available or missing, enter a date that is narrowed down as much as possible (by range of years) or enter a date for century (18uu, 19uu, 20uu), in accordance with EDTF specifications.
- Abstract
- MODS mapping: abstract
- Not repeatable
- Abstract provides a space for describing the contents of the item. Examples include liner notes, contents list, or an opera scene abstract. This field is not meant for cataloger's descriptions but for descriptions that accompany the item. The first 15-20 words are included in search result listings.
- Editable after ingest in "Summary" field of Resource Description form.
- Topical Subject
- MODS mapping: subject/topic
- Repeatable
- Subject should be used for the topical subject of the content. For consistency and to allow for sorting and aggregating, use terms from the Library of Congress Subject Headings. For temporal subjects (time periods), use Temporal Subject and for geographic subjects (locations), use Geographic Subject. See below.
- Editable after ingest in "Subject(s)" field of Resource Description form.
- Geographic Subject
- MODS mapping: subject/geographic
- Repeatable
- Geographic Subject should be used for the location associated with the content. For consistency and to allow for sorting and aggregating, use terms from the Getty Thesaurus of Geographic Names.
- Editable after ingest in "Location(s)" field of Resource Description form.
- Temporal Subject
- MODS mapping: subject/temporal
- Repeatable
- Temporal Subject should be used for the time period of the content (for example, years or year ranges). Enter date information in a format consistent with the options shown in Extended Date/Time Format (EDTF) 1.0.
- Editable after ingest in "Time period(s)" field of Resource Description form.
In addition to the descriptive fields, there are five supported operational fields:
- Publish
- Whether the item should be automatically published after ingest.
- Default is "No".
- To auto-publish, enter value of "Yes".
- Hidden
- Whether the item will appear in search/browse results for end users. Use this field to prevent users from discovering extra-restricted items.
- Default is "No".
- To trigger hiding, enter value of "Yes".
- Hidden items will still appear in search/browse results for those with ingest privileges.
...
- 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).
- Repeatable
- 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.
- Excel will automatically format hh:mm:ss into time. To circumvent this, begin time offset with a single quote, for example: '0:10 for 00:00:10 and '1:06 for 00:01:06.
- 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 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”
...
...
...
...
...
...
...
...
...