Danish ISO 20775 profile for holdings requests

Identifier: http://biblstandard.dk/ill/dk/docs/Danish_ISO_20775_profile_for_holdings_requests.htm

Publication: 2 March 2014

Last update: 2 March 2014

Creator: Tommy Schomacker

Approved by danZIG ILL working group

Published by The Danish Agency of Culture

1. Introduction

This profile has to be used in connection with ISO 20775 Information and documentation -- Schema for holdings information; it doesn’t replace ISO 20775.

All Mandatory elements are mentioned in the profile. This profile doesn’t prescribe the use of not mandatory elements not mentioned below.

Also based on this standard is “Guidelines for exchange of bibliographic data and holdings information between a library acquisitions client and local library systems in Danish libraries” (danZIG-specification 09).

2. Scope

The profile is intended for the following use cases.

· Presentation of holdings information in a client (e.g. bibliotek.dk and netpunkt)

ILL request

These use cases are based on holdings received as a result of a holdings request identifying a library and a bibliographic record describing a resource or group of resources.

The profile shows which parts of the schema it is recommended to deliver in the resulting xml document. But the profile does not restrict the use of the schema to these parts only.

3. Profile description

3.1 General

The profile presupposes that the holdings request identifies a resource or a group of resources on bibliographic level by use of record id either from DanBib or from the requested library catalogue.

The profile identifies three scenarios determined by characteristics of the bibliographic record.

1. Record describes a resource which is circulated as a unit

2. Record describes a resource and multiple parts circulated independently

3. Record describe a periodical with individual issues not identified

These scenarios offer two ways of handling multi volume works (scenario 1 and 2) and two ways of handling issues of a periodical (scenario 2 and 3). More scenarios may be added later.

The library may have a number of interchangeable copies of the resource, but the single copy is not addressed in the answer.

The resulting xml document shall for all three scenarios contain identification of library to which the holdings applies.

Data element	ISO 20775 element	Value
Identification of library	holdings.holding.institutionIdentifier.value	<ISIL-code for library>
Identification of library	holdings.holding.institutionIdentifier.typeOrSource.text	”ISIL”

In addition to this is for each of the scenarios below mentioned the required and the recommended data elements to be returned to support the specific scenario.

3.2 Record describes a resource which is circulated as a unit

The scenario comprise among others:

· Works published as a single volume, described in a single record

· The single volumes of a multivolume work, described in separate records for each volume

· Articles described in separate analytic records

The rest of the data is given in a holdingSimple element.

Data element	ISO 20775 element	Value
Id for ordering	holdings.resource.resourceIdentifier.value	text
Id for ordering	holdings.resource.resourceIdentifier.typeOrSource.text	“SUFFICIENT”
Total number of copies	holdings.holding.holdingSimple.copiesSummary. copiesCount	positive integer (*)
Number of copies available	holdings.holding.holdingSimple.copiesSummary.status. availableCount	nonnegative integer
Expected dispatch date	holdings.holding.holdingSimple.copiesSummary.status. earliestDispatchDate	date and time

(*) Mandatory. If unknown set to ”1”.

3.3 Record describes a resource and multiple parts circulated independently

This scenario covers among others multivolume works or combined materials catalogued as a single bibliographic record. It may also be used if the record has a full specification of the issues held for a given periodical.

This scenario uses the holdingStructured element. All data is given in one set-element with a component-element for each part. The id for ordering is for each component given in a pieceIdentifier element. The value is a string and the qualifying text indicates that this value is sufficient to fulfill an ILL-request.

Data element	ISO 20775 element	Value
	holdings.holding.holdingStructured.set.label	”all sets”

Each component element contains the following.

Data element	ISO 20775 element	Value
Id for ordering	holdings.holding.holdingStructured.set.component. pieceIdentifier.value	text
Id for ordering	holdings.holding.holdingStructured.set.component. pieceIdentifier.typeOrSource.text	“SUFFICIENT”
Text used to select part	holdings.holding.holdingStructured.set.component. enumerationAndCronology.text	text (*)
Availability	holdings.holding.holdingStructured.set.component. availabilityInformation.status.availabiltyStatus	0: unknown 1: available 2: not available 3: possibly available
Expected dispatch date	holdings.holding.holdingStructured.set.component. availabilityInformation.status.dateTimeAvailable	date and time

(*)The text should be compiled by the responding system in a way, which supports presentation of the part in a meaningful sequence, e.g. by insertion of blank characters in front of digits.

3.4 Record describes a periodical with individual issues not identified

This scenario covers the situation, where the bibliographic record has information of a periodical only, and maybe completeness and intervals, but not the individual issues.

The id for ordering corresponds to the record id and is therefore in this Danish profile given in a resource element. The value is a string and the qualifying text indicates that this value needs additional information about issue to fulfill an ILL-request. Further data is given in a set element. The endingEnumAndChronology element may be omitted in the last interval.

