3

EDITORIAL RULES, CONTINUED

3.5

Associative Relationships

Included in this chapter

• Related Concepts
• Relationship Type
• Historical Flag
• Dates for Associative Relationship
  

• Example
  [from VCS, for "travertine"]

[from an end-user display, for "travertine"]

3.5.1

Related Concepts

3.5.1.1

Definition
Associative relationships to other concept records in the AAT, including various types of ties or connections between concepts, excluding genus/species (hierarchical) relationships. Related Concepts are also called Related Terms (RT) in the jargon of thesaurus construction.

3.5.1.2

Values
Values for the Related Entity are concatenated automatically by the system, using the preferred name and other information from the linked record.

3.5.1.3

Sources: Warrant for linking the concepts
The same standard general references that are appropriate for the Scope Note may be used to determine which concepts are related. See 3.4 Scope Note.

3.5.1.4

Discussion
A Related Concept is an associative relationships between the AAT record at hand and another AAT record. Only clear and direct relationships should be recorded. These direct relationships are typically current, but occasionally may be historical.

• Given that associative relationship may be used for retrieval, it is recommended not to frivolously make links between Related Concepts. Relationships should be made only between records that are directly related, but where hierarchical relationships are inappropriate. If a thesaurus is bound together by too many associative relationships between entities that are only loosely or indirectly related, the value of the relationships in retrieval is lost. Consider this question: If the end-user is interested in retrieving Concept X, will he or she also want to retrieve Concept Y? If not, probably there should not be an associative relationship between the two records.

3.5.1.5

RULES

3.5.1.5.1

Minimum requirements
Adding a Related Concept is required when necessary, as described under Relationship Type below.

• Link concepts that contain terms that are semantically or conceptually linked, but are neither equivalents (synonyms) nor hierarchically related.

3.5.1.5.2

When to make Associative Relationships
Make links to Related Concepts when it is useful to the end-user to have a cross-reference to the other concepts and when the concepts are directly related to each other but they do not have a hierarchical relationship. Think in terms of retrieval: Would such a link be useful in a search engine? If the concept records are clearly related but they are not linked via the hierarchy, create an associative relationship to prevent the conceptual link from being lost. In the examples below, the Related Concepts are in different hierarchies from the record for watercolors.

• Example
  [for "watercolors" paintings]
  
• Relationship Type: equipment needed/producing is
  Related Concept: watercolor brushes (<artists' brushes by function>, artists' brushes, ... Furnishings and Equipment)
  
  Relationship Type: material(s) used/producing is
  Related Concept: watercolor (water-base paint, <paint by composition or origin>, ... Materials)
  
  Relationship Type: material(s) used/producing is
  Related Concept: watercolor paper (drawing paper, <paper by function>, ... Materials)
  
  Relationship Type: creator(s) is
  Related Concept: watercolorists (<painters by technique, implement, or material employed>, implement, ... People)
  
  
• Guide terms
  Associative relationships may be made between concept records, between a concept record and a guide term record, and between two guide term records.
  
• Example
  [for the guide term "<bookbinding and bookbinding processes and techniques>"]
• Relationship Type: equipment needed/used is
  Related Concept: <bookbinding equipment> (<equipment by process>, equipment, ... Furnishings and Equipment)
  
  
• Confusion between two concepts
  If there is a significant possibility that two concepts may be confused by knowledgeable AAT users, link them as Related Concepts.
  
• Example
  [for "airfields"]

• See the list of Relationship Types below for further examples of when to make Related Concepts.
  
  
• Homographs
  If the only cause of potential confusion is that the descriptors or other terms are the same or similar, do not link them as Related Concepts. Make a Qualifier for both terms to distinguish them from each other (see Chapter 3.3: Terms).
  
  
  • In the rare event that the historical meanings of the terms have changed, explain it in the Scope Note and link the terms as Related Concepts.
    
    
• Example
  [for "dinoi"]
