Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.1]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ WorkItem ]
Entity Type
Independent_Entity[ x] or
Dependent_Entity[ ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ The WorkItem Entity or File is the unique record for each work (of art) in the database. The WorkItemID key field is the unique object (work) record. Because most attributes (fields) of which the WorkItem is composed are multi-valued, individual fields cannot be created for such values within the WorkItem Table.

Instead a series of dependent entities (Children to the WorkItem Parent) are defined to link to the WorkItem entity. In the AIC Subject Entities diagram three categories of the VRA Core fields are combined into a single link. Work Type (W.1.), Title (W.2.) and Subject (W.3.) because their terminologies so often overlap are combined into an associative entity called SubjTitleType.

A WorkItem record is require for each Work (object). WorkItems can be defined as related to one another through the WorkItem Recursion Entity (See WorkItem Recursion Entity Diagram).

One WorkItem (parent) is related optionally to many SubjTitleType (child) records.

FIELDS:
WorkItemID
WorkItemID is the key field for the WorkItem Entity. Its values are unique are are indexed. It is defined as a "long" datatype.
...
[Other Fields to be defined later.]

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.2]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ SubjTitleType ]
Entity Type
Independent_Entity[ ] or
Dependent_Entity[ x ] or
Associative_Entity[ x ] or
Subset_Entity[ ]
Entity_Description[ SubjTitleType is an associative entity that is used to record work's Subject terms, Work Type terms and Titles (as defined by the VRA Core Categories ver 2.0. Whereas most implementations of these three categories define three separate fields or three separate related files, SubjTitleType is used for all three kinds of identifications concurrently. The reason to merge these fields stems from the ambiguity created when trying to distinguish terms that are either subject terms, title terms or work type terms, and the consequential confusion on the part of users and catalogers alike when cataloging terms in these fields. In SubjTitleType the terms, no matter how they are classified, all fall within the same field: "SubjTitletypeTerm."

Here is how these entities function:
Each record in SubjTitleType has a manditory field called STTQualifier. In this field the cataloger chooses from among three values: Subject, Title or Work Type. Based on the content of the STTQualifier, the "SubjTitleTypeTerm" is taken from one of three authority files: 1) WorkTypeAuthority, 2) WorkTitleAuthority or 3)SubjectAuthority respectively.

Each "SubjTitleType" record may contain only one term linked to the WorkItem record, but one WorkItem record can have many SubjTitleType records attached to it. No link is manditory, however, but it is highly recommended to create at least one record each for Work Type, Title and Subject.

Although each SubjTitleType record contains a link to a record in an authority file for WorkType, Subject or Title, note that the term chosen from these authority files is copied over (redundantly) from the Authority File into the SubjTitleTypeTerm field. This should reduce the amount of associative processing in the database and prepares a field that can be queried across authority files.

It makes sense to combine these terms in the same field from the standpoint of efficiency in cataloging. These three fields are frequently cataloged together.

If an attempt is made to delete a term in an authority file (Title, Work Type, Subject, etc.) that is linked to a SubjTitleType record, that deletion should be prohibited.

