7. Z39.50 Specifications

This section specifies the required services available from Z39.50. The specifications address the use of attribute sets for searching cultural heritage information resources and the processes by which a client requests both content and syntax of retrieval records from a server. The terms CIMI-clients and CIMI-servers refer to Z39.50 clients and servers that support this Profile.

7.1. Protocol Version

The Profile requires CIMI-clients and CIMI-servers to support Z39.50 Version 3 as specified in Z39.50-1995 [13].

7.2. Z39.50 Objects

The Profile addresses the following Z39.50 objects by reference to registered Object Identifiers (OIDs). For information on Z39.50 OIDs, see Z39.50 Maintenance Agency [18]. Requirements regarding CIMI-client and CIMI-server support of these objects differ according to the Conformance Levels described in Section 7.6. Conformance.

Object     OID
Bib-1 attribute set     1.2.840.10003.3.1
CIMI-1 attribute set     1.2.840.10003.3.8
Bib-1 diagnostic set     1.2.840.10003.4.1
GRS-1 record syntax     1.2.840.10003.5.105
SUTRS record syntax     1.2.840.10003.5.101
USMARC record syntax     1.2.840.10003.5.10
Digital Collections Schema     1.2.840.10003.13.3
CIMI Schema     1.2.840.10003.13.5
TagSet-M     1.2.840.10003.14.1
TagSet-G     1.2.840.10003.14.2
Collections TagSet     1.2.840.10003.14.5
CIMI TagSet     1.2.840.10003.14.6

7.3. Communication Services

When the Transmission Control Protocol (TCP) is used as the transport service, the specification for Z39.50 implementations’ use of TCP is found in RFC 1729, Using the Z39.50 Information Retrieval Protocol in the Internet Environment [11].

7.4. Z39.50 Services

The Profile requires CIMI-clients and CIMI-servers to support four Z39.50 (Version 3) services:

No additional services are required for conformance to this Profile. CIMI-clients and CIMI-servers optionally may use other Z39.50 services.

Standard Z39.50 Init Service negotiation procedures control the use of all services.

7.4.1. Init

CIMI-clients supporting this Profile may use the IDAuthentication parameters to transmit authentication information (e.g., userid and password). CIMI-servers supporting this Profile may or may not require authentication. The Profile specifies no other security requirements.

Although Z39.50 segmentation of records is not required, CIMI-clients and CIMI-servers should negotiate a reasonable value of the Exceptional-record-size parameter. For example, a server might negotiate a maximum record size large enough to allow it to transmit any of its own records.

7.4.2. Search

The Profile requires CIMI-clients and CIMI-servers to support Z39.50 Type 1 queries (i.e., general purpose Boolean query structures).

It is recommended, but not mandatory, that searching is performed case-insensitively.

7.4.2.1. Attribute Sets

The Profile requires CIMI-clients and CIMI-servers to support the CIMI-1 Attribute Set (see Appendix A for the CIMI-1 Attribute Set).

CIMI-1 uses the six Attribute Types defined in the Bib-1 Attribute Set. Semantics for Bib-1 attributes can be found in Attribute Set Bib-1 (Z39.50-1995): Semantics (September 1995) [2].

CIMI-1 defines two new attribute types, Authority and Charset. Use attribute values defined for the CIMI-1 Attribute Set are derived in part from the CIMI Access Points [8] and other relevant cultural heritage information guidelines and standards. Appendix C provides semantics for CIMI-1 Use attribute values.

CIMI-clients and CIMI-servers must recognize the Bib-1 Attribute Set OID (1.2.840.10003.3.8.) to the extent that a CIMI-client may pass the OID in a query and CIMI-servers may receive and process a query with the OID. Conformant servers will support selected Use Attribute values according to Section 7.6. Conformance. "Support" in this context means that the CIMI-server will recognize the Use Attribute value(s), and searches using Use Attribute values listed for a Conformance Level will always result in a valid result set (which could contain 0 hits). This implies that all implementations supporting this Profile must have search capabilities for Use Attribute values listed in each conformance level claimed. A CIMI-server may, if appropriate to its database, support additional attributes from other Z39.50 Attribute Sets.