• Scope Note: Used by modern scholars to refer to ancient Greek large, round-bottomed bowls that curve into a wide, open mouth, and that often stood on a stand. Metal vessels of this shape were probably used for cooking and those made of terracotta were used for mixing wine and date from the mid-seventh through the late fifth centuries BCE. They are distinguished from "lebetes" by their larger size. Ancient literary evidence suggests that the term was originally applied to drinking cups rather than bowls, and that such bowls were at that time called "lebetes."
  
• Relationship Type: related to
  Related Concept: lebetes (vessels, <containers by form>, ... Furnishings and Equipment)
  
  
• Hierarchical vs. Associative Relationships
  Do not make associative relationships when hierarchical relationships are more appropriate. Generally, concept records that have the same parent or grandparent, or that have a parent/child relationship themselves, should not be linked as Related Works. An exception is for the Relationship Type distinguished from (see discussion of Relationship Types below).
  
  
  • If you are tempted to make an associative relationship, but none of the Relationship Types seems to fit, you probably have an invalid associative relationship (generally because a hierarchical relationship would be more appropriate). For example, if the editor were creating the term compluvia, and the Scope Note reads: Apertures in the center of roofs of atriums in ancient Roman houses, sloping inward to discharge rainwater into a cistern or tank, called an impluvium, there would be a close relationship between compluvia ((<openings by location or context>) and impluvia (<plumbing and stormwater system components>). However, none of the Relationship Types adequately conveys the association. Therefore, the editor may realize that compluvia and impluvia should instead be siblings under the parent atriums (Roman halls), and the editor would then make atriums (Roman halls) the non-preferred parent (see 3.1 Hierarchical Relationships).

3.5.2

Relationship Type

3.5.2.1

Definition
A phrase characterizing the relationship between the concept at hand and the linked concept.

3.5.2.2

Values
Values are chosen from a controlled list comprising a code and phrase. Each code-plus-phrase is linked to another code, which is the reciprocal relationship.

• Example
  [partial view of controlled list from VCS]

3.5.2.3

RULES

3.5.2.3.1

Appropriate Relationship Types
It is required to include a Relationship Type for each Related Concept.

• Choose a specific suitable Relationship Type, if possible. Use the broad related to as a default if a specific one is not appropriate.
  
  
• Link to the correct side of the relationship
  Remember that Relationship Types are reciprocal (that is, linked to both records). When you choose a Relationship Type, make sure that the Relationship Type and its counterpart will work from the points of view of both linked records. Be very careful! There are hundreds of mistakes in the AAT where editors have linked to the wrong side of the relationship.
  
  
  • For example, if you are in the record for naive artists and you want to link to naive art, you should use 2326 creation/product(s) created is because you are linking to the creation naive art.

• Test: The Relationship Type should make sense in a string or phrase like the following one, where the focus record is the one you are editing and the target record is the one to which you are linking:

Focus Record - Relationship Type - Target Record
[for] naive artists - creation/product(s) created is - naive art

• Avoid Redundant Relationships
  Link a concept to another concept only once. If multiple relationships apply, choose the predominant or best one.
  
  
• Example
  [NOT this, for "languages," three links to the same Related Concept, only the Relationship Type differs]

• Relationships mentioned in the Scope Note
  Important relationships related to the meaning or usage of the term should be mentioned in the Scope Note and often linked as an associative relationship. This relationship is often distinguished from, but you should use whatever Relationship Type is compatible with the description in the Scope Note. The examples below illustrate various ways to refer to distinguished from relationships in the Scope Note. See also 3.4 Scope Note.
  
  
• Examples
  [in the record for "rock-cut churches"]
  
• Scope Note: Churches comprising spaces that have been cut into the living rock. They are distinguished from "cave churches," which utilize natural cavities in the earth's surface.
• Relationship Type: distinguished from
  Related Concept: cave churches
  
  [in the record for "eaves"]
  
• Scope Note: Refers to the horizontal portions of a sloping roof that project beyond the walls. For portions of the roof projecting beyond the gable, use "verges."
• Relationship Type: distinguished from
  Related Concept: verges
  
  [in the record for "realia"]
  
• Scope Note: Generally, refers to all physical objects or physical phenomena not produced by humans. The universe of physical objects is often divided into realia, which are naturally occurring objects and phenomena, and "artifacts," which are human-made objects and phenomena. Specifically, in library classification systems, realia are physical objects that are not the books, periodicals, or sound recordings typically cataloged by libraries. Specifically, in education, realia are objects from nature, home, or otherwise from real life that are used in classroom instruction.
• Relationship Type: distinguished from
  Related Concept: artifacts
  
  
• Quick reference for Relationship Types
  The code number of the relationship guide term occurs at the intersection of the two sides of the relationship. For example, a relationship between a person (top row) and an activity (left column) is guide term number 2310 <person and an activity>. Where there is no guide term, the number represents the relationship type itself.

• Definitions of Relationship Types
  Apply Relationship Types according to the definitions below.
  
  
  • For some relationships, the relationship type is the same on both sides of the link; however, for most it is different depending upon which record you are in. Be very careful to choose the correct relationship for the focus record (i.e., the record you are in when you make the relationship). Consider what will make sense when displayed to a user.
    
    
  • Do not link to the phrases in angled brackets; these serve as guide terms only.

   » List of relationship types:

• general
  related to: General designation for relationships, where no specific relationship is known or appropriate. Also, legacy data from the old AAT editorial system may contain this relationship type. Replace it with a more specific one when you edit the legacy record.
  formerly related to: Use for relationships that no longer exist because the situation has changed or because the state of scholarship has changed regarding the appropriateness of the relationship.
  distinguished from: Use when there is a significant risk that two or more concepts could be confused or misused.
  meaning/usage overlaps with: Use when the terms are not synonyms and thus are recorded in separate records, but a significant part of the meaning or usage overlaps between the terms.
  
  

• Examples
  [in the record for "emergency housing"]
• Relationship Type: related to
  Related Concept: crisis shelters
  
  [in the record for "piers (supporting elements)"]
  
• Relationship Type: distinguished from
  Related Concept: columns (architectural elements)
  Relationship Type: distinguished from
  Related Concept: posts
  
  [in the record for "cave architecture"]
  
• Relationship Type: meaning/usage overlaps with
  Related Concept: rock-cut architecture

• 2204 <a thing causes/caused by an action>
  Use for relationships between processes or actions and a thing caused by or resulting from the process or action.

• Example
  [in the record for "carving (process)"]
• Relationship Type: causative/resulting concept(s) is
  Related Concept: carvings (visual work)

• 2207 <a thing exists in locational setting>
  Use for things that are associated with a particular location, context, or setting.

• Examples
  [in the record for "ball courts"]
  
• Relationship Type: locational context/setting is
  Related Concept: hachas [ceremonial axes]
  
  [in the record for "computer centers"]
  
• Relationship Type: thing(s) involved are
  Related Concept: computers

• 2210 <a product and asscociated equipment>
  Use for things that are produced by equipment. Use only for unique things and equipment, not for common equipment that is used to make many things (e.g., you would not link scissors to all the things made by using scissors).
  

• Example
  [in the record for "stereoscopic cameras"]
• Relationship Type: thing(s) needing/produced by are
  Related Concept: stereoscopic photographs

• 2214 <a thing and its product>
  Use for things needed to produce a product. Only record unique relationships.

• Example
  [in the record for "eyelets"]
• Relationship Type: product(s) needing/produced by are
  Related Concept: broderie anglaise
  
  [in the record for "basilica"]
  
• Relationship Type: thing(s) needed/using are
  Related Concept: basilican plan

• 2280 <person works/exists with another person>
  Use for people who work with, exist with, are otherwise closely associated with, or are counterparts of other people.
  

• Example
  [in the record for "barons"]
• Relationship Type: counterpart is/works/exists with
  Related Concept: baronesses

• 2284 <a person and field of study>
  Use for persons who are involved in a field of study or discipline. See also 2285/2286 for persons involved in activities.
  

• Examples
  [in the record for "architects"]
• Relationship Type: field of study/discipline is
  Related Concept: architecture (discipline)
  
  [in the record for "Egyptology"]
  
• Relationship Type: practitioner(s)/student(s) are
  Related Concept: Egyptologists

• 2290 <a person and locational setting>
  Use for persons associated with a locational context. Use only for unique relationships, not for locations common to multiple types of people.

• Example
  [in the record for "roperies"]
• Relationship Type: user(s)/inhabitant(s) are
  Related Concept: rope-makers

• 2310 <person and an activity>
  Use for persons who perform an activity, process, or technique. Use only for unique relationships. See also 2311/2312 for persons in a field of study.

• Example
  [in the record for "clockmaking"]
  
• Relationship Type: person(s) performing activity are
  Related Concept: clockmakers

• 2314 <a person and a material>
  Use for persons who use materials. Use only for unique relationships.

• Example
  [in the record for "precious stone"]
• Relationship Type: user(s)/producer(s) are
  Related Concept: lapidaries

• 2320 <a person uses things/equipment>
  Use for persons who use equipment or other things. Use only for unique relationships.

• Example
  [in the record for "violoncellos"]
• Relationship Type: user(s) are
  Related Concept: violoncellists

• 2324 <a person creates things>
  Use for persons who create or produce objects or other things. Use only for unique relationships.

• Examples
  [in the record for "drawings"]
• Relationship Type: creator(s) are
  Related Concept: draftsmen
  
  [in the record for "glassmakers"]
  
• Relationship Type: creation/product(s) created are
  Related Concept: glassware

• 2396 <field of study and a thing>
  Use for a field of study, discipline, or practice and thing(s) that are the focus of the field of study. Use for unique relationships.

• Example
  [in the record for "religion (discipline)"]
• Relationship Type: thing(s) that are focus
  Related Concept: religions

• 2407<a field of study and a location>
  Use for a field of study or practice and the location where the study or practice takes place. Use for unique relationships.

• Example
  [in the record for "religion and related disciplines"]
• Relationship Type: locational context/setting is
  Related Concept: theological seminari

• 2410 <a field of study and an activity/event>
  Use for a field of study or practice and an activity or event required for or closely associated with the field of study. Use for unique relationships.

• Example
  [in the record for "cinematography"]
• Relationship Type: activity/event involved is
  Related Concept: filmmaking

• 2414 <an activity and materials>
  Use for materials needed for an activity or event. Use only for unique relationships.

• Example
  [in the record for "dyeing"]
• Relationship Type: material required/producing is
  Related Concept: dye

• 2420 <an activity and locational setting>
  Use for an activity or event and its locational setting. Use only for unique relationships.

• Example
  [in the record for "puppet theaters"]
• Relationship Type: activity/event taking place is
  Related Concept: puppetry (performing arts)

• 2426 <an activity and products>
  Use for an activity or event and the products produced by the activity or event. Use for unique relationships.

• Examples
  [in the record for "collages"]
• Relationship Type: activity/event producing is
  Related Concept: collage (technique)
  
  [in the record for "paper (fiber product)"]
  
• Relationship Type: activity/event producing is
  Related Concept: papermaking

• 2430 <an activity and equipment>
  Use for an activity or event and equipment used or needed. Use only for unique relationships.

• Examples
  [in the record for "masks (costume)"]
• Relationship Type: activity/event using/producing is
  Related Concept: masquerades
  
  [in the record for "Easter"]
  
• Relationship Type: equipment needed/used is
  Related Concept: paschal candles

• 2500 <material and a thing>
  Use for materials used to make objects. Use only for unique materials that are used to make one particular type of work, not for common materials that are used to make many types of work (e.g., do NOT link stone to sculpture because stone is a common material used to make many things).

• Examples
  [in the record for "mosaics (visual works)"]
• Relationship Type: material used/producing is
  Related Concept: tesserae (mosaic components)
  
  [in the record for "stained glass (materials)"]
  
• Relationship Type: object(s) using/produced by are
  Related Concept: stained glass (visual works)

• 2550 <a style/period/culture and a thing>
  Use for a style, period, or culture that is uniquely reflected in or associated with an object, creation, or other thing.

• Example
  [in the record for "Nasca lines"]
• Relationship Type: related style/period/culture is
  Related Concept: Nasca

• 2600 <person in a state or condition>
  Use for persons or organizations that are directly associated with a particular state or condition. Use only for unique situations, not for states or conditions that are common to multiple types of persons.

• Example
  [in the record for "adulthood"]
• Relationship Type: related person(s) are
  Related Concept: adults

• 2603 <things in a state or condition>
  Use for objects, materials, or other things that are directly associated with a particular state or condition. Use only for unique situations, not for states or conditions that are common to multiple types of things.

• Example
  [in the record for "magnets"]
• Relationship Type: condition is
  Related Concept: magnetism

• 2606 <activities related to a state or condition>
  Use for activities that are directly associated with a particular state or condition. Use only for unique situations, not for states or conditions that are common to multiple types of activities.

• 2800 <a thing, material, etc. is closely associated with another>

Use for two things that are always located together or otherwise closely associated. Do not use for things that also have a hierarchical relationship to each other. It is generally not necessary to use this relationship for siblings under a single parent, unless there is an additional special relationship that will be lost without this associative relationship. See also 2805/2806 for things related contextually.

• Example
  [in the record for "cups"]
• Relationship Type: conjuncted with
  Related Concept: saucers

• 2804 <one thing is usually in the context of another bigger thing>
  Use for a thing,style, or material always seen or used in the context of another, typically larger thing. Do not use this relationship if the two things also have hierarchical whole/part relationships in the AAT. For things that are equal in the contextual relationship, use 2801 conjuncted with or 2808 coexisted with (for styles).

• Example
  [in the record for "bookmarks"]
• Relationship Type: contextual thing(s) are
  Related Concept: books

• 2807 thing(s) derived from common source
  Use for things or materials derived from a common source. If the source object or material is also in the AAT and the two things are already linked to it, do not use this to redundantly link them to each other.

• Example
  [in the record for "peaches"]
• Relationship Type: thing(s) derived from common source
  Related Concept: peach (hardwood)

• 2808 <culture/style/period coexisted with another>
  Use for cultures or styles that coexisted in the same time and place, or were in the same place and significantly overlapped in time, even if they did not coexist for the entire period. Do not use for records that have a parent/child hierarchical relationship.

• Example
  [in the record for "Sangoan" culture/style]
• Relationship Type: coexisted with
  Related Concept: Fauresmith

• 2810 <style/period preceded / followed>
  Use typically for styles/periods when one period followed another chronologically and 1) the periods are not linked as siblings in the hierarchy or 2) you wish to use the Date fields for the relationship (see Dates for Related Concepts below).