FIELDS:
SubjTitleTypeID
Key Field for the SubjTitleType record.
WorkItemID
Foreign Key for SubjTitleType record. Links to WorkItemID key field in the WorkItem entity.
STTQualifier
Field determines whether the SubjTitleType record is being used to record a Subject, a Title, or Work Type (VRA core ver 2.0: W.16, W.2. or W.1. This field is required and must contain either the term "Work Type," "Title" or "Subject." Optionally we can permit this field to be blank and to fill the SubjTitleTypeTerm field (see below) with terms that are not authority controlled. In such cases the foreign keys that link to authority files must be empty.
DateAssigned
The date on which the record for SubjTitleType was created.
WhoAssigned
The name of the person who created or last edited this record. Ideally this value should be taken from an authority file of names and information about editors. This structure is not shown in the Subject Entities diagram.
ForDisplay
ForDisplay is a Boolean field that is used to identify which one of the records designated as Title, Work Type or Subject is to be used in short representations of the work of art. The rule for this field states that the boolean field can have only one "y" for WorkType, one for Title and one for Subject. It is to be used when it is in the interest of the user not to be confused by the underlying cataloging.
SubjTitleTypeTerm
SubjTitleTypeTerm is a text field used to record the single value taken from whichever authority file controls the record. Because the SubjTitleType entity is designed so that terms that do not belong to any authority may be listed, entry into the SubjTitleTypeTerm field may be made manually without verification by an authority file.
Normally when the SubjTitleType record is filled the cataloger should be able to refer to whichever authority file is appropriate, choose a term from it. That term and the link to the authority file would then be inserted into the record.
This entity does not at this time support the creation of composite terms -- terms fashioned out of several authority file entries.
When the value in the SubjTitleTypeTerm is not authority controlled, the fields designated as foreign keys linking to authority files should be empty.
This field should be indexed by word in order to aid in searches. In a query form when a user is prompted to "search for works by subject or title: enter keyword:" the search should work in the SubjTitleTerm field. All qualifying hits within the SubjTitleType entity should be shown as a list of different values with (ideally) the number of hits for each string rendered in the list. The user should be able to choose one or more (or all at once) of the strings presented and continue the query into a list list of objects through which the user is allowed one page one item at a time.
Citation
In some cases it will be appropriate to document through a citation listing the choices made in creating a SubjTitleType record. For example, an article might argue (not an infrequent occurrence) that the subject or iconography of a work is different than the one by which it is commonly known. A reference to that article would be appropriate. In such cases the Citation field is to be used in conjunction with the Bibliography entity. The Bibliography file is used to record the work or publication that is the source for the information, and a link to that record is established in the SubjTitleType record. In addition the Citation field is filled in with the specific page reference (or other specific reference) for that bibliographical item. In some cases the citation will record a conversation with a scholar. In these cases the conversation should be recorded in the bibliography file which should be flexible enough to record a variety of information sources.
The syntax used for the Citation field should correspond to common practice but no usage rules are being suggested here.
If the citation is to a web page the field should recognize that type of reference and become a hot link to the page. Even in such cases the web-page should be documented in the Bibliography file, which would include the date on which it was accessed.
WorkTypeAuthorityID
This is a link to the WorkTypeAuthority entity. One-to-many relationship. One WorkTypeAuthority record to many SubjTitleType records.
WorkTitleAuthorityID
This is a link to the WorkTitleAuthority entity. One-to-many relationship. One WorkTitleAuthority record to many SubjTitleType records.
WorkTitleTypeID
This is a link to the WorkTitleType entity.
Sometimes it is important to identify the kind of title or the source of a title used to characterize a work. The VRA Core guidelines name a few such instances. Typically, however, this data is not recorded, but it is useful to provide an opportunity to record (or link) Title Types. WorkTitleTypeID links to the authority file WorkTitleType. There is a one-to-many relationship between the WorkTitleType entity and SubjTitleType entity. One record in WorkTitleType may link to many SubjTitleType records.
Because it is used so rarely, no field is provided in SubjTitleType for this data; it relies on the link only.
BibliographyID
Link to the Bibliography entity key field. One-to-many relation. One Bibliography record to many SubjTitleType records.
SubjectAuthorityID
Link to the SubjectAuthority entity key field. Subject authorities are one of the more problematic areas in arts cataloging. There are several standard sets of authority files for subject access, some thesaurus-like. None are complete. It is expected that sources such as Iconclass or the LC subject headings will bused as general sources and that their components will be used to fashion a Subject Authority file for use of the AIC.
STTCatalogingStatus [new name: STTRecordStatus]
Provides a location for the cataloger to maintain control of the completeness or correctness of any record in this category. A set of standard term should be invented and employed for this purpose, and these should be coded into the entry form or linked by way of an editable file.
Because the AIC plans to accept data submitted from its users, it may be necessary to use the STTCatalogingStatus field to record the fact that it is submitted data. The Citation and Bibliography field may then be used to record the source of this donated data.
STTNote
This Memo field is used to comment on the nature of the record. It may be used to comment upon reader submission as described above or for any other information of significance. This note field differs from those attached to the Authority File entities in that this note field discusses the nature of the relationship established between the Work in WorkItem and the terms used in that relationship.

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.3]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ WorkTypeAuthority ]
Entity Type
Independent_Entity[ x] or
Dependent_Entity[ ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ WorkTypeAuthority is an authority file that records values consistent with the VRA Core Work Type (W.1.) that answers the question "What is the work's generic name?" Refer to the VRA guidelines for further definition of the values to be collected in this table. Most of the values will be collected from the AAT or other sources. And t is necessary to indicate the source (if any) from which the terms for Work Type have been taken. In thesauri like the AAT these terms are collected and arranged hierarchically. In the WorkTypeAuthority file no effort is to be made to arrange term hierarchically. For the most part the terms in this entity are those that are being used to classify the AIC collection or those that have a high likelihood of being so used. No effort is to be made to create an encyclopedic collection of Work Type terms.

There is a one-to-many relationship between WorkTypeAuthority and SubjTitleType. One record in WorkTypeAuthority can link to zero, one or more records in SubjTitleType.

Usage notes: Susan Williams, in her implementation of the VRA Core for this entity introduces a simple hierarchical relationship between terms. For example if the object classification type (same as work type) is "Painting" it may further be reclassified as "Altarpiece." I don't believe that this hierarchy is built into the authority file but is, rather, applied and invented as needed. The same effect (without the hierarchical structure) may be achieved by creating multiple Work Type records of any such work. Care must be taken, however, to define such multiple records with care. If "painting" is used as a worktype, and "altarpiece" used as a sub-type, then every painted altarpiece must also be classified as a painting, and other paintings, such as "portrait" must also be classified as a painting. A work classified as an "altarpiece," is is important to remember, is not necessarily always a member of the class of objects called "painting." An altarpiece may also be entirely sculptural. To define these terms hierarchically would require that "altarpiece" have dual parentage.

There is a tendency to try to create uniform usage when applying cataloging terms such as found in Work Type. While uniformity and the use of authorities helps create consistency and success in reporting and in the execution of queries, consistency and standardization also serves to defeat the success of queries executed without benefit of the knowledge of the authorities defined. Therefore is is often advisable to enter alternate and rejected terms for objects. Two fields are defined to aid in that process: WTTermAuthorized, a Boolean field, when entered as "y" or "true" or checked, simply designates that the term in the WorkTypeAuthority record is recognized as a valid and authorized term. If it is not checked, it is an alternate term. No effort is made however to show the hierarchical or associative relationship between terms. That is a project for another day.

FIELDS:

WorkTypeAuthorityID
This is the key field for the WorkTypeAuthority entity.

WorkTypeTerm
WorkTypeTerm is the value that is used to characterize the work described in the WorkItem Entity. This term is imported into the SubjTitleType entity by virtue of a lookup created by the link in SubjTitleType called WorkTypeAuthorityID (a foreign key). See note above on the use of alternate (see also) terms.

This field is required and is indexed for uniqueness.

WorkTypeTermSource
This field records the source for the term used. Most often it will have been taken from the AAT, but it will not be uncommon that its source is something other than the AAT, including terms of local usage.

WorkTypeTermDateAssigned
The date when the term record was created or last edited.

WorkTypeTermWhoAssigned
The name of the editor who worked on this record. Not indicated here, but at some time, this term should be turned into a link field that goes to a list of editors and individuals associated with the creation of the database.

WTTermAuthorized
See discussion, above. This boolean field indicates that the term represented has been taken as an authorized term for the purposes of this database. At some point this structure should be replaced by a hierarchically structured device that permits works to be linked to the structure of the hierarchy so that all sister terms are similarly accessible.

WTTermNotes
A memo field in which to describe usage notes and scope notes and other related data.

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.4]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ WorkTitleAuthority ]
Entity Type
Independent_Entity[ x ] or
Dependent_Entity[ ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ WorkTitleAuthority records the terms used to title works. Since a single work can have more than one title there is a one-to-many relationship between the SubjTitleType entity and the WorkTitleAuthority entity. One A WorkItem may have zero, one or many SubjTitleType records for Titles. One title term can be used in one or many records in the SubjTitleType entity.

No encyclopedic authority exists for art object work titles. But work titles often are composed of elements or entire terms taken from Work Types and from Subject lists. The difference between "Work Type" which is ultimately a classification entity and "Title" is subtle. "Title" refers to what a work has been called or named, and is therefore neither a classification entity nor a subject term, though titles may indicate or refer to both. Unlike books, art work titles are more often than not the consequence of custom, of provenance, of efforts to describe content. Only rarely (and recently) in the history of art have titles been given to works by their makers. A single work may have been given a variety of titles through the years and each title may be the result of the varying purposes of the titler. A common example used by catalogers to how how complex a title may be is the use of the word "untitled." A work may not be titled and therefore be called "untitled," or it may be titled by its maker as "untitled," hence its title is "Untitled." However most works of art through the ages are untitled by their makers, but we don't use the term "untitled" for these -- only for modern works to which no title has been awarded by custom.

The entity WorkTitleAuthority merely records titles that have been used to identify works of art. Some titles, such as "Madonna and Child" will be used for many works, other titles, such as "The Donni Madonna" will be applied to just one. Similar works may have varying titles that are the result of publication or exhibition decisions. Variations sometimes exist for no explicable reason, such as "Madonna and Child" or "Virgin and Child" the cataloger should follow the source text.

When a title merely repeats the term used in WorkTypeAuthority it may be useful to omit entering a value for title altogether.

The Entity WorkTitleType is defined in order to classify the kinds of titles registered. A link to a value in WorkTitleType may be made (optionally) from SubjTitleType when the SSTQualifier records "title" and the SubjTitleTypeTerm is a Title from WorkTitleAuthority.

Care must be taken not to use The title field to represent the subject of a work of art when that subject merely describes a detail of a larger work. In the AIC database there is a distinction made between whole works that are sub-divisions of larger works and works that are merely dependent details of whole works. The title entity is used to describe whole works only. For example, The "Baptistry, Florence," the "Gates of Paradise" on the Baptistry in Florence, and "The Story of Jacob and Esau" from the Gates of Paradise on the Baptistry in Florence are each whole works. But the "Head of Jacob" from "The Story of Jacob ..." etc. is a detail of a larger work and should be described in an entity reserved to characterize the "view" of a work represented by an image in the AIC collection.

Some titles are translated into the language of common use (English, here) and other titles are rendered as found on objects or by custom. Provision should be made (perhaps eventually if need be) to render the alphabets of the language of origin of titles and other data. Unicode may be chosen as a character set of choice.

FIELDS:

WorkTitleAuthorityID
This field is the key field for the entity and is used as the basis of a lookup that imports the WorkTitleTerm into the SubjTitleTypeTerm field in the SubjtitleType entity.

WorkTitleTerm
In this field is rendered the strings that form the titles of use. The data in this field should be indexed by word to ease the process of searching for authoritative values. It is a required, and is indexed for uniqueness

WorkTitleTermNote
Title that appear in this record are those that are validated by the fact that they have been used to identify or describe the work. These titles are not to be invented by the cataloger. Nonetheless on occasion it may be necessary to annotate a specific title, especially when that title is frequently used to refer to images of similar or different dispositions. Further, specific titles, such as "The Gero Crucifixion" may warrant annotation from time to time to explain the origin of the title. This note is not the same as a "scope note" of the sort used in vocabularies and thesauri to determine how the term is to be applied.
]

Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.5]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ WorkTitleType ]
Entity Type
Independent_Entity[ ] or
Dependent_Entity[ x ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ WorkTitleType is used to identify the nature of the title imported into SubjTitleType. It may only be used when the STTQualifier is "title" and when a WorkTitleTerm from the WorkTitleAuthority entity has been entered into SubtTitleTypeTerm field of the SubjtitleType entity.

The use of the WorkTitleTypeTerm is optional.

FIELDS:

WorkTitleTypeID
The key field for the entity WorkTitleType. Links to WorkTitleTypeID in SubjTitleType entity where it is a foreign key.

One-to-many relation between WorkTitleType and SubjTitleType. One record in WorkTitleType can link to multiple records in SubjTitleType entity. Link is optional. No link is allowed if the content of the attribute STTQualifier is anything else but "title." No link is necessary if the value in STTQualifier is "title."

WorkTitleTypeTerm
The content of this field is usually a short phrase that describes the origin or the nature of the title. For example "Traditional Title." or "Author's Title" or "Exhibit Title." If it is necessary to annotate the generic phrase use the field "WorkTitleTypeTermNote." If it is necessary to annotate or document the specific use of the title type or the title regarding the work, use the Citation/Bibliography fields in SubjTitleType entity.

This field is required and is indexed for uniqueness.

WorkTitleTypeTermNote
A memo field. See above for an explanation.

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.6]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ Bibliography ]
Entity Type
Independent_Entity[ x] or
Dependent_Entity[ ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ Bibliography entity will be defined as an expanded more inclusive entity than what Allan Kohl designed for the concordance Textbook entity. It is not defined here, but while it should be bibliographic in concept is should be able to identify all kinds of resources from which supporting data is derived. This includes, lectures, conversations, contributed opinions, web-pages, in addition to the traditional print resources.

Any time in this database that documentation is required, the documentation should look back to the Bibliography entity. However the exact location within that Bibliographic record should be kept with the record where it applies.

Over time the Bibliography file will grow to be a powerful research tool. Users will be able to go from images or opinions to Bibliography and from Bibliography to information about specific works. Today there is no tool like this at all for art historians and students.

Fields for this entity need to be defined.

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]

