Alphanumeric Fields
Fields marked as text in the schema may include any alphanumeric (scalar or string) values.
Fields marked as number in the schema may include any numeric (scalar) value. Institutions may choose to limit the types of numbers that can be used in a field (e.g. whole numbers only if describing number of artifacts; two decimal places for valuation).
Identification Number Fields
Field marked as controlled number in the schema may include any alphanumeric values (scalar or string), or may be filled by the identification number generator. Values created by the generator may be over-written by a user. Patterns in the generator are set by the implementing institutions.
Vocabulary Fields
Fields marked as authority or controlled list in the schema are linked to existing vocabularies, authority files (one or more vocabularies), or controlled lists (non-hierarchical or flat vocabularies). Institutions may configure the display option (auto complete, predictive text, dropdown), default value, validation requirements, and source vocabularies for a vocabulary-enabled field. Static controlled lists may only have terms added programatically; Dynamic term lists may be edited via the UI.
If the associated field on a data entry form is configured to allow terms to be added, then the user will be able to add a term to the source vocabulary list. If the associated field on a data entry form is configured to allow terms to be added AND the field is associated with multiple sources, then the user will be able to add a term and identify the source vocabulary list the term should be added to.
Date Fields
Fields marked as calendar date in the schema can accept a single date. See the Formatting and Validation section of the Date and Time service description for a more comprehensive discussion of single-date formatting. The date may be selected from the date-picker widget or entered manually.
Fields marked as structured date can accept structured date information, including earliest/single, latest, degree of certainty, and association.
Group and Repeatable Fields
Fields in a schema may be part of a group, such as a title and its translation. The first field in a group is represented normally in the schema, additional fields that are part of a group are prefixed with a >.
Example:
Other number | An alternative number for an object other than the Object number. |
> Other number type | A description of an Other number assigned to an object. |
Fields in a schema may be: repeatable; part of a group, the entirely of which is repeatable; or individually repeatable within a group.
Visualizations of the group and repeatability requirements of a given schema can be difficult in the wiki; spreadsheets are attached to each schema page that attempt to clarify these relationships.
Field Repeatable
Schema example
Information Group | Information Unit | Definition | Field Type | Field Repeatable | Group Repeatable |
|---|---|---|---|---|---|
| Brief description | A text description of an object in approximately one sentence; normally used for administrative and identification purposes. It records the most important information from a number of separate descriptive units of information. | Text | Yes |
|
How it looks
Group Repeatable
Schema example
Information Group | Information Unit | Definition | Field Type | Field Repeatable | Group Repeatable |
|---|---|---|---|---|---|
| Object production organization | An Organization involved in the design, creation or manufacture of the object. | Name authority: Organization | No | Yes |
| Object production organization - role | The role or activity performed by a organization in the conception, design, or production of a work. | Text | No |
|
How it looks
Sub-field Repeatable
Schema example
Information Group | Information Unit | Definition | Field Type | Field Repeatable | Group Repeatable |
|---|---|---|---|---|---|
| Title | The name assigned to an object or group of objects by the artist/creator or collector at the time of origin or subsequent titles either specifically assigned or generally understood to refer to it. | Text | No | Yes |
| > Title language | The language used for the Object title. | Controlled list: static | No |
|
| > Title type | The nature of the Title recorded. | Controlled list; static | Yes |
|
| > Title translation | A translation into the organization's first language of a title as recorded. | Text | Yes |
|
| >> Title translation language | The language used for the Object title translation. | Controlled list; static | Yes |
|
How it looks