• Example
  [in the record for "First Dynasty (Egyptian)," the linked record is a sibling, but the editor needed to use the date fields for the relationship, thus the Associative Relationship was used]
• Relationship Type: preceded
  Related Concept: Second Dynasty (Egyptian)
  Display Date: Second Dynasty began ca. 2775 BCE
  Start: -2785 End: -2765

• 2813 <things, materials comprise another>
  Use for things or materials that comprise another thing or material. Do not use if there is already a hierarchical relationship between the things or materials. May be used to link components to their larger context, but see also 2805/2806 for things related contextually.

• Example
  [in the record for "lapis lazuli (rock)"]
• Relationship Type: composed of
  Related Concept: calcite

• 2816 <thing,material transforms into another>
  Use for things or materials that are transformed into another, whether by natural or artificial process.

• Example
  [in the record for "obsidian"]
• Relationship Type: transforms into
  Related Concept: pumice

• 2820 <one concept/style/period is based on another>
  Use when one thing, material, or style/period is derived from another and the things/materials/styles/periods are not linked through the hierarchy. Do not use when both are in the same segment of the hierarchy (e.g., do not use it to link Renaissance and Baroque). Do not use when one thing or style/period simply influenced another. A relationship characterized by "influenced by" is not significant enough to warrant an associative relationship.

