William C. Brumfield Russian Architecture Collection

Title

Title (none)

REQUIRED

A short descriptive phrase in English describing what is depicted in the image. This field will be used as the thumbnail caption and will be used for sorting the thumbnails. This field should start with the English-language name for any named buildings or objects, then a description of the view, and any details shown. A consistent pattern here will lead to better sorting of thumbnails in Contentdm.

Suggestion: If the specific object is unknown, but the larger site is known (e.g., an unknown street in IAroslavl), use the site name plus the generic term in TITLE; repeat the site name in COMPLEX or LOCATION as appropriate.

Examples: Church of St. John Chrysostome, exterior, cornice

Church of St. Nicholas Mokry, interior, fresco

Korovniki, panorama

IAroslavl, street

Subtitle

none (none)

Field created for nonCONTENTdm interface

Full building name

none

This field will be the full formal venacular language name of the building or architectural entity depicted (e.g., in Russian, in Kazakh), as supplied by Prof. Brumfield, followed by geographic qualifier. Only proper names in venacular will go in this field, leave blank for unnamed generic buildings. If no name supplied by Prof. Brumfield, repeat venacular proper name from COMMON NAME field.

Examples: Sobor Blagoveshcheniia Presviatoi Bogoroditsy (Nizhnii Novgorod, Russia)

Ulitsa Lenina, 4 (Volgograd, Russia)

If 2 or 3 buildings are depicted,  separate by <br>. Leave this field blank if more than 3 buildings are shown and a larger complex name is available.

English building name

none

REQUIRED

This field will be the English language name of the building or architectural entity depicted. This field will also include generic names for unnamed buildings. Follow with the geographic qualifier.

Examples: Church of St. Nicholas Mokryi (IAroslavl, IAroslavskaia oblast, Russia)

Taternergo Building (Nizhnii Novgorod, Russia)

log house (IAroslavl, IAroslavskaia oblast, Russia)

If 2 or 3 buildings are depicted,  separate by <br>. Leave this field blank if more than 3 buildings are shown and a larger complex name is available.

Common building name

Subject (LCAF)

This field will be the venacular language name of the building or architectural entity depicted (e.g., Russian, Kazakh). This name will be the most commonly used form as found in reference sources and as established in the National Authority File. If no authorized version of a named object can be found, the cataloging supervisor will be alerted and a name may be established in the LC NAF.

Examples: Kazanskii sobor (Saint Petersburg, Russia)

TSerkov Ioanna Zlatousta v Korovnikakh (IAroslavl, IAroslavskaia oblast, Russia)

If 2 or 3 buildings are depicted,  separate by <br>. Leave this field blank if more than 3 buildings are shown and a larger complex name is available.

Complex/ensemble name

Subject (LCAF)

Larger architectural ensemble of which the object depicted is a component. (Must be a named site that is smaller than the city or town.) If no authorized version of the name can be found, the cataloging supervisor will be alerted and a name may be established in the LC file.

The English name of the complex may be included in NOTES field, if it is not present in the title.

Example: Iosif Volokolamskii monastyr

View Type

Desc (AAT)

Type of view, from subset of AAT views hierarchy.

Examples:  exterior view

interior view

View Orientation

Desc (AAT)

Orientation of view. (2 separate view fields may be needed for non-Contentdm interface.)

Examples: east

northwest

Architectural detail

Subject (AAT)

Type of objects depicted when a part of a single building is emphasized in the image.

Some terms specific to Russian architecture may not be in AAT. We will create a local list based on Brumfield's own glossaries and publications for this field (and any other fields using AAT). We will also try submitting these terms to AAT, but will not wait for approval to use them.

List only details that are visible in the image and that are visible *enough* so that a user would judge the image a suitable example of that detail.

List details in order of prominence. The first detail listed should be the one considered most prominent, the focus of the picture. Data in other fields (OBJECT DATE, ARCHITECT/ARTIST, STYLE/SCHOOL, RESTORATION DATE) will be supplied based on the first detail.

Example: cornices

iconostases

Location

Coverage (LCAF, MIG style)

REQUIRED

Enter <Country--Oblast--City>.
Derive place names from LC headings. If no authorized version of the place can be found, the cataloging supervisor will be alerted and a name may be established in the LC file.

Example: Russia (Federation)--IAroslavskaia oblast--IAroslavl

Street Address

None

Street address of the architectural entity. (In some cases may duplicate the BUILDING NAME.)

Example: Nevskii prospekt, No. 5

Object Date

Date (non searchable, but displayed)

Be sure to include all four digits of all years. This field is used in combination with the BEGIN and END DATE fields to enable searching (see that entry for details). Specific dates (e.g., September 12, 1933; June 1912) are to be noted in the NOTES field.

Project staff in consultation with Brumfield will come up with only one date range for the object depicted. Only the Date or date range that applies to the first listed ARCHITECTURAL DETAIL will be used as OBJECT DATE if that detail is the most prominent part of the image.

Examples: 1649-1654

16th century

Begin Date

Date (searchable, but hidden)

Reflects the OBJECT DATE field. If the date is a single year, it is the same in both the OBJECT DATE and the BEGIN DATE fields. If the date in the OBJECT DATE field is a date range, then the BEGIN DATE field contains the first date in the range.

Prof. Brumfield's advice: for "ca." dates, use a range +/- 10 years from the ca. date; for "mid-century," use +/- 20 years from the mid-century; for "first half/second half/early or late century," use the first or last 50 years of that century.

Examples for BEGIN DATE: 1649

1500

End Date

Date (searchable, but hidden)

Reflects the OBJECT DATE field. If the date is a single year, then END DATE field is blank. If the date in the OBJECT DATE field is a date range, then the END DATE field contains the last date in the range.