CIMI-servers are required to return appropriate diagnostics when they receive a query containing attribute types and values not supported. Appropriate diagnostics are listed in Bib-1 Diagnostic Set and include, for example:

See Section 7.5. Diagnostic Messages for use of the unsupported attribute diagnostic.

Appendix B provides additional information and guidance on the CIMI-1 Attribute Types and their values, including default values for attribute types and valid attribute combinations.

7.4.2.2. Named Result Sets

The Profile requires support for named result sets. CIMI-servers will support a minimum of two concurrent result sets.

7.4.2.3. Date Searching

Dates occurring as search terms should, when possible, be transmitted in normalized form and using the Structure Attribute (Attribute Type = 4) with value "normalized date" (Structure Attribute Value = 5) with the search term. The normalized form is described in the document, Attribute Set Bib-1 (Z39.50-1995): Semantics (September 1995) [2].

A date may be preceded by a minus sign (-) to indicate a BC date. In this case, only the year number may be specified, but it may be any number of digits long.

If a client is not able to normalize the date, then it may transmit it in whatever form it has, without the Structure Attribute. The CIMI-server should interpret all date searches, with or without the structure attribute, as best they can.

7.4.3. Retrieval

This section provides specifications and procedures for using Z39.50 to return records in response to a query. The Profile specifies a CIMI Tag Set, a CIMI Schema, and an Abstract Record Structure (ARS) for the Retrieval Record. The ARS specifies the use of elements from tagSet-M, tagSet-G, the Collections Tag Set, and the CIMI Tag Set.

The Profile is a companion profile to the Z39.50 Profile for Access to Digital Collections [10] (referred to as the Digital Collections Profile) and uses the Digital Collections Schema's object descriptive record in a conformant manner. The Profile specifies only those elements of the Digital Collections Schema that are pertinent to the goal of retrieval (rather than navigation of digital collections). CIMI-clients and CIMI-servers supporting this Profile optionally may use, in a conformant manner, other Digital Collections Profile specifications.

7.4.3.1. The Retrieval Record: An Overview

This Profile defines an ARS for the Retrieval Record to support three levels of semantic interoperability by partitioning the record into three levels of elements. In order of occurrence, the record contains elements for:

  1. Generic Level of Semantic Interoperability: At the beginning of a retrieval record there may occur generic elements (in the form of tagSet–M and tagSet–G elements). A Z39.50 client may recognize and process these elements even if it does not recognize any specific schema.
  2. Digital Collections Schema Level of Semantic Interoperability: The Digital Collections Schema is assumed, and a Digital Collections Schema–aware Z39.50 client can recognize and process these elements.
  3. CIMI Schema Level of Semantic Interoperability: The CIMI Schema is assumed, and a CIMI Schema-aware Z39.50 client can recognize and process the remaining elements in the record.

This partitioning allows for wider semantic interoperability between CIMI-servers and Z39.50 clients that do not support this Profile.

At the generic level of semantic interoperability, a generic Z39.50 client might search databases that include collection and object descriptive records as well as other types of records. By including generic elements at the top level of a retrieval record, such a client will be able to partially, if not fully, process these retrieval records.

At the Digital Collections level of semantic interoperability, a Z39.50 client aware of the Digital Collections Schema may perform a distributed search across multiple domains and over multiple collections including those provided by a CIMI-server. It may retrieve a record from the CIMI-server, and discover that there is a potential object of interest, even though the Z39.50 client is not able to fully process the record.

At the CIMI level of semantic interoperability, a Z39.50 client aware of the CIMI Schema should be able to fully process the complete retrieval record defined in this Profile.