• Example
  [in the record for "Gothic Revival," which is in a different part of the hierarchy from "Gothic (Medieval)"]
• Relationship Type: is based on
  Related Concept: Gothic (Medieval)

• 2823 <one culture/style/period has parallels with another>
  Use to link two cultures or styles that seem to have developed from one another or from a common source, but where the relationship has not been firmly established by scholars or where scholars otherwise generally use imprecise language such as "closely associated with," etc.

• Example
  [in the record for "Chasseen," which has a relationship with Lagozza, but scholars are uncertain of the nature of the contact between the cultures]
• Relationship Type: parallels exist with
  Related Concept: Lagozza

• 2830 <species are related>
  Use to link one species or variety that evolved from another, whether by natural or artificial selection, when this relationship is not otherwise apparent from the hierarchy; the relationship should be the next known evolutionary ancestor, but it need not be an immediate ancestor, given that in the study of evolution, there are often gaps.

• Example
  [in the record for "donkey," which is a direct descendant of the "Equus asinus"]
• Relationship Type: descendant of
  Related Concept: Equus asinus

• 2840 <material made from species>
  Use to link a species or variety of animal or plant to the material derived from it. Link to the broadest applicable taxonomic level.

• Example
  [in the record for "tortoise shell," which is derived from various species of tortoises; link is made to the broadest applicable level, the taxonomic order]