Academic Image Cooperative
Data Model Entity Definitions

SortOrder[2.7]

DIAGRAM_NAME[ AIC Subject Entities ]
Entity_Name[ SubjectAuthority ]
Entity Type
Independent_Entity[ x ] or
Dependent_Entity[ ] or
Associative_Entity[ ] or
Subset_Entity[ ]
Entity_Description[ Subject Authority development is the most irresolute of authority controls. Subject (VRA Core ver 2.0 W.16) which answers the simple question "What is this work about." can be very difficult to define and pin down because, as well known, subject can answer "What does this work depict? What is this work's meaning? and What is this work's significance." The answers to these questions may refer to religious and literary narratives, to figures taken out of narratives, to mythology, to portraiture, and even, according to the VRA Core guideline, to the pattern or type of brickwork or decoration. Following Erwin Panofsky, subject identification can be naive (without knowledge of allusions), can use associations to identify specific references or can refer to deeply held beliefs or political points of view.

Subject identification can be quite "subjective," and the meaning of works for one age can be quite different than it is for another age. Neither does the intended meaning given to the work by the creator warrant special authority since subject is not merely the identification of what was intended, or what was actually produced, but is also, as stated, what was understood by observers.

A number of subject guides have helped iconographers define subjects and have provided a way to refer to standard subjects outside of the means of describing them. Iconclass, for standard literary and religious themes has provided a coded system in a hierarchical environment that has proven quite useful if difficult to use. In addition the subject headings of the Library of Congress, of the Princeton Index of Christian Art is also used.

No expectation is made here for the images within the database to be fully classified or identified. Such a goal, at best is a cumulative task. The simple format offered here is intended to make the best use of the standard guides and yet permit use of conventional terms to identify subject.

Frequently the subject of a work is rendered in the same language as its Title, or even its Work Type. In such cases it is at the discretion of the cataloger to determine whether to repeat values from one category to another or simply to choose which location best suits the kind of term cataloged. If entered merely to ensure that a term will be hit during a query, because all Work Types, Titles and Subjects are placed in the same field, repetition for its own sake is not necessary. This author prefers Work Type to precede Subject and Subject to precede Title. In other words if a term suitable for Work Type is also appropriate for Subject, enter it in Work Type and not Subject. If a term suitable for Subject is also suitable for Title enter it in Subject and not in Title unless the Title term is known as the Title of a work. For instance Hals' "The Jolly Toper" is a known title, even though it can also be used as the subject.

The Subject entity is independent and is related to SubjTitleType in a one-to-many relation. A single subject record may be linked to zero, one or many SubjTitleType records. The value in the SubjectTerm field is loaded through a lookup into the SubjTitleTypeTerm field in the SubjTitleType entity.

Note on working procedure.
The editing procedure for the series of Subject entities should all work in a similar fashion, as follows.
1) From the WorkItem record, the editor indicates that a SubjTitleType record is going to be created. A window opens (with a link to the current WorkItem already established) that permits the editor to choose the type of record to be made: a) Work Type, b) Work Title, c) Subject or d) None.
2) If a, b, or c is chosen then the editor can enter a string into a search field that queries the appropriate (based on the choice above) authority file. A list of hits corresponding to the string is offered.
3) The user can backtrack to try another string. Or,
4) The user can select one of the terms offered.
5) The remaining terms are kept in memory in case other terms are going to be used for multiple links to the Work.
6) Requesting another query empties the memory cache and the process begins again.
7) Before each request the user can choose which value in the STTQualifier field is to apply, and consequently, which authority file is to be used.
8) This same process is to be used to create other links. In some cases the selected term will be imported through a lookup. In other cases only the link is preserved.
9) whenever there is a one-to-many relationship where the parent record is the dominant record on screen, all child records appear in a list with the most important and telling field showing.

