Central Eurasian Information Resource - Image Database
Central Eurasian Information Resource Image Database
Data Dictionary
Mar. 27, 2002
Metadata liaison: Diana Brooking
|
Field Name |
DC Mapping |
Searchable? |
Authority File |
Comments |
|---|---|---|---|---|
|
Title |
Title |
Yes |
none |
A short descriptive phrase in English describing what is depicted in the image. This field will be used as the thumbnail caption. This field will include the English-language name for any named objects. |
|
Notes |
Description |
Yes |
none |
May contain a narrative explanation of the image, its significance, etc. Any information of importance that is not represented elsewhere, or that needs further explanation. |
|
Subjects |
Subject |
Yes |
TGM-1 (LCAF for names) |
Subject terms that denote what is depicted in the image. Terms to be taken from LC's Thesaurus for Graphic Materials I, used as simple descriptors without subdivision. N.B. Replace the ampersand ("&") in TGM with the word "and". Also, if there is absolutely no suitable term in TGM, use LCSH. This field will also include the authorized name for any named objects depicted--this will often be the "original-language" name (e.g., Russian, Kazakh). If no authorized version of a named object can be found, the original-language name will be included in this field anyway. Examples: Kazanskii sobor (Saint Petersburg, Russia) If more than one subject, separate by <br> |
|
Photographer |
Creator |
Yes |
LCAF |
Name of the photographer. Input as lastname, firstname. If more than one name, separate by <br> |
|
Country |
Coverage |
Yes |
BGN |
|
|
Region |
Coverage |
Yes |
" |
Could be used to create canned searches. This field will not always be filled in? Examples: Dalnii Vostok; Siberia (or Sibir?) |
|
Oblast/Province |
Coverage |
Yes |
" |
Will be used to create canned searches. |
|
Rayon/District |
Coverage |
Yes |
" |
This field will not always be filled in. |
|
City/Town |
Coverage |
Yes |
" |
|
|
Latitude |
Coverage |
Yes |
none |
Example: 42.883 |
|
Longitude |
Coverage |
Yes |
none |
Example: 132.900 |
|
Artist/Architect |
Creator |
Yes |
LCAF |
Name of the artist or architect (if known) when the image depicts a building or work of art. Input as lastname, firstname. If more than one name, separate by <br> |
|
Object Date |
Coverage |
Yes |
|
Meant to be used for the date of creation of an art work, the date of construction of a building, or the date the object depicted was created (if known). Prefer a named time period rather than a numeric identifier such as a date range if possible.If more than one phrase used, separate by <br> Examples: 16th century |
|
Image Source |
Source |
Yes? |
none |
This will be a bibliographic citation to the source of an image if it is taken from a book or other published source. Will include the date of publication. Database owner did not anticipate users searching this field. |
|
Contributors |
Contributor |
No? |
LCAF |
Possibly to be a hidden field for staff only. The contributor of the image (may not be the same as photographer). Will staff need to search? Last name, first name if a personal name. If more than one contributor listed, separate by <br>. Example: Rural Development Agency |
|
Image Date |
Date |
Yes |
none |
Date the image was created. Date that a photograph was taken or date of publication for an illustration from a book. Generally the year only. Examples: 1984 1910 |
|
Image Type |
Type |
Yes |
A controlled list, with terms derived from AAT and other thesauri, is being created for the use of inputters. Terms should be used in the singular. Examples could include drawing, photograph, postcard, map... |
|
| Digital Collection | Relation-Is Part Of | no | none | Central Eurasian Information Resource |
| Contact Information | none | no | none | The University of Washington Libraries does not provide reproductions of this image. The original negative, print, or slide reproduced here remains in the possession of the copyright holder. For further information contact the UW Libraries' Slavic and East European Section, slavinfo@u.washington.edu. |
|
Image No. |
Identifier |
Yes |
none |
Possibly an accession number for the image to help with administration of the database--for staff use only probably. |
|
Rights |
Rights |
No |
LCAF |
Copyright is held by the photographer. Input as lastname, firstname. If more than one name, separate by <br> |
| Type | Type | Yes | DCMI Type Vocabulary | Used for cross database search limits.
StillImage |
Issues:
Transliteration and diacritics: CONTENT cannot support diacritics at all. So I anticipate typing words in as they should be, just minus diacritics. Transliteration will be an issue, since different authority files use different transliteration systems. Consistency within this database may not be achieved. LC transliteration would be used for personal, corporate, and building and other object names, as LCAF will be used as the authority file for these terms. (See below for geographic names.)
Controlled vocabulary for geographic names: The GIS portion of the project will be using the BGN/GEOnet forms of geographic names. For consistency within the project, BGN forms should be used in the CONTENT image portion of the project as well. (But for cross-database consistency within CONTENT, LCAF forms in our local hierarchical format would be the choice. In addition to choosing different forms of names sometimes, BGN and LC do not use the same transliteration system.)
Examples:
|
GEOnet |
LC |
Other CONTENT databases |
|---|---|---|
|
Russia |
Russia (Federation) |
|
|
Moskva |
Moscow |
Russia (Federation)--Moscow |
|
Smolenskaya Oblast |
Smolenskaia oblast |
|
MIG said to use BGN as authority file to maintain consistency within the project.