Data element	ISO 20775 element	Value
Id for ordering	holdings.resource.resourceIdentifier.value	Text
Id for ordering	holdings.resource.resourceIdentifier.typeOrSource.text	“INSUFFICIENT”
	holdings.holding.holdingStructured.set.label	”all sets”
Completeness	holdings.holding.holdingStructured.set.completeness	0: info not available 1: complete 2: incomplete 3: incomplete or scattered
Interval (may be repeated)	holdings.holding.holdingStructured.set. enumerationAndCronology.startingEnumAndChronology.text	text (*)
Interval (may be repeated)	holdings.holding.holdingStructured.set. enumerationAndCronology.endingEnumAndChronology. text	text (*)

(*)The text should be compiled by the responding system in a way, which supports presentation of the intervals in a meaningful sequence, e.g. by insertion of blank characters in front of digits.

4. References

[1] ISO 20775:2009 Information and documentation -- Schema for holdings information

http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39735

[2] Danish ISO 18626 profile for ILL transactions

http://biblstandard.dk/ill/dk/docs/Danish_ISO_18626_profile_for_ILL_transactions.htm

[3] Bekendtgørelse om undtagelse fra pligten til anmeldelse af visse behandlinger, som foretages for den offentlige forvaltning (§ 12):

https://www.retsinformation.dk/Forms/R0710.aspx?id=843&exp=1

Annex A. ISO 20775 overview

Informative Annex

A.1 Introduction

The schema is located at Library and Congress, http://www.loc.gov/standards/iso20775/

ISO 20775 defines a format for delivery of holdings data covering traditional holdings information as well as statistical and actual information on the usage of all types of resources, physical and electronic, all types of resource format such as printed text, visual images, sound recordings, videos, electronic media and resources published or issued once such as monographs or those published serially or in part.

The schema is primarily designed to be included in responses to queries. Two primary query types have been identified and targeted, based on availability (main focus) and historical usage. In the context of delivery, holdings responses need to provide sufficient, precise information regarding an individual copy or set of copies to indicate whether or not a delivery request would be successful.

The ways to request the data and how data is gathered and assembled to populate the schema is outside the scope of the standard.

A.2 Root element

The schema contains one root element, holdings, with two subelements, holding (M,R) and resource (O,R), described in subsequent sections.

A.3 holdings.ressource

The resource element describes the resource to which the holding element applies.

· resourceIdentifier (O,R) – identification of resource

form (O) – physical or digital characteristics of resource

partDetail (O) – information on how the resource form part of an entirety

The resource element is repeatable. If repeated the holding element will apply to the union of resources addressed by the resource elements. The standard gives the following examples for use of more ressource elements:

· a serial representing multiple issues published over a given time period or an open-ended time period;

all expressions and manifestations of a work, e.g. all different translations, all different editions;

a group of resources retrieved by a search and represented as a result set.

A.4 holdings.holding

The holding element is mandatory and repeatable. Each holding element contains a group of subelements (institutionIdentifier (M), physicalLocation (O,R), physicalAddress(O,R) og electronicAddress (O,R)).

The description of the holdings is given in either holdingSimple or holdingStructured. It is the responding server that determines whether holdingSimple or holdingStructured is appropriate to a given set of resources. The reason for this is that one resource may be held as a unit at one institution but as multiple parts at another, or a requester may believe a request to be for a single part whereas it is actually a multiple-part resource.

A.4.1 holdings.holding.holdingSimple

The holdingSimple element is appropriate where the pieces are interchangeable, at least in the context of a particular query. Monographs, monographic works, and fully cited serial articles would typically use the simple version.

The copiesSummary (M) element may specify number of copies, availability etc.:

· copiesCount (M) – total number of copies; is set to 1 if the number is unknown

status (O,R)

o availableCount (O) – number of copies available for use or delivery

o availableFor (O) – code specifying how the resource is available

§ 0: unspecified

§ 1: loan

§ 2: physical copy

§ 3: digital copy

§ 4: online access

§ 5: reference look-up

§ 6: other

earliestDispatchDate (O) – date and time when the resource will be ready for delivery

reservationQueueLength (O) – length of reservation queue

onOrderCount (O) – number of copies ordered, but not ready for circulation yet

The copyInformation (O,R) element may give information on specific copies. Use of this element requires knowledge of bar code numbers or accession numbers for these copies.

A.4.2 holdings.holding.holdingStructured

By replying with holdingStructured the responding server is indicating that there are multiple parts; for example a multivolume work or a periodical. The holdings data is given in a set element, identified by a label element. The value ”all sets” is reserved for data, that applies to all set.

For periodicals with individual issues not described the completeness and enumerationAndCronology elements is useful. For multivolume works and periodicals with individual described volumes or issues may be addressed in component elements. The completeness, enumerationAndCronology and component elements are described below.

A.4.2.1 holdings.holding.holdingStructured.set.completeness

The completeness element may take the values

· 0 (info not available)

· 1 (complete)

· 2 (incomplete)

· 3 (incomplete or scattered)