Note: If a Subject Authority Term is used in SubjTitleType, that term cannot be altered without alerting the SubjTitleType record and asking for permission to alter it, at which time those records linked to the SubjectTerm field are updated automatically.

Sometimes the subject of an image or of a work is a geographical location or an archaeological site, e.g. The Acropolis, or the Roman Forum. A link to the GeographicNameAuthority entity allows lookups from that authority file into the subject file. This linkage enables the GeographicNameAuthority to link, not only to works from sites and to locations of repositories, but also to depictions of locations.

Special attention must be paid to the difference between the VRA core ver 2.0 Subject category (W16) and V8, the Visual Document Subject.

Useful Tool
Susan Williams inserted hot links to the AAT and other on-line authority files in the Authority worksheet of her Filemaker Pro database. This is a great idea and one that potentially can save a lot of time and frustration. Refer to Susan's database for layout suggestions.

FIELDS:

SubjectAuthorityID
Key field.

GeographicNameAuthorityID
Foreign Key linking to GeographicNameAuthority entity. See, further. Diagram 04.

SubjectTerm
SubjectTerm is the word or phrase used to identify the subject matter. Because more than one record from the SubjectAuthority entity can be attached to a single object, multiple subject terms can be linked to an object. Frequently subject terms are taken of authority guides lie Iconclass or the LC Subject Headings. Care must be taken not to represent the same subject multiple times with minute variations.
The value of this field is automatically entered into the SubjTitleTypeTerm field in the SubjTitleType entity.