• Relationship Type: derived from
  Related Concept: Testudines (order)

• Example
  [in the record for "poplar (wood)" which is derived from the genus Populus]
• Relationship Type: derived from
  Related Concept: Populus (genus)

3.5.2.3.2

Adding new Relationship Types
Most of the necessary Relationship Types should already be included in the controlled list. If you feel that you wish to add another Relationship Type to this list, consult with your supervisor.

3.5.3

Historical Flag

3.5.3.1

Definition
Flag indicating the historical status of the relationship of this AAT record to the Related Concept.

• Example

3.5.3.2

Values
C - Current, H - Historical, B - Both, N/A - Not Applicable, U - Unknown

3.5.3.3

RULES

• The default flag for the relationship is Current. In the AAT, it will rarely be necessary to use any flag other than Current. If you feel you should use another flag, discuss it with your supervisor.
  
  
  • Current: For relationships that still exist, even though they may have been established long ago, use Current. Most relationships in the AAT are current.
    
    
  • Historical: For a relationship that no longer exists because the meaning of the terms has changed. Do not use this flag without consulting your supervisor.
    
    
  • Both: For a relationship that is both current and historical. Do not use this flag without consulting your supervisor.
    
    
  • N/A: When Current or Historical are not appropriate to the situation. Do not use this flag without consulting your supervisor.
    
    
  • Unknown: This flag is used primarily for data that is loaded into VCS. Do not use this flag without consulting your supervisor.