To accommodate these levels of semantic interoperability, it is necessary to insert the element schemaIdentifier (tagSet-M element 1) at both interoperability boundary points within a retrieval record. The Digital Collections Schema identifier occurs when the record changes from the generic to the Digital Collections level, and the CIMI Schema identifier occurs when the record changes from Digital Collections level to the full CIMI level of semantic interoperability.

The term "abstract record structure" is commonly used within the context of a specific schema. For this Profile, the ARS for the Retrieval Record transcends the CIMI schema.

7.4.3.2. Tag Types

The tag types referenced in the ARS for the Retrieval Record are:

Tag Type Definition
1 Elements from tagSet-M defined in Z39.50-1995 (Appendix TAG, TAG.2.1.). A server may include elements from tagSet-M at its discretion, and a client may ignore any tagSet-M elements except schemaIdentifier. See also TagSet -G and -M Elements [19]
2 Elements from tagSet-G defined in Z39.50-1950 (Appendix TAG, TAG.2.2.). A server may include elements from tagSet-G not listed in the Abstract Record Structure for the Retrieval Record, and a client may ignore them. See also TagSet -G and -M Elements [19]
3 Reserved for tags locally defined by a target. Servers that send string tags for locally-defined elements will use tagType 3 to identify those elements. String tags should be used only if available elements defined in tagSet-M, tagSet-G, Collections Tag Set, and CIMI Tag Set are not adequate.
4 Elements from Collections Tag Set defined in Z39.50 Profile for Access to Digital Collections [10]
5 Elements from CIMI Tag Set as defined in this Profile (see Section 7.4.3.3.)

At the generic level of semantic interoperability, the ARS for the Retrieval Record assumes the use of Tag Types 1, 2, and 3. At the Digital Collections level of semantic interoperability, the ARS for the Retrieval Record assumes the use of Tag Types 1, 2, 3, and 4. At the CIMI level of semantic interoperability, the ARS for the Retrieval Record assumes the use of Tag Types 1, 2, 3, 4, and 5.

7.4.3.3. The CIMI Tag Set

This section defines the CIMI Tag Set by identifying the tag value, element name, and recommended ASN.1 datatype for each element. The CIMI Tag Set is a registered object: OID = 1.2.840.10003.14.6. Semantics for these elements can be found in Appendix C.

Tag Element ASN.1 Datatype
1 repositoryName InternationalString
2 subject InternationalString
3 objectID InternationalString
4 nationalityCultureRace InternationalString
5 materialMedium InternationalString
6 reserved  
7 creditLine InternationalString
8 dateOfBirth InternationalString
9 dateOfDeath InternationalString
10 role InternationalString
11 placeOfOrigin InternationalString
12 processTechnique InternationalString
13 dimensions InternationalString
14 stylePeriod InternationalString
15 provenance InternationalString
16 relatedObjects InternationalString
17 quantity InternationalString
18 award InternationalString
19 reserved  
20 collection InternationalString
21 reserved  
22 inscriptionMark InternationalString
23 reserved  
24 association MoreInfo (see Section 7.4.3.6.)
25 content MoreInfo (see Section 7.4.3.6.)
26 repositoryPlace InternationalString
27 reserved  
28 mrObject MrObject (see Section 7.4.3.6.)
29 rendition Rendition (see Section 7.4.3.6.)
30 resource OCTET String, External, or InternationalString
31 objectName InternationalString
32 objectTitle InternationalString
33 bibliographicTitle InternationalString
34 reserved  
35 relatedTextualReferences InternationalString
36 creatorInfo CreatorInfo (see Section 7.4.3.6.)
37 reserved  
38 owner InternationalString
39 contentGeneral InternationalString
40 reserved InternationalString
41 place InternationalString
42 event InternationalString
43 activity InternationalString
44 reserved  
45 dateOfOrigin InternationalString
46 contextHistorical InternationalString
47 contextArchaelogical InternationalString
48 copyrightRestriction InternationalString
49 creatorGeneral InternationalString
50 associationGeneral InternationalString
51 objectLanguage InternationalString
52 condition InternationalString
53 physicalDescription InternationalString
54 wallTextLabel InternationalString
55 protectionStatus InternationalString
56 protectionDate InternationalString
57 spatialReferencingSystem InternationalString
58 xCoordinateInSpatialReferencingSystem InternationalString
59 yCoordinateInSpatialReferencingSystem InternationalString
60 fieldCollector InternationalString
61 dateCollected InternationalString
62 agePeriod InternationalString
63 typeSpecimen InternationalString
64 address InternationalString
65 periodName InternationalString
66* administrativeEvent AdministrativeEvent (see Section 7.4.3.6.)
67* administrativeEventType InternationalString
68 administrativeEventGeneral InternationalString
69 administrator InternationalString