SubjectTermSource
This field records the name of the authority reference from which the SubjectTerm has been taken.

At the beginning the terms for this field can be set as a set of terms from which to choose, coded into the application layer. If and when the number of sources begin to increase, it will be advisable to create a link to the Bibliography file and to enter the source data into that resource.

SubjectTermDateAssigned
The date on which this record was created or last edited. If the record is viewed but not edited, then the date should not be altered.

SubjectTermWhoAssigned
The name of the last editor of this field. The name of the editor should be entered automatically whenever the field is edited. The name of the previous editor should not be changed if no editing change has taken place.

SubjectTermSourceCode
Some iconographic sources (such as Iconclass) assign numerical or other codes to subject listings. This field is to be used to identify those codes if thought useful to do so.

SubjectTermType
Patterned after Susan William's "Subject Type" field, this field characterizes the kind of subject listed in SubjectTerm. For example in Susan's trial form one finds subjects classified as "Iconographic," "Historic Content," "Descriptive" (for Animals and Plants) "Associative Content" (for tromp l'oeil).

SubjectTermSubgroup
This field further divides hierarchically the categories presented in SubjectTermType. Examples include, for example, "Religious" or "Myth" under "Iconographic." Whatever system is used should have at least two broader classification levels in order to arrange and locate subject matter. Only the lowest-level term appears to the public user. The higher levels, until or unless they are edited systematically will just be used for internal administration of the Subject Authority file.

]
Entity_Connection_One-Name[ ]
Entity_Connection_One_Cardinality[ ] 1)1:1, 2)1:M, 3)M:M
Entity_Connection_One_Direction[ ] Parent / Child

Manditory[ ] or
Optional[ ]