Z39.50 Holdings Attribute Set

Version 1.0 April 2000

Prepared by Janifer Gatenby & Pieter Van Lierop, Geac Computers


The object identifier for this attribute set definition is 1.2.840.10003.3.16

Objective

The objective of this document is to create an attribute set for searching holdings information.

This attribute set is cast in the new attribute architecture.

 

Use of the holdings attribute set

The holdings attribute set may be used in several ways.

Direct search on a holdings database

The attributes can be used to search a holdings database directly. The search response would indicate number of records in the search response. This would be the number of holdings records matching the search request. If the GRS-1 or XML record syntax with the Holdings schema is requested in the present response, the target would assemble all holdings for one bibliographic record together and present only one record. It would also include the bibliographic record in the response, depending on the element specification or element set defined in the present request. Note that the origin does not need to provide the name of the bibliographic database as the target would already know it.

As part of a search on a bibliographic database

A search on a bibliographic database includes bibliographic search attributes and holdings search attributes. Note that the origin does not need to provide the name of the holdings database as the target would already know it. The search response includes a count of all bibliographic records matching the search criteria. It does not indicate a holdings count. If the GRS-1 or XML record syntax with the Holdings schema is requested in the present response, then the target would assemble all holdings associated with the matching bibliographic records and present one Holdings record per bibliographic record. The Holdings record may contain holdings that did not match the holdings search criteria as well as those that did. Bibliographic records that matched the bibliographic search criteria but did not include holdings that match the holdings search criteria would not be included in the response.

As a search element within eSpec-q

A search is performed on the bibliographic database. A count of bibliographic records is returned in the search response. The origin then sends a present request using eSpec-q containing both holdings search attributes (value restrictor) and an indication of the desired contents of the results records (element selector). The results from a present request using the holdings schema (record syntax either GRS-1 or XML) would include one holdings record per bibliographic record, and the holdings record would only contain holdings that matched the value restrictor.

3. Relation with other attribute sets

 

Bib1 and Bib2 Attribute sets

 

Searches may be conducted that combine bibliographic search attributes. The following attributes from Bib1 are examples of Use attributes that are likely to be combined with holdings access point attributes.

'7 ISBN

'8 ISSN

'12 Local number

'1007 Identifier--standard

'1011 Date / time added

'1012 Date / time modified

'1032 Doc-id

The bib-1 and bib-2 attributes are used to search bibliographic information and the holdings attribute set is used to search holdings information. This seems obvious, however it is less clear when for example there is an Access Point called "Institution". In that case, a bib-2 search on an Institution pertains to information available through the bibliographical record and a holdings search on a Location pertains to holdings information.

 

Utility Attribute Set.

For all attribute types other than access point and semantic qualifier, the Utility attribute set is used. Moreover, the following Access Point values within the Utility attribute set may be useful for search on holdings records:

(Quotes from /z3950/agency/attrarch/util.html:)

"Record Date
A date associated with the record. May be used in conjunction with a semantic qualifier, such as: "date/time created", "date/time last modified", or "date/time last reviewed", or it may be used unqualified, in which case it it a date/time associated with the record, assigned by the server.

(...)

Local Control Number of Record
A string (integer or character string) assigned by the server that uniquely identifies a record in the database.

(...)

Record Format
The format of the database record. This access point may be used to limit the results to include records of a specific format.

  

4. Explanation of the attribute set tables

Table 1 outlines the Access Points and Semantic Qualifiers according to the new Z39.50 attribute architecture.

Practically, this means that the client application or origin can choose to search in a generic or more precise way.

2 examples:

Search on location

 

Search

Comment

Generic

Access Point: Location

Term: CENTRAL

This would retrieve holdings where CENTRAL occurred, whether in the locationName, institutionOrSiteId, countryId or regionId etc.

Precise

Access Point: Location

Semantic Qual: InstitutionOrSiteId

Term: "CENTRAL"

This would retrieve holdings where CENTRAL occurred specifically in the institutionOrStieId.

 

 Search on a certain periodical, issue 3 of 1988

 

 

Search

Comment

Generic

Access Point: EnumerationAndChronology Term: "1988, 3"

Search could retrieve holdings where "3" occurs at issue level or at another enumeration level such as part or volume or at another chronological level such as day number.

Precise (enumeration level known)

Access Point: Chronology

Semantic qual: specificChronology

Term: "1988" AND

Access Point: Enumeration

Semantic qual: EnumLevel

Term: "2" AND

Access Point: Enumeration

Semantic qual: specificEnumeration

Term: "3"

Search will only retrieve holdings where the second enumeration level (assuming that there is a first, e.g. volume) equals 3.

 