3.5.4

Dates for Related Concepts

3.5.4.1

Definition
Dates delimiting the relationship between the two concepts.

• Example
  [for "First Dynasty (Egyptian)"]

3.5.4.2

Fields
There are three fields: Display Date, Start Date, and End Date.

3.5.4.3

Values
Display Date is a free-text field; values may be any ASCII character; no special characters or diacritics are allowed; diacritics must be expressed according to the codes in Appendix A.

• Start Date and End Date must contain valid years, as validated by VCS.

3.5.4.4

Sources
The dates should be determined using the same standard reference works that supply other information about the relationship.

3.5.4.5

Discussion
The Display Date for the relationship usually refers to a period or date, however, it may sometimes contain notes that do not explicitly make reference to a date. In such cases, the note should implicitly refer to a date or datable condition or event, because you are required to include a Start Date and End Date with every Display Date.

• Display dates are indexed with Start Date and End Date. Start and End Dates are controlled by special formatting; dates BCE are represented by negative numbers.
  

3.5.4.6

RULES

• Dates are not appropriate for most associative relationships in the AAT
  
  .
• When dates are appropriate, keep in mind that if you enter data in any of the three fields, you must enter data in ALL three of the fields.
  
  
• The dates appear on reciprocal links. That means that the same dates will appear in BOTH records. Write the Display Dates and assign Start and End Dates so that they will be correct and unambiguous in both records. Repeat the names of the concepts in the Display Date when necessary to avoid ambiguity.
  
  
  • Example
    [in the record for "rapiers"]
  • Relationship Type: thing(s) needing context is
    Related Concept: cup-hilts
    Display Date: cup-hilts were found on rapiers beginning in the 17th century
    Start Date: 1600 End Date: 9999
    
    