A.4.2.2 holdings.holding.holdingStructured.set.enumerationAndCronology

The enumerationAndCronology element can define an interval. If the interval is up to today, the endingEnumAndChronology element is omitted. ISO 20775 shows how these elements may be mapped from MARC 21 format for holdings data, fields 853-855 (Captions and Pattern), 863-865 (Enumeration and Chronology) and 866-868 (Textual Holdings Statement). DanMARC2 do not have a standardized holdings format. But the main idea is, that the interval may either be defined by text strings or structured elements defining hierarchial level, caption and value.

The figure shows the enumeration element. The chronology element is structured the same way.

Example enumeration:

level	caption	value
2	årgang	5
4	hæfte	11

The alternative text could be “Årgang 5, hæfte 11”. If it shall be possible to sort such texts properly for presentation, it will be necessary to follow a strict syntax when forming the text; insert blanks in front of numbers etc.

Example chronology:

level	caption	value
1	år	1995
4	hæfte	11

The alternative text could be “År 1995, hæfte 11”.

A.4.2.3 holdings.holding.holdingStructured.set.component

For the component element pieceIdentifier, enumerationAndCronology og availabilityInformation is commented below.

A.4.2.3.1 holdings.holding.holdingStructured.set.component.pieceIdentifier

The pieceIdentifier element identifies the specific part (e.g. volume 4) of the current set. If the set has the reserved value ”all sets” as label, the data is a consolidated summary for all set, and the pieceIdentifier element therefore identifies an arbitrary copy of the given volume.

A.4.2.3.2 holdings.holding.holdingStructured.set.component.enumerationAndCronology

The enumerationAndCronology element is used to specify how the specific part (e.g. volume 4) is part of an entirety. The alternative text and structured is defined in the same way as in the interval specification (see section 4.2.2.2 above).

A.4.2.3.3 holdings.holding.holdingStructured.set.component.availabilityInformation

The availabilityInformation element may contain information on the availability of the resource.

· status (O,R)

availabilityStatus (O) – code that indicates availability

0: unknown

1: available

2: not available

3: possibly available

availableFor (O) – code specifying how the resource is available

0: unspecified

1: loan

2: physical copy

3: digital copy

4: online access

5: reference look-up

6: other

dateTimeAvailable (O) – date and time when the resource will be ready for delivery

Annex B. Examples

Informative Annex

B.1 Record describes a resource circulated as a unit

<?xml version="1.0" encoding="UTF-8"?>

</typeOrSource>

</institutionIdentifier>

</status>

</copiesSummary>

</holdingSimple>

</holding>

<text>SUFFICIENT</text>

</typeOrSource>

</resourceIdentifier>

</resource>

</holdings>

B.2 Record describes a resource and multiple parts circulated independently

B2.1Multivolume work with two volumes (bind 1 and bind 2)

<?xml version="1.0" encoding="UTF-8"?>

</typeOrSource>

</institutionIdentifier>

<set>

<text>SUFFICIENT</text>

</typeOrSource>

</pieceIdentifier>

</enumerationAndChronology>

</status>

</availabilityInformation>

</component>

<text>SUFFICIENT</text>

</typeOrSource>

</pieceIdentifier>

</enumerationAndChronology>

</status>

</availabilityInformation>

</component>

</set>

</holdingStructured>

</holding>

</holdings>

B2.2 Periodical with two issues (hæfte 1 and hæfte 2)

<?xml version="1.0" encoding="UTF-8"?>

</typeOrSource>

</institutionIdentifier>

<set>

<text>SUFFICIENT</text>

</typeOrSource>

</pieceIdentifier>

<text>hæfte 1</text>

</enumerationAndChronology>

</status>

</availabilityInformation>

</component>

<text>SUFFICIENT</text>

</typeOrSource>

</pieceIdentifier>

<text>hæfte 2</text>

</enumerationAndChronology>

</status>

</availabilityInformation>

</component>

</set>

</holdingStructured>

</holding>

</holdings>

B.3 Record describes a periodical with individual issues not identified

B.3.1 Complete

<?xml version="1.0" encoding="UTF-8"?>

</typeOrSource>

</institutionIdentifier>

<set>

</set>

</holdingStructured>

</holding>

<text>INSUFFICIENT</text>

</typeOrSource>

</resourceIdentifier>

</resource>

</holdings>

B.3.2 Incomplete (årgang 3 to 5, from årgang 8 and forward)

<?xml version="1.0" encoding="UTF-8"?>

</typeOrSource>

</institutionIdentifier>

<set>

<text>årgang 3</text>

</startingEnumAndChronology>

<text>årgang 5</text>

</endingEnumAndChronology>

</enumerationAndChronology>

<text>årgang 8</text>

</startingEnumAndChronology>

</enumerationAndChronology>

</set>

</holdingStructured>

</holding>

<text>INSUFFICIENT</text>

</typeOrSource>

</resourceIdentifier>

</resource>

</holdings>