...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
- Main Title
- MODS mapping: titleInfo/title
- Not repeatable
- Required field – This should be the title used for display in browsing and search results
- Alternative Title
- MODS mapping: titleInfo@type=”alternative”
- Repeatable
- Translated Title
- MODS mapping: titleInfo@type=”translated”
- Repeatable
- Uniform Title
- MODS mapping: titleInfo@type=”uniform”
- Repeatable
- Creator
- MODS mapping: name/namePart
- ATTN: Can we assign “creator” for this role to distinguish it from other names included with an item? That would mean auto assignment of “creator” or some other role for name/role/roleTerm within this name element.
- Not repeatable
- No ability to specify Corporate Body in batch at this time
- ATTN: Is this editable in the form after ingest?
- Required field – This should be the main person or body associated with the item
- MODS mapping: name/namePart
- Contributor
- MODS mapping: name/namePart
- ATTN: I don’t think there’s any role we can automatically assign for name/role/roleTerm with this name element?
- Repeatable
- No ability to specify Corporate Body in batch at this time
- ATTN: Is this editable in the form after ingest?
- MODS mapping: name/namePart
- Statement of Responsibility
- MODS mapping: note@type=”statement of responsibility”
- Not repeatable
- Resource Type
- MODS mapping: typeOfResource
- Not repeatable
- This will help sort results and browse-able content. Please use one of the following:
- sound recording-musical
- sound recording-non-musical
- sound recording
- still image
- moving image
- Genre
- MODS mapping: genre
- Select from one of the following:
- LOC Moving Image Genre-form Guide [http://www.loc.gov/rr/mopic/miggen.html]
- Open Metadata Registry labels for PBCore: pbcoreGenre [http://metadataregistry.org/concept/list/vocabulary_id/148.html]
- ATTN: Do we need to decide which list and which labels are acceptable?
- Repeatable
- Publisher
- MODS mapping: originInfo/publisher
- Not repeatable
- Place of Origin
- MODS mapping: originInfo/place/placeTerm
- Not repeatable
- Date Created
- MODS mapping: originInfo/dateCreated@encoding=”edtf”
- Not repeatable
- Date Created should only be used if Date Issued is a re-issue date. Then Date Created 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 [http://www.loc.gov/standards/datetime/pre-submission.html]
- Date Issued
- MODS mapping: originInfo/dateIssued@encoding=”edtf”
- Not repeatable
- Required field – This should be the main 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 [http://www.loc.gov/standards/datetime/pre-submission.html]
- Copyright Date
- MODS mapping: originInfo/dateIssued
- Repeatable
- This field does not need to be formatted to any certain encoding standard.
- Language Code
- MODS mapping: language/languageTerm@type=”code”
- Repeatable
- Select terms from the LOC MARC Code List for Languages [http://www.loc.gov/marc/languages/language_name.html]
- If this is available, no need to include Language Text
- Language Text
- MODS mapping: language/languageTerm@type=”text”
- Repeatable
- Select terms from the LOC MARC Code List for Languages [http://www.loc.gov/marc/languages/language_name.html]
- If this is available, no need to include Language Code
- Abstract
- MODS mapping: abstract
- Not repeatable
- Note
- MODS mapping: note
- Repeatable
- No ability to distinguish type of note for batch upload at this time
- ATTN: Are we using an automatic type for note at this point or not specifying a type?
- Topical Subject
- MODS mapping: subject/topic
- Repeatable
- Geographic Subject
- MODS mapping: subject/geographic
- Repeatable
- Temporal Subject
- MODS mapping: subject/temporal
- Repeatable
- Occupation Subject
- MODS mapping: subject/occupation
- Repeatable
- Person Subject
- MODS mapping: subject/name@type=”personal”/namePart
- Repeatable
- Corporate Subject
- MODS mapping: subject/name@type=”corporate”/namePart
- Repeatable
- Family Subject
- MODS mapping: subject/name@type=”family”/namePart
- Repeatable
- Title Subject
- MODS mapping: subject/titleInfo/title
- Repeatable
- Related Item ID
- MODS mapping: relatedItem/identifier
- Repeatable
- No ability to specify type of relation in batch at this time
- ATTN: Are we using an automatic type at this point or not specifying a type?
In addition to the descriptive fields, there is one supported operational field, Publish (default: false) for which a value of "True" will cause the newly ingested media object to be published immediately after ingest.
Notes
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.
...