• A brief set of rules for Dates appears below. See also Appendix B and Dates for Names in Chapter 3.3 Names.

3.5.4.6.1

Display Date
A short set of rules appears below. For further discussion of Display Dates, see Appendix B.

• Follow the style of existing Display Dates.
  
  
  • Examples
    
  • Display Date: pertinent after 1520
    Start Date: 1520 End Date: 9999
    
    
  • Display Date: since the mid-18th century
    Start Date: 1730 End Date: 9999
    
    
  • Display Date: first used in Baroque paintings
    Start Date: 1590 End Date: 9999
    
    
• Do not use an initial capital, unless the word is a proper name.
  
  
• Do not use full sentences; do not end the display date with a period or any other punctuation.
  
  
• Ideally, the display date should refer, explicitly or implicitly, to a time period or date associated with the link between the Related Concepts.
  
  
• If a date is uncertain, use a broad or vague designation (e.g., ancient) or other terms such as ca. and probably to express uncertainty (e.g., ca., in the example below).
  
  
  • Example
  • Display Date: from ca. 1810 through 1940
    Start Date: 1800 End Date: 1940
    
    
• In some cases, the Display Date may be used to record unusual or important information about the Related Concept relationship (see the example below), but not referring explicitly to a date. However, dates should be implicit in the condition or event mentioned and you should have a period or date in mind, because - if you record a Display Date - Start and End dates are required.
  
  
  • Example
  • Display Date: pertinent for native inhabitants along the seacoast from Niantic Bay to the Connecticut River
    Start Date: 1400 End Date: 1900

3.5.4.6.2

Start Date and End Date
Use dates that most broadly delimit the span of time of the relationship referred to in the display date. In many cases, the years will be approximate years. When in doubt, it is better to estimate too broad a span rather than too narrow a span. See the Date Authority in Appendix B for approximate dates of historic events and entities; you should also consult other, related records in the AAT to establish dates.

• Dates must be expressed in the proleptic Gregorian calendar, which is the Gregorian calendar projected back in time before it came into existence.
  
  
• Express dates BCE by negative numbers, using a hyphen before the number. Do not use commas or any other punctuation.
  
  
  • Example
  • Display Date: relevant only for Banshan urns
    Start Date: -2800 End Date: -2300
    
    
• For current relationships, use the End Date 9999.
  
  
  • Example
  • Display Date: from 1810
    Start Date: 1810 End Date: 9999
    
    
• For very ancient dates, expressed as years ago or before present in the Display Date, translate these dates into approximate years in the proleptic Gregorian calendar for the Start and End Dates.

Last updated 18 December 2008
Document is subject to frequent revisions