APPENDIX B
CIMI-1 Attributes & Attribute Combinations

 

This appendix provides guidance for combining attributes in queries and on the occurrence of attribute types and default values for attribute types when they are not present in a query.

Occurrence of Attributes in Query

CIMI-servers should be prepared to receive a query containing only a search term and no attributes. In such cases, the server should default to behavior equivalent to receiving a search term with a Use attribute value 1016 (Any).

CIMI-clients should include one Use attribute value per term in a query. All other attribute types defined in the CIMI-1 Attribute Set are optional. In the case when a query contains a Use attribute value but contains no other attribute types, the recommended default for the server is:

Type 101 Authority has no explicit default. Instead, the server is to interpret the lack of an authority value in a query as the client "not saying" anything about the term. When such a case occurs, it is the server's choice in processing the term.

One (and only one) of each type of attribute may be sent in each operand of the Type 1 query. CIMI-clients can reduce ambiguity in the query by including all attributes types in a query to explicitly characterize a term. If a CIMI-server receives an attribute type or an attribute value it can not accept, it should reject the search with a diagnostic.

Client and server are required to support a minimum of one Boolean operator in each query .

AND and OR must be supported as Booleans in the Type 1 query. AND NOT is optional.

 

Attributes & Attribute Combinations

The following provides additional guidance on the attribute types. The support of attribute values, especially Use attributes, is governed by the conformance statement (see Section 7.6. Conformance). Other values may be optionally supported.

Type 1 (USE)

If the database being searched has elements (and/or indexes) that match the attribute as defined, the search should succeed and the appropriate result returned. If not, the search should be failed with the appropriate diagnostic (114 Unsupported Use attribute). No mapping from one attribute to another should be done. In the absence of any prior knowledge of the target, origins are required to support sending all defined values.

Type 2 (RELATION)

Value 3 (equal) should be accepted for all Type 1 attributes. For Use Attributes that support structure types date, year, local number or numeric string, the following additional relation attribute values should be supported:

1 = less than
2 = less than or equal
4 = greater or equal
5 = greater than

The relation attribute value 103 (AlwaysMatches) can be used with Use attribute 2020 (image) search for occurrences of records with images. Term is Null.

Type 3 (POSITION)

Value 3 (any position in field) should be accepted.

Type 4 (STRUCTURE)

The following Type 4 values may be combined with the Type 1 (Use) attributes listed.

Word (Value 2) and Phrase (Value 1)
4 = title
7 = ISBN
8 = ISSN
21 = subject heading
54 = Code language
58 = name geographic
62 = abstract
1003 = author
1004 = personal author
1016 = any
1018 = publisher
1031 = material type
2000 = award
2002 = collection
2004 = copyrightRestriction
2005 = creditLine
2007 = inscriptionMark
2008 = materialMedium
2009 = creatorNationalityCultureRace
2012 = processTechnique
2014 = creatorRole
2017 = stylePeriod
2023 = placeOfOrigin
2024 = objectID
2026 = owner
2027 = repositoryName
2028 = repositoryPlace
2029 = provenance
2030 = contentGeneral
2032 = objectName
2033 = objectTitle
2034 = relatedTextualReferences
2035 = creatorName
2038 = contextHistorical
2039 = contextArchaelogical
2040 = subject
2041 = creatorGeneral
2042 = associationGeneral
2043 = objectLanguage
2044 = condition
2045 = physicalDescription
2046 = who
2047 = what
2049 = where
2070 = fieldcollector
2072 = agePeriod
2073 = typeSpeciment
2074 = dimensions
2075 = quantity
2076 = relatedObjects
2077 = resource
2078 = wallTextLabel
2079 = administrativeEventGeneral
2080 = administrator
3000 = protectionStatus
3003 = spatialReferencingSystem
3007 = address
3008 = currentLocation
3009 = periodName

Date (Value 100)
31 = date of publication
32 = date of acquisition
2022 = dateOfOrigin
2036 = creatorDateOfBirth
2037 = creatorDateOfDeath
2048 = when
2071 = dateCollected
3001 = protectionDate

Year (Value 4)
31 = date of publication
32 = date of acquisition
2022 = dateOfOrigin
2036 = creatorDateOfBirth
2037 = creatorDateOfDeath
2048 = when
2071 = dateCollected
3001 = protectionDate

Numeric String (Value 109)
31 = date of publication
32 = date of acquisition
2022 = dateOfOrigin
2036 = creatorDateOfBirth
2037 = creatorDateOfDeath
2048 = when
2071 = dateCollected
2074 = dimensions
2075 = quantity
3001 = protectionDate

urx (Value 104)
1032 = doc-id

Type 5 (TRUNCATION)

Value 100 (do not truncate) should be accepted for all Type 1 attributes.

Type 6 (COMPLETENESS)

Value 3 (complete field) should be accepted.

Type 101 (AUTHORITY)

Value 1 (non-authoritative) should be accepted.


To Table of Contents

Next Section of Profile