![]() |
|
|
|
A mapping of data elements from Cities/Buildings Image Archive to Dublin Core
Last updated 8/25/99
Metadata Liaison: Diana Brooking
|
(Image Archive became an independent, hosted database in Autumn Quarter, 1999) Cities/Buildings |
Dublin Core |
Authority file |
Comments |
|
Title |
Title |
|
A brief descriptive phrase. The title is a concise phrase that will be used to label the thumbnails. TITLE may be the title given to the image by the contributor. Generally, it is a commonly used, specific identifying phrase. Some objects are not known by a specific name, but are still commonly identified by a generic name. Note: in original database, residential building names such as "J.J. Glessner House" may be found under a person’s full name or surname: "Glessner House." Please use the most complete form. Examples (specific): Winter Palace; Seagram Building; Temple of Love; Hall of Mirrors Suggestion: If the specific object is unknown, but the larger site is known (e.g., an unknown street in Montmarte), use the site name plus the generic term in TITLE; repeat the site name in SITE or CITY as appropriate. This is so that the display of thumbnail captions and the default sort based on TITLE will be more useful to users. Also in the case of an image of a room or object within a building, use the building's name plus the generic name for the smaller object. Examples: |
|
Site |
Coverage |
LCAF |
Larger architectural object or location that the object is a component of (Note: many objects will not be part of a larger site) (Note: in original data this may include named neighborhoods or city names for generic broad views--please do not duplicate city name in SITE) Examples: Chateau de Versailles; Place de la Concorde; Eurodisney |
|
Detail |
Description |
Type of view: AAT Views in Visual Works hierarchy (use singular form) Object: AAT (singular or plural depending on what is in image) |
The view and/or aspect of the object shown. Generally this is characterized in three ways
Examples: Aerial view; Exterior view; Interior view; Detail Example: Façade; Entrance; Garden; Door; Nave pier Either the compass point orientation or orientation in relation to another object Examples: Southwest; Fountain; South Portico The DETAIL statement should be constructed in the following manner: <Type of view> of <object> from <orientation> Examples: Aerial view from south; Exterior view of west facade from water parterre; Distant view from Siaigan Hill; Detail of interior wall Note: do not duplicate information in different aspects (e.g., Interior view of interior wall) |
|
City |
Coverage |
LCAF |
The city where the object is located Examples: Seattle; Paris; Amsterdam |
|
State |
Coverage |
LCAF |
The state or province where the object is located if in the United States or Canada (Note: use full form) Examples: North Dakota; Washington; British Columbia |
|
Nation |
Coverage |
LCAF |
The nation where the object is located Examples: United States; France; Bhutan |
|
CE Date of Construction |
Coverage |
|
Construction or renovation year(s) of the object DATE will always be expressed as a year or range of years, never as a phrase (17th c.; 1970s) (as per Guide to Indexing and Cataloging with the Art & Architecture Thesaurus, App. A, Date and Geographic Name Guidelines) For indications of century, follow the conventions of these examples: 17th century: 1600-1699 Early 17th century: 1600-1629 Mid-17th century: 1630-1669 Late-17th century: 1670-1699 For indications of a decade: 1970s: 1970-1979 To represent dates before year 1, use the BCE (Before Common Era) field. To represent dates after the year 1, use the CE field. Use a question mark after the date to indicate approximate, probable or uncertain dates |
|
BCE Date of Construction |
Coverage |
|
|
|
Object/Building Name |
Subject |
LCAF |
The proper name given to the specific object or building represented in the slide in authorized form. This field will be used ONLY if there is a proper, specific name for the object depicted. LCAF will be used for the authorized form. The intent is to provide a consistent, uniform name as a search point, as opposed to the TITLE field, which is an uncontrolled, descriptive phrase. (Note: TITLE will often be a common English-language phrase; OBJECT/BUILDING NAME will often be the official, vernacular name in the language of the country where the object is located.) Examples: |
|
Architect/Builder |
Creator |
LCAF; LCSH |
Person or body responsible for object design or people responsible for construction Examples: Wright, Lloyd Frank; Aalto, Alvar; NBBJ (Firm); Gusii (African people) Suggestion: Follow standard format of lastname, firstname for personal names; use LC Subject Headings for the names of peoples |
|
Materials |
Subject |
AAT Materials hierarchy (use singular form) |
The physical substance or physical qualities of the object Examples: Masonry; Brickwork |
|
Type |
Subject |
AAT Built Environment hierarchy (use plural form) |
The physical or purposive form of the object (Note: this will generally be a building type) Examples: Cathedrals; Universities; Amusement parks; Bungalows |
|
Style |
Subject |
AAT Styles and Periods hierarchy (singular or adjectival form) |
A specific style and/or historical period the work represents (Note: this is independent of specific construction date and place. Meant to be used to identify examples of a particular style or historical period) Examples: Deconstructivist; Mediterranean; Baroque |
|
Other terms |
Subject |
|
Additional concepts that are not represented by other data elements but are deemed significant enough to provide access for Examples: Public art; Tilt-up construction; Reclamation projects Suggestion: May use AAT or LC Subject or Name Authority files if terms found there. Suggestion: This could be further refined to several separate fields |
|
Notes |
Description |
|
Descriptive narrative text that provides further background information, points of interest, lecture notes, etc. |
|
********* |
********* |
********* |
********* |
|
Slide number |
Identifier |
|
A unique slide identifier assigned by Meredith Clausen. Consists of two or three letters (representing photographer initials or photograph collection) and several digits (representing an accession number). Examples: DW33; PhJ80; add60; USA250 Note: this is generally the same as the file name (minus extension) of the digitized photograph Suggestion: standardize case |
|
File format |
Format |
|
File format of the image file Consists of a period with a three letter extension of the image file type Examples: .JPG; .jpg; .GIF; .gif Suggestion: standardize case; drop initial period |
|
Transmission data |
Format |
|
Information about the original photograph and of the electronic conversion process Includes information about original source format, machine used for conversion, and digital version details (file format, resolution, color) Example: scanned from slide format using AFGA bulk scanner, tiff format converted to jpeg factor 32, 300-400 ppi Suggestion: Develop standard form for this information as we do more Suggestion: Drop this field if not found useful or incorporate FILE FORMAT into this field |
|
Photographer |
Creator |
LCAF |
Creator of original visual image Examples: Clausen, Meredith L.; Hu, Mary Lee Suggestion: follow Lastname, Firstname format |
|
Photographer’s reference no. |
Identifier |
|
A unique photographer identifier Examples: Meredith L. Clausen Suggestion: Eliminate as it appears to duplicate PHOTOGRAPHER |
|
Date of Photograph |
Date |
  |
Year the photograph was taken Example: 1963 Suggestion: Follow format conventions expressed above in DATE |
|
Source |
Contributor |
LCAF |
Image acquisition source Generally the individual or body who provided the slide or the citation if taken from another work Examples: Clausen, Meredith L.; Fletcher, Banister. History of Architecture, 1905 Suggestion: Lastname, Firstname |
|
Copyright holder |
Rights |
LCAF |
Individual or body that retains copyright to the visual image Examples: Clausen, Meredith L.; Hu, Mary Lee Suggestion: Lastname, Firstname |
| Type limit | Type | DCMI Types | image |