Examples: 1654

1599

Architect/artist

Creator (LCAF)

Use standard format of Last name, First name. If no authorized version of the name can be found, the cataloging supervisor will be alerted and a name may be established in the LC file. If the architect is known to be unknown, input "unknown", rather than leaving blank.

In cases where there are multiple names pertaining to different ARCHITECTURAL DETAILS, list only those names associated with the first listed detail, if that detail is considered to be the most prominent part of the image.

Do not list names of restorers in this field.

Examples: Starov, Ivan Egorovich, 1744-1808

unknown

Patron/Owner

Creator (LCAF)

The name of the patron who contributed financially to the construction of the building (usually churches). More details about the patronage can be included in NOTES. NOT to be confused with the saints that churches may be dedicated to. Also can be used for historically important owners of the building. Use standard format of Last name, First name.

Example: Sveteshnikov, Nadei

Notes

Desc

Free text field giving any descriptive information about the image that could be useful. Includes more details about what is depicted, photo notes, and the history of the object, including details about restoration, demolition, or original location (if the building was moved). Different aspects should be separated by paragraphs <br><br>. Descriptions pertaining to different ARCHITECTURAL DETAILS should be listed in the same order as the details are listed.

Examples:  Left to right: Church of Vladimir Mother of God, bell tower, Holy Gates, Church of St. John Chrysostome. View taken from edge of Volga River.<br><br>

The Korovniki complex was built in the 16th century by an Austrian Dominican order, and was saved from an extensive, tasteless renovation in the 19th century by the sudden bankruptcy of the town's leading merchants.

Style/school

Subject (AAT)

A specific style and/or historical period the work represents.

If there is more than one ARCHITECTURAL DETAIL listed, use only the style that pertains to the first listed detail, if that detail is considered to be the most prominent part of the image.

Examples: Deconstructivist; Mediterranean; Baroque

Building type

Subject (AAT)

Example: parish churches

Materials

Subject (AAT)

If there are multiple ARCHITECTURAL DETAILS with different materials, list materials in the same order as the details, that is, the first listed material should correspond to the first listed detail.

Example: brick<br>ceramic title<br>copper

Restoration Date

Date

Only the first year of a restoration will be listed. No date ranges will be used here. However, there may be more than one restoration for a building, so that more than one beginning year could be listed.

If there are multiple ARCHITECTURAL DETAILS, list only the Restoration Dates associated with the first listed detail, if that detail is considered to be the most prominent part of the image.

Example: 1993

1878<br>1912<br>1994

Preservation Status

Desc (local list)

A list of terms will be used, still to be devised. A delimiter (<br>?) will be used to separate following free text describing  in more detail the most current known information about the state of the object depicted.

Examples: threatened<br>The roof of this church is caving in and the city council has a plan(1997)  to use the property to build a swimming pool.

Site Contact

None

Person to contact in the object's location or elsewhere in Russia, for information, access, etc. for the object itself.

Example: Ivan Ivanov, church janitor, Lenin prospekt 34, IAroslavl RUSSIA 1184594

Digital Collection

Relation-Is Part Of

REQUIRED
William C. Brumfield Russian Architecture Collection

Image No.

Identifier

REQUIRED Use WCB iventory number, but you have to remove the hyphen. (There is some question as to the uniqueness of the numbers in WCB's scheme. May need to devise accession numbers. Stay tuned.)

Example: I303

Contact Info

None

REQUIRED

Information about whom to contact for information about the image (as opposed to the object)

Copyright

Rights

REQUIRED

Any information about restrictions can go here or in the Contact Info field, and then the name of the person holding copyright would go here.

Example: Brumfield, William Craft, 1944-

Photographer

Creator (LCAF)

Example: Brumfield, William Craft, 1944-

Photo date

Date

Example: 1997

Photo type

Type (local list)

Example: 35 mm color slide

Image Modification

none (none)

Brief information with initials and date for any digitally enhanced images.

Example: underexposed image enhanced, JW, 12-17-02

Record Last Updated

None (ISO standard)

Date the metadata was last updated. Somewhat useful in determining currency of the Preservation and Site Contact information.

Examples: 2002-07-24

Category

None (local list)

(searchable, hidden)

REQUIRED

List of terms that help to define relationships between images for use in an additional interface to Contentdm. Choose only one value for each image.

Panorama: wide-range and far away views that include architectural entities and landscape. Images in this category could have multiple KEY ENTITY values.

Complex: views of an architectural complex that shows architecture only. Images in this category could have multiple KEY ENTITY values.

Building-Exterior: exterior shots of a building where no particular detail is emphasized.

Building-Interior: interior shots of a building where no particular detail is emphasized. There will be very few images in this category, as most interior shots will be Detail-Interior.

Detail-Exterior: exterior shots of a building where a particular detail is the focus.

Detail-Interior: interior shots of a building where a particular detail is the focus.

Key entity

None (local numbering scheme?)

(searchable, hidden)

REQUIRED

The architectural entity with which this image associates. Unique identifier to be used in an additional interface to Contentdm.

Latitude

Coverage (searchable, hidden)

To be used in non-Contentdm interface.

Example: 42.883

Longitude

Coverage

(searchable, hidden)

To be used in non-Contentdm interface.

Example: 132.900

Key image

None

(searchable, hidden)

REQUIRED

Toggle that indicates whether this image is used as the visual anchor for the architectural entity it is associated with, in the additional interface to Contentdm.

Examples: 0: image is NOT key image; 1: image IS key image

Type limit

Type

(DCMI types; searchable, hidden)

REQUIRED

Example: image