Gallery Maps Format
Gallery Maps Format is documentation for entering maps in the Wayne County, Ohio Online Resource Center. Click to create or edit a record Form:Gallery Maps.
Title Name
This is a mandatory field. Every record must have a title.
Repeatable | No |
Definition | The name given to the resource by the creator or publisher; may also be an identifying phrase or name of the object supplied by the contributing institution. |
Usage | Transcribe the title from the resource itself, if available.
If not available, supply a title. Add the line “Title supplied by cataloger” to the end of the Description field if only some of the titles in the collection have been supplied. When every title in a collection is supplied, a note to that effect on the “About the Collection” page will suffice.
Capitalize only the initial first letter and proper names. Remove leading articles (e.g. A, An, The). |
Examples |
|
Template | title_name |
Form name | Title name |
Organization Name
This is a mandatory field. Every record that includes an organization must be populated.
Repeatable | Yes |
Definition | The name given to the resource by the creator or publisher; may also be an identifying phrase or name of the object supplied by the contributing institution. |
Usage | Transcribe the title from the resource itself, if available.
If not available, supply a title. Add the line “Title supplied by cataloger” to the end of the Description field if only some of the titles in the collection have been supplied. When every title in a collection is supplied, a note to that effect on the “About the Collection” page will suffice. |
Examples |
|
Template | organization_name |
Form name | Organization name |
Creator
This field is mandatory if available. It should be used whenever name(s) associated with the creation of the resource are known. If no names are known, leave the field blank.
Repeatable | Yes. Enter each creator in the same field, separated by a semicolon and a space. |
Definition | An entity primarily responsible for creating the intellectual content of the resource, such as authors of written documents; artists; photographers; collectors of natural specimens or artifacts; etc. |
Usage | Do not use "Unknown"--just leave the field blank.
Use the correct form of the name when available in Library of Congress Authorities(http://authorities.loc.gov) or UofL's Voyager cataloging client. Visual Resources Center will use Getty’s Union List of Artist Names (see Appendix 2 for this and other exceptions specific to the VRC). If an authoritative version of a name is not available, create one:
The function of a creator may be included in parentheses after the name. Use the Relator Terms (see table below). |
Examples |
|
Relator Terms | The function of a creator may be included in parentheses after the name. Use the Relator Terms (see table below of approved terms) |
Template | creator |
Form name | Creator |
Approved Relator Terms
Use the Relator Terms (http://lcweb2.loc.gov/cocoon/loc.terms/relators/dc-relators.html).
Contributor
This field is optional. If a secondary contributor is unknown leave blank.
Repeatable | Yes. Enter each contributor in the same field, separated by a semicolon and a space. |
Definition | The person(s) or organization(s) that made significant intellectual contributions to the resource but whose contribution is secondary to any entity already specified in a Creator element. |
Usage | Use for photographic studios (the photographer would be considered the Creator).
Do not use "Unknown"--just leave the field blank. Use the correct form of the name when available in Library of Congress Authorities (http://authorities.loc.gov) or UofL's Voyager cataloging client. If an authoritative version of a name is not available, create one:
The function of a contributor may be included in parentheses after the name. Use the Relator Terms (see above Relator Terms table). |
Examples |
|
Template | Contributor |
Form name | Contributor |
Description Photo
This is a mandatory field. Every record must include a description.
Repeatable | No |
Definition | An account of the content of the resource [providing background and specifics about it, comparable to what would appear on an exhibit label]. |
Usage | Enter a free-text account of the intellectual content of the resource and any specialized information not included in other elements.
Consider the audience, and the terminology they would likely use. Use the full form of words, at least the first time they are referenced, rather than abbreviations such as St. for Street, ca. for circa, OH for Ohio, etc. Consider including: People depicted in the image or discussed in the audio, in the common usage (if different from the authority) form of their name; transcriptions of signs in the image; any history of objects or people in the resource; speculation about dates, events, or people related to the resource; points of interest; addresses of buildings depicted, etc.
|
Examples |
|
Template | description_photo |
Form name | Description photo |
Subject Tags
This is a mandatory field. Every record must include subject(s).
Repeatable | Yes. Enter each subject in the same field, separated by a semicolon and a space.
See People Pictured OR People Discussed for personal names as subjects. |
Definition | What the content of the resource is about or what it is, expressed by headings, keywords, phrases, names, or other terms for significant people, places, and events, etc. |
Usage | Enter multiple subjects in order of importance.
Set up field properties to link to Library of Congress Thesaurus for Graphic Materials I (LCTGM). Reference usage at http://www.loc.gov/pictures/collection/tgm/. Separate each entry by a semicolon and a space. In addition to LCTGM Use specific or unique words as well as more general words. Identify ethnic groups as appropriate (e.g., African Americans). Refer to LCSH for subject terms for ethnic groups. Geographic subheadings may be applied on a case-by-case basis. Corporate entities (e.g. Oneida Baptist Institute) and physical entities (e.g. Buckingham Palace) belong in this field rather than in Location Depicted, which should be reserved for geographic entities (Oneida (Ky.) and London (England) in the above examples). For corporate entities, the name of the corporation at the time of the artifact being described should be used. |
Examples |
|
Template | subject_tags |
Form name | Subject tags |
People Pictured OR People Discussed OR People Named
This field is mandatory if available. If individuals are not pictured/discussed or named, leave the field blank.
Repeatable | Yes. Enter each name in the same field, separated by a semicolon and a space. See Subject for subjects that are not personal names. |
Definition | Names of people pictured (for images) or discussed (for audio) in the resource. |
Usage | Separate multiple entries by a semicolon and a space.
Do not use "Unknown"--just leave the field blank. Use the correct form of the name when available in Library of Congress Authorities (http://authorities.loc.gov) If an authoritative version of a name is not available, create one:
|
Examples |
|
Template | people_pictured |
Form name | People pictured |
Location
This field is mandatory if available. If the location is not known and cannot be estimated, leave it blank.
Repeatable | No |
Definition | The spatial characteristics of the intellectual content of the resource (more general than the content of the item). |
Usage | Use for geographical headings more general than the content of the item, e.g. to name of the political and physical/spatial settings of the content of the resource (e.g. street, neighborhood, city, county, state, country), as well as any geographic features (lakes, mountains, rivers, etc.) seen in the image. Entities such as named buildings and institutions belong in the Subject field rather than here.
Use the correct form of the place name when available in Library of Congress Authorities (http://authorities.loc.gov) If an authoritative version of a name is not available, create an AACR2-compliant heading:
For renamed places, enter the new place name in this field. (The Title and/or Description should contain the name used when the photo was taken.) Do not use "Unknown"--just leave the field blank. |
Examples |
|
Template | location |
Form name | Location |
Location Note
This field is mandatory if available. If the location is not known and cannot be estimated, leave it blank.
Repeatable | No |
Definition | Add addition location notes |
Usage |
|
Examples |
|
Template | location_note |
Form name | Location note |
Time Period
This field is optional.
Repeatable | No |
Definition | The time period covered by the intellectual content of the resource. |
Usage | If an authoritative version of an era is not available, create a DCMI Period-compliant
heading https://dublincore.org/specifications/dublin-core/dcmi-period/
Do not use "Unknown"--just leave the field blank. |
Examples |
|
Template | time_period |
Form name | Time period |
Date Original
This field is mandatory if available. If the date is not known and cannot be estimated, leave it blank.
Repeatable | No |
Definition | Creation or modification dates for the original resource from which the digital object was derived or created. |
Usage | Follow W3C-DTF standard (ISO 8601) of YYYY-MM-DD.
Use only as much of the date as is known.
Do not use "Unknown"--just leave the field blank. For a range of dates, put space-dash-space in between dates. |
Examples |
|
Template | date_original |
Form name | Date original |
Object Type
This field is optional.
Repeatable | No |
Definition | The term used to describe the physical object. |
Usage | Use the Library of Congress Thesaurus for Graphic Materials vocabulary
(http://www.loc.gov/pictures/collection/tgm/) for graphic materials, and the Getty Art & Architecture Thesaurus (http://www.getty.edu/research/conducting_research/vocabularies/aat/) for non graphic materials (e.g. sound recordings, transcripts, etc.). Add these new names to the shared “Object Type” file. If an object is more than one type, enter each type in the same field, separated by a semicolon and a space. |
Examples |
|
Template | object_type |
Form name | Object type |
Source
This field is mandatory if applicable. It does not apply to born-digital materials.
Repeatable | No |
Definition | When applicable, use the Source element to cite any other resource from which the digital resource was derived, either in whole or in part. |
Usage | When applicable, use the Source element to cite any other resource from which the digital resource was derived, either in whole or in part. |
Examples |
|
Template | source |
Form name | Source |
Collection
This field is mandatory if applicable.
Repeatable | Yes. When an object is part of more than one collection |
Definition | The described resource is a physical or logical part of the referenced resource(s). |
Usage | Use to relate the item to its collection. Note that there is also a Collection Website field intended to relate the digital item to the digital collection home page.
Add collection names to the shared “Collection” file. |
Examples |
|
Template | collection |
Form name | Collection |
Digital Publisher
This is a mandatory field. Every record must have a Digital Publisher.
Repeatable | No |
Definition | An entity that made the resource available. For digital objects, Publisher is the entity that created the digital resource. |
Usage | The name of the University of Louisville unit responsible for digitizing the collection.
Add unit names to the shared “Publisher” file. |
Examples |
|
Template | digital_publisher |
Form name | Digital publisher |
Image Number
This is a mandatory field. Every record must include a unique identifier for the digital object. Also known as an accession number.
Repeatable | No |
Definition | A character string or record number that clearly and uniquely identifies a digital object or resource. The Identifier element ensures that individual digital objects can be accessed, managed, stored, recalled, and used reliably. |
Usage | Preface numbers with the 4-digit code identifying the UL unit.
|
Examples |
|
Template | image_number |
Form name | Image number |
Rights
This field is recommended. It will be particularly useful when metadata entry is dispersed for a given project.
Repeatable | No |
Definition | Internal notes by/for digital projects personnel can be entered here as a way to flag
items for follow-up. |
Usage | Example |
Examples | Example |
Template | rights |
Form name | Rights |
Administrative Notes
This field is recommended. It will be particularly useful when metadata entry is dispersed for a given project. Any notes should be left in the "Discussion" tab and not on the page name.
Repeatable | No |
Definition | Internal notes by/for digital projects personnel can be entered here as a way to flag items for follow-up. |
Usage |
|
Examples |
|