Precise (enumeration level unknown)

Access Point: Chronology

Semantic qual: specificChronology

Term: "1988" (data type External using Z39.50 Date / Time) AND

Access Point: Enumeration

Semantic qual: EnumCaption

Term: "issue" AND

Access Point: Enumeration

Semantic qual: specificEnumeration

Term: "3"

Search will only retrieve holdings where the enumeration caption equals issue and enumeration equals 3.

Note that this could lead to retrieval failure if the enumeration caption is stored differently in the database, e.g. abbreviated.

 

Use should be made of truncation in the Expansion / Interpretation attribute from the Utility Attribute Set so that a search using Chronology and Enumeration would succeed when it matches part of the database record.

Example: When the client application asks for specificChronology = 7 (data type month which is July), it should match the July/August issue of a given periodical.

 

Explanation of the information in table 1

In general, the values / names / definitions / semantics in this table stem from the Holdings Schema. 

The values for Access Points and Semantic Qualifiers are unique.

  

Table 1: Attribute Set holdings in the New Attribute Architecture

 

column 1: Description of attribute values of attribute type Access Point

column 2: List of attribute values of attribute type Access Point

column 3: Description of attribute values of Semantic Qualifier

column 4: List of attribute values of Semantic Qualifier

column 5: Semantics to the Value in column 4; or: Enumeration of possible values of Term for the value in column 4 (the numbers in brackets indicate GRS-1 tag path for the Holdings Schema).

 

(1)

Access Point

(2)

Value

(3)

Semantic Qualifier

(4)

Value

(5)

Semantics; or: Enumeration of Term values

Local Control number of record

4 (Utility Set)

bibPartId

1000

Unique identifier for a bibliographic part in a database. (4,40)

targetCopyId

1001

Unique identifier for a specific copy in a target database (4,41)

copyId

1002

Indicates a specific copy of a bibliographic item or part. It could be a copy number or other unique identification scheme used by the institution and/or sublocation (4,59)

locator

1003

a shelfmark, call number or electronic locator for all or any copies or pieces of a bibliographic item. (4,9 & 4,60)

targetPieceId

1004

Unique identifier for a specific piece in a target database (4,75)

pieceDesignation

1005

Identifies a single piece associated with the copy reported. The piece designation may be an identification number such as a barcode or accession number. (4,76)

Location

1

targetLocationId

1011

Unique identifier for a physical site in a target database (4, 26)

institutionOrSiteId

1012

A person, library, organization, consortium or physical site holding an item or from which access is given. May or may not be an authoritative code. When authoritative, the source for the institution code should conform to the specified countrys Symbols of Libraries or similar definitions. (4,27)

locationName

1013

Indicates the complete name of the physical site, i.e. name of institution followed, optionally, by the name(s) of one or many of its sub-divisions. (4,28)

isilCode

1014

A sites International Standard Institution Identifier for Libraries and Related Organizations (ISIL) code (4,29)

countryId

1015

An authoritative two- or three-character code that identifies the country of a physical sites location. (4,31)

regionId

1016

A non-authoritative identifier or name that identifies a specific geographic area within the country of the reporting physical site (4,32)

networkAddress

1017

Network (or internet) address of a physical site. Network address should be a fully qualified host name or dotted-format IP address, followed optionally by a TCP/IP port number (4,33)

EnumerationAndChronology

2

   

Free text string that an origin sends to a target to parse (4,45 + 4,46)

Enumeration

3

enumLevel

1031

A number indicating the sequence of an enumeration element in relation to other similar elements in an enumeration and chronology group. (4,93)

enumCaption

1032

A label describing the contents and level of an enumeration element. (4,94)

If the enumeration level is unknown, Enumeration caption is sent in conjunction with enumeration- sent if level unknown. Provides the caption describing this division level. (e.g.: "v.", "no.", "pt.", etc.)

specificEnumeration

1033

Number, letter or word identifying a unit of an item that is published in parts and identifying the relationship of the part to the whole item. (4,95)

Chronology

4

chronLevel

1041

A number indicating the sequence of a chronological element in relation to other similar elements in an enumeration and chronology group. (4,96)

chronCaption

1042

A label describing the contents and level of a chronological element. (4,97)

specificChronology

1043

A phrase expressing a time period identifying a unit of an item which is published serially in parts and identifying the relationship of the part to the whole item. (4,98)

The data type may be the external Z39.50 Date and Time or numeric or characterString

alternativeEnumeration

5

enumLevel

1051

A number indicating the sequence of an enumeration element in relation to other similar elements in an enumeration and chronology group. (4,93)

enumCaption

1052