* Note: The elements administrativeEvent and administrativeEventType had tag numbers 1000 and 1001 respectively in the Aquarelle Profile. These have been reassigned numbers in the CIMI Tag Set. Clients should be prepared to receive the original Aquarelle Profile tag numbers.

7.4.3.4. The CIMI Schema

The CIMI Schema uses elements defined in the CIMI Tag Set as well as tags from other registered tag sets. The CIMI Schema defines the constructed datatypes identified in the CIMI Tag Set and describes an abstract record structure that provides the layout and ordering of elements for the retrieval record. See Section 7.4.3.6 for the constructed datatypes. The CIMI Schema is a registered object: OID = 1.2.840.10003.13.5.

The Schema addresses the need to retrieve one or more "images" (where "images" can be any type of digital resource including audio, video, images) that may be available in one or more versions (e.g., differing resolutions, color-depth, and sampling rate). The element mrObject occurs for each instance of an image, and each available version occurs in the repeating subelement rendition. Descriptive metadata may be provided for each instance of mrObject and for each instance of rendition (thus metadata and multiple renditions). Since information provided in the subelements for mrObject may apply to subelements in the element rendition (e.g., the value of the title subelement in mrObject is the same for that subelement in rendition), the subelements of rendition can assume by inheritance the values from mrObject subelements. Only in cases where a subelement in rendition takes on a value different from its parallel subelement in mrObject is there a need to include that subelement in the rendition element.