A label describing the contents and level of an enumeration element. (4,94)

If the enumeration level is unknown, Enumeration caption is sent in conjunction with enumeration. Provides the caption describing this division level. (e.g.: "v.", "no.", "pt.", etc.)

specificEnumeration

1053

Number, letter or word identifying a unit of an item that is published in parts and identifying the relationship of the part to the whole item. (4,95)

alternativeChronology

6

chronLevel

1061

A number indicating the sequence of a chronological element in relation to other similar elements in an enumeration and chronology group. (4,96)

chronCaption

1062

A label describing the contents and level of a chronological element. (4,97)

specificChronology

1063

A phrase expressing a time period identifying a unit of an item which is published serially in parts and identifying the relationship of the part to the whole item. (4,98)

Pagination

7

paginationStart

1071

Numbering of the pages of an item or part of an item indicating the start point in a range

paginationEnd

1072

 Numbering of the pages of an item or part of an item indicating the end point in a range.

Extent of Holdings

8

completenessDesignator

1081

Indicates how much of the published part of a serial unit or multipart unit is held by an institution . (4,15 4,53 4,64)

Term values:

infoNotAvailable (0),

complete (1),

incomplete (2),

veryIncompleteOrScattered (3),

notApplicable (4)

retentionDesignator

1082

Indicates the period for which the bibliographic units are held by the reporting institution . (4,17 4,66)

Term values:

infoNotAvailable (0),

other (1),

asReplacedByUpdates (2),

sampleIssueRetained (3),

untilReplacedByPreservationFormat (4),

untilReplacedByCumulationOrOther (5),

limitedRetention (6),

noRetention (7),

permanentRetention (8)

physicalFormDesignator (or: Format)

9

   

Specifies the physical medium or type of material of the bibliographic unit. (4,44)

Example term values (refer to Holdings Schema for a complete list):

microform (hh),

multiplePhysicalForms (mm),

text (tt),

textLargePrint (tb),

textBraille (tc),

visualMaterial (vv),

videorecording (vc),

map (ma),

physicalFormUnspecified (zu),

Status

 

10

 

acquisitionStatusDesignator

1091

Indicates whether a bibliographic item or part has been or will be acquired by the reporting institution. (4,16 4,65)

Term values: infoNotAvailableOrApplicable (0)

other (1)

completedOrCeased (2),

onOrder (3),

currentlyReceived (4),

notCurrentlyReceived (5)

CircStatus

1092

Contains the circulation status of a piece .

(4,99)

Example term values: (for a complete list refer to Holdings Schema)

available (0), undefined (1),

onOrder (2), notAvailable (3),

onLoan (4), onLoanUntilRecall (5),

inProcess 6), recalled (7),

onHold (8),

waitingToBeMadeAvailable (9),

inTransit (10),

claimedReturnedOrNeverBorrowed (11),

   

reservationStatus

1093

Indicates whether or not a physical unit or a piece is reserved, and the stage of the active reservation . (4,113)

Term values:

currentReservation (0),

returnedReservation (1) onReservationShelves (2),

expiredReservation (3)

servicePolicy

11

Lending

1101

unknown (0),

will (1)

willNot (2)

Reproduction

1102

unknown (0),

will (1)

willNot (2)

Reservation

1103

unknown (0),

will (1),

willNot (2)

PieceUseRestrictions

12

   

Contains information about any restrictions on the use of the piece. (4, 102). Term values:

undetermined (0), notForLoan (1),

inLibraryUseOnly (2),

overnightOnly (3),

useOnlyInControlledAccessRoom (4),

renewalsNotPermitted (5),

limitedCircShortLoanPeriod (6)

limitedCircNormalLoanPeriod (7),

limitedCircLongLoanPeriod (8),

termLoan (9),

semesterLoan (10),

availableForSupplyWithoutReturn (11)

 

 

 

 

Searching Serials and Multi-Part Items

 

Different Citation Versions

How does an origin construct a search for a serial or multi-part citation?

There are three variables:

For example, the publisher creates:

  1. Publisher's version
  2. European journal of medicine Volume 3, Number 5 July 1998 (publisher's version)

  3. Database version
  4. The target database records the pattern as:

    Enumeration level 1 = Vol. (Caption)

    Enumeration level 2 = No. (Caption)

    Chronological level 1 = Month

    Chronological level 2 = Year

    Cataloguing practice is to describe the pattern faithfully according to the publisher's version. However, cataloguers may sometimes abbreviate captions.

    Hence

    European journal of medicine Vo1. 3, No. 5 July 1998 (target database version)

  5. Searcher's version

The searcher may have the following citation

European journal of medicine 3 (5) 1998, 45-89 (searcher's citation)

There are numerous different conventions for constructing serial citations. These can differ across domains and from one institution's style guide to another. Captions may be abbreviated, normalised to a language or omitted. The publisher's actual captions are rarely used. All these are attempts to normalise data that actually is not normalised and can vary for each published title. The client then has to determine from the citation known to the searcher how to form a request with the holdings attributes.

Searching When the Pattern is Known

In this case, the enumeration and chronology elements should be used as search attributes:

e.g. searching for 3 (5) 1998, 45-89

853 a (level 1enumeration) = Volume

853 b (level 2 enumeration) = Number

853 i (level 1 chronology) = Month (invisible caption)

853 j (level 2 chronology) = Year (invisible caption)

Search created for:

Enumeration level 1 = 3

Enumeration level 2 = 5

Chronological level 2 = 1998

The client (origin) has two possibilities. It can either parse the citation or it can present the citation pattern elements for the end user to complete. If the chronological elements are incomplete, it may be possible for the client to parse the citation. However, if the enumeration elements are incomplete or completeness is unknown, and especially if they lack captions, then the client cannot determine the enumeration level. Therefore, it must either present the user with the pattern elements to complete or it must omit enumeration and only use chronology.

 

Example search:

Access Point

Semantic Qualifier

Term

Comment

Enumeration

 

 

 

Chronology

EnumLevel

specificEnumeration

enumLevel

specificEnumeration

chronLevel

specificChronology

"1" AND

"3" AND

"2" AND

"5" AND

"2" AND

"1988"

Where level is known, it is used in preference to caption which is less precise.

 

 

 

Searching When the Pattern is Unknown

Constructing a search without a pattern record

The origin can:

Example:

Access Point

Semantic Qualifier

Term

Comment

Enumeration

 

 

 

Chronology

EnumCaption

specificEnumeration

enumCaption

specificEnumeration

chronLevel

specificChronology

"V." AND

"3" AND

"No." AND

"5" AND

"2" AND

"1988"

Where level is unknown, caption is used.

Caption is imprecise (is it V. or Vol. or Volume?) so use of caption could lead to retrieval failure.

 

 

 

Requesting a pattern record

The client should be able to send a present request for the citation pattern (enumeration and chronology pattern). The pattern for any one serial title may change over time, e.g. when a serial publication changes its frequency, it will most likely add or lose an enumeration level. Therefore, the response needs to include all patterns relevant to a serial title indicating the date range of each pattern. The present request would be for GRS-1 or XML syntax with the element set name or eSpec indicating the pattern schema defined below.

Format of Pattern Record

Suggested data structure for the data returned in response to a request for a pattern record:

Element

Occurrence

Repeatable

Data Type

recordId

Mandatory

No

InternationalString

title

Optional

No

InternationalString

pattern

Mandatory

Yes

Pattern

Definition of Pattern:

Element

Occurrence

Repeatable

Data Type

enumeration

Mandatory if Chronology absent, else Optional

Yes

Enumeration

alternativeEnum

Optional

Yes

Enumeration

chronology

Mandatory if Enumeration absent, else Optional

Yes

Chronology

alternativeChronology

Optional

Yes

Chronology

patternStartDate

Optional (Mandatory if more than one pattern)

No

Z3950Date

patternEndDate

Optional

No

Z3950Date

Definition of Enumeration:

Element

Occurrence

Repeatable

Data Type

enumDataFormat

Optional

No

InternationalString

enumLevel

Mandatory if enumerationCaption absent, else optional

No

Integer

enumCaption

Mandatory if enumerationLevel absent, else optional

No

InternationalString

Definition of Chronology

Element

Occurrence

Repeatable

Data Type

chronDataFormat

Optional

No

InternationalString

chronLevel

Mandatory if chronologyCaption absent, else optional

No

Integer

chronCaption

Mandatory if chronologyLevel absent, else optional

No

InternationalString

Examples:

Enumeration data format, e.g. Roman numerals, Arabic numerals etc.

Enumeration caption, e.g. Volume, Part, Tome, Band, Numéro

Chronology caption, e.g. season, year

Chronology data format, e.g. Eté / Printemps / Autonne / Hiver, YYYY etc.

* The Chronology data format includes valid values if there is a definite set or it includes the format itself.

 

 

Sequence of Transactions

 

Therefore, where the origin needs the pattern in order to be able to construct a search for a citation it would perform the following transactions in sequence

 

Search for title

Present citation pattern

Present with eSpec-q using 'value restrictor' elements, e.g. enumeration levels supplied from citation pattern and 'elementSelector', e.g. ESN C3.