Within rendition, the subelement resource carries either a uniform resource locator (URL) for the image or the actual bits that comprise the image (see Section 7.4.3.13. Retrieval of Images . The subelement resource has information provided by appliedVariant (see Section 7.4.3.11. Use of GRS-1).

7.4.3.5. The Abstract Record Structure for the Retrieval Record

The ARS for the Retrieval Record addresses important goals of the Profile. First, the tagSet–G and tagSet-M elements at the beginning of the retrieval record allow semantic interoperability with Z39.50 clients that have no knowledge of either the Digital Collections Schema or the CIMI Schema. CIMI-servers will include, at the beginning of a retrieval record, the tagSet-G elements corresponding to the Dublin Core elements as listed below. Other tagSet–G and tagSet-M elements can occur at the beginning or elsewhere in the the record.

Second, the ARS maintains alignment with the Digital Collections Profile in that it adopts the structure of that Profile’s object descriptive record. The resources addressed by the CIMI Profile are modeled as digital objects. This Profile treats all content and descriptive information as digital objects, and to this extent does not exploit fully the functions of the Digital Collections Profile (e.g., for navigation of collections).

Notational notes: The "occurrence" column contains information related to optionality and repeatability according to the following:

The Occurrence column may also include conditional information. The Description column points to reference for semantics and may also indicate usage guidance and/or indicate required values for selected schema elements in the ARS.

The datatype for each schema element will be found in the relevant documents that define the various external tag sets (e.g., TagSet -G and -M Elements [19] and Z39.50 Profile for Access to Digital Collections [10]) or in Section 7.4.3.3. that defines the CIMI Tag Set.

For ease of reading, the ARS for the Retrieval Record is separated into three component parts, each aligned with a specific level of semantic interoperability identified above.

Level I. Generic Level of Semantic Interoperability

Z39.50 clients and servers need only share knowledge of tagSet-G and tagSet-M elements to process this top level of the Retrieval Record.

TagPath Element Occurrence Description
(1,14) localControlNumber 1 see tagSet-M
(2,1) title 0+ see tagSet-G
(2,2) creator 0+ see tagSet-G
(2,32) contributor 0+ see tagSet-G
(2,8) date 0+ see tagSet-G
(2,170) description 0+ see tagSet-G
(2,28) identifier 0+ see tagSet-G; the server can choose the data to return in this element. For example, it may return a URL for a rendition of an image or a pointer to other pages that are appropriate from the perspective of the server.
(2,22) type 0+ see tagSet-G
(2,20) language 0+ see tagSet-G
(2,21) subject 0+ see tagSet-G
(2,31) publisher 0+ see tagSet-G
(2,27) format 0+ see tagSet-G
(2,33) source 0+ see tagSet-G
(2,30) relation 0+ see tagSet-G
(2,34) coverage 0+ see tagSet-G
(2,29) rights 0+ see tagSet-G

 

Level II. Digital Collections Schema Level of Semantic Interoperability

The Digital Collections Schema is assumed and indicated by the schemaIdentifier. A Digital Collections Schema–aware Z39.50 client can recognize and process these elements.

TagPath Element Occurrence Description
(1,1) schemaIdentifier 1 see tagSet-M; First occurrence of this element in a retrieval record has Required Value = OID of Digital Collections Schema (1.2.840.10003.13.3).
(4,1) typeOfDescriptiveRecord 1 see tagSet-Collections; Required Value = 2 (object descriptive record)
(4,4) objectInfo 1 see tagSet-Collections
(4,4)(4,12) typeOfObject 1 see tagSet-Collections;see tagSet-Collections; Required Value = 1 (object is a digital object)
(4,4)(4,13) categoryOfObject [0,1] see tagSet-Collections;
Permissible Values
cimi:unspecified
cimi:cataloging record
cimi:image record
cimi:object record
(4,4)(4,14) digitalObject 1 see tagSet-Collections
(4,4)(4,14)(4,29) actualDO 1 see tagSet-Collections

 

Level III. CIMI Schema Level of Semantic Interoperability

The CIMI Schema is assumed and indicated by the occurrence of the schemaIdentifier. A CIMI Schema-aware Z-client can recognize and process these elements.

TagPath Element Occurrence Description
(4,4)(4,14)(4,29)(1,1) schemaIdentifier 1 see tagSet-M; Second occurrence of this element in a retrieval record has Required Value = OID of CIMI Schema (1.2.840.10003.13.5).
(4,4)(4,14)(4,29)(5,31) objectName 0+ see Appendix C
(4,4)(4,14)(4,29)(5,32) objectTitle

1+

In each retrieval record, the element objectTitle must occur if the record is an object record or an image with text record OR if there is no occurrence of the element bibliographicTitle

see Appendix C
(4,4)(4,14)(4,29)(5,33) bibliographicTitle 1+

In each retrieval record, the element bibliographicTitle must occur if the record is a bibliographic record OR if there is no occurrence of the element objectTitle

see Appendix C
(4,4)(4,14)(4,29)(5,49) creatorGeneral 0+ see Appendix C
(4,4)(4,14)(4,29)(5,36) creatorInfo 0+ Constructed datatype CreatorInfo (Section 7.4.3.6); see also Appendix C
(4,4)(4,14)(4,29)(5,60) fieldCollector 0+ see Appendix C
(4,4)(4,14)(4,29)(5,1) repositoryName 0+ see Appendix C
(4,4)(4,14)(4,29)(5,26) repositoryPlace 0+ see Appendix C
(4,4)(4,14)(4,29)(5,38) owner 0+ see Appendix C
(4,4)(4,14)(4,29)(5,7) creditLine 0+ see Appendix C
(4,4)(4,14)(4,29)(5,2) subject 0+ see Appendix C
(4,4)(4,14)(4,29)(5,3) objectID 0+ see Appendix C
(4,4)(4,14)(4,29)(5,5) materialMedium 0+ see Appendix C
(4,4)(4,14)(4,29)(5,12) processTechnique 0+ see Appendix C
(4,4)(4,14)(4,29)(5,13) dimensions 0+ see Appendix C
(4,4)(4,14)(4,29)(5,11) placeOfOrigin 0+ see Appendix C
(4,4)(4,14)(4,29)(5,45) dateOfOrigin 0+ see Appendix C
(4,4)(4,14)(4,29)(5,61) dateCollected 0+ see Appendix C
(4,4)(4,14)(4,29)(5,62) agePeriod 0+ see Appendix C
(4,4)(4,14)(4,29)(5,63) typeSpecimen 0+ see Appendix C
(4,4)(4,14)(4,29)(5,14) stylePeriod 0+ see Appendix C
(4,4)(4,14)(4,29)(5,65) periodName 0+ see Appendix C
(4,4)(4,14)(4,29)(5,15) provenance 0+ see Appendix C
(4,4)(4,14)(4,29)(5,17) quantity 0+ see Appendix C
(4,4)(4,14)(4,29)(5,18) award 0+ see Appendix C
(4,4)(4,14)(4,29)(5,20) collection 0+ see Appendix C
(4,4)(4,14)(4,29)(5,22) inscriptionMark 0+ see Appendix C
(4,4)(4,14)(4,29)(5,51) objectLanguage 0+ see Appendix C
(4,4)(4,14)(4,29)(5,52) condition 0+ see Appendix C
(4,4)(4,14)(4,29)(5,53) physicalDescription 0+ see Appendix C
(4,4)(4,14)(4,29)(5,55) protectionStatus 0+ see Appendix C
(4,4)(4,14)(4,29)(5,56) protectionDate 0+ see Appendix C
(4,4)(4,14)(4,29)(5,57) spatialReferencingSystem 0+ see Appendix C
(4,4)(4,14)(4,29)(5,58) xCoordinateInSpatialReferencingSystem 0+ see Appendix C
(4,4)(4,14)(4,29)(5,59) yCoordinateInSpatialReferencingSystem 0+ see Appendix C
(4,4)(4,14)(4,29)(5,64) address 0+ see Appendix C
(4,4)(4,14)(4,29)(5,16) relatedObjects 0+ see Appendix C
(4,4)(4,14)(4,29)(5,35) relatedTextualReferences 0+ see Appendix C
(4,4)(4,14)(4,29)(5,50) associationGeneral 0+ see Appendix C
(4,4)(4,14)(4,29)(5,24) association 0+ Constructed datatype MoreInfo (Section 7.4.3.6); see also Appendix C
(4,4)(4,14)(4,29)(5,39) contentGeneral 0+ see Appendix C
(4,4)(4,14)(4,29)(5,25) content 0+ Constructed datatype MoreInfo (Section 7.4.3.6); see also Appendix C
(4,4)(4,14)(4,29)(5,46) contextHistorical 0+ see Appendix C
(4,4)(4,14)(4,29)(5,47) contextArchaelogical 0+ see Appendix C
(4,4)(4,14)(4,29)(5,48) copyrightRestriction 0+ see Appendix C
(4,4)(4,14)(4,29)(5,54) wallTextLabel 0+ see Appendix C
(4,4)(4,14)(4,29)(2,9) displayObject 0+ see Appendix C;
appliedVariant may be used with element; default is text
(4,4)(4,14)(4,29)(5,68) administrativeEventGeneral

0+

see Appendix C
(4,4)(4,14)(4,29)(5,66) administrativeEvent 0+ Constructed datatype AdministrativeEvent (Section 7.4.3.6); see also Appendix C
(4,4)(4,14)(4,29)(5,69) administrator

0+

see Appendix C
(4,4)(4,14)(4,29)(5,28) mrObject 0+

Occurs for each "image" associated with record.
If the element mrObject occurs, at least one occurrence of rendition and its subelement resource are mandatory.

Constructed datatype MrObject (Section 7.4.3.6); see also Appendix C

 

7.4.3.6. Constructed Datatypes

The CIMI Schema defines five constructed datatypes: CreatorInfo, MrObject, Rendition, MoreInfo, AdministrativeEvent.

Datatype CreatorInfo is structured as follows:

Tag Element Occurrence Description
(2,7) name 1 see tagSet-G
(5,4) nationalityCultureRace 0+ see Appendix C
(5,8) dateOfBirth 0+ see Appendix C
(5,9) dateOfDeath 0+ see Appendix C
(5,10) role 0+ see Appendix C

 

Datatype MrObject is structured as follows:

Tag Element Occurrence Description
(2,1) title 0+ see tagSet-G
(2,2) creator 0+ see tagSet-G
(2,32) contributor 0+ see tagSet-G
(2,8) date 0+ see tagSet-G; The element date may be returned as either GeneralizedTime or EXTERNAL datatypes. See Z3950DateTime [21] for specifications when using EXTERNAL.
(2,17) description 0+ see tagSet-G
(2,22) type 0+ see tagSet-G
(2,20) language 0+ see tagSet-G
(2,21) subject 0+ see tagSet-G
(2,31) publisher 0+ see tagSet-G
(2,27) format 0+ see tagSet-G
(2,33) source 0+ see tagSet-G
(2,30) relation 0+ see tagSet-G
(2,34) coverage 0+ see tagSet-G
(2,29) rights 0+ see tagSet-G
(5,29) rendition 1+

If the element mrObject occurs, at least one occurrence of rendition and its subelement resource is mandatory.

Renditions are to be ordered in the GRS record with the smallest size/lowest resolution listed in the first occurrence of rendition.

see below for constructed datatype Rendition; also see Appendix C

 

Datatype Rendition is structured as follows:

Tag Element Occurrence Description
(5,30) resource 1 see Appendix C; appliedVariant must be used with element
(2,1) title 0+ see tagSet-G
(2,2) creator 0+ see tagSet-G
(2,32) contributor 0+ see tagSet-G
(2,8) date 0+ see tagSet-G; The element date may be returned as either GeneralizedTime or EXTERNAL datatypes. See Z3950DateTime [21] for specifications when using EXTERNAL.
(2,17) description 0+ see tagSet-G
(2,22) type 0+ see tagSet-G
(2,20) language 0+ see tagSet-G
(2,21) subject 0+ see tagSet-G
(2,31) publisher 0+ see tagSet-G
(2,27) format 0+ see tagSet-G
(2,33) source 0+ see tagSet-G
(2,30) relation 0+ see tagSet-G
(2,34) coverage 0+ see tagSet-G
(2,29) rights 0+ see tagSet-G

 

Datatype MoreInfo is structured as follows:

Tag Element Occurrence Description
(2,7) name [0,1] see tagSet-G
(5,41) place [0,1] see Appendix C
(5,42) event [0,1] see Appendix C
(5,43) activity [0,1] see Appendix C
(2,17) description [0,1] see tagSet-G

 

Datatype AdministrativeEvent is structured as follows:

This structure should not be used to record events in the life of the object described by the record but only events in the life of the record itself. The intent is that each AdministrativeEvent structure describes as single administrative event in the life of an electronic record, such as creation, folder-publishing, etc. The date of the event, the person responsible, and that person's role are all recorded together.

Tag Element Occurrence Description
(5,67) administrativeEventType 1 Takes on values such as "Creation" and "Fst-publ"
(2,8) date 1 Date of event
(2,2) creator 1 Person responsible for event
(5,10) role 1 Takes on values such as "Editor," "Publishr" (sic), and "Reviewer"

 


To Table of Contents

Next Section of Profile