Look-up of holdings information

Identifier: http://biblstandard.dk/ill/dk/docs/Look-up_of_holdings_information.htm

Publication: 26 August 2014

Last update: 27 October 2014

Creator: Leif Andresen

Approved by danZIG

Published by The Danish Agency of Culture

 

1. Introduction

The Danish ISO 20775 profile for holdings requests [1] specifies the format of holdings information, but do not include a specification of exchange of requests and responses. This is synchronously with ISO 20775:2009 Information and documentation -- Schema for holdings [2], which only define the schema.

2. Scope

This specification describes how to transport holdings information with special consideration to lookup of holdings information from the Danish National Union Catalogue to public and research libraries in Denmark. The response is intend to be used for selection of library to send a ILL request using Danish ISO 18626 profile for ILL transactions [3].

3. Look-up of holdings information

 

3.1 Specification of lookup of one title in local data base

 

Lookup of one title in local data base from DanBib or bibliotek.dk to be done by SRU [4] according to this model :

 

http://sruserver.nyby.dk/program?version=1.2&operation=searchRetrieve&recordSchema=isohold&query=rec.id%3D12345678

 

The local library record id "12345678" is to be replaced by the actual local id in the actual local database.

 

The server "sruserver.nyby.dk" is the local server and "program" is name of the local programme. For use by DanBib and bibliotek.dk for lookup op in local data bases, the local libraries shall register URL of local server and program in VIP-basen as one parameter.

 

To support this specification of look-up holdings information does not imply to support other SRU searches or to support use of isohold for more than one record per search.

 

 

3.2 Specification of lookup of more than one title

 

Even lookup of more than one title is outside the scope of this specification this information: A query for more than one title is possible with SRU,  by using Boolean operator or.

 

 

3.3 Specification of response

 

For header the mandatory response parameters version (= 1.2), and numberOfRecords (= 1 or other integer) are used.

 

For the record only the recordSchema (= info:srw/schema/5/iso20775-v1.0), recordPacking (= xml) and recordData (= the actual holdings record) are used.

 

See Annex A for an example of response.

 

4. References

[1] Danish ISO 20775 profile for holdings requests

http://biblstandard.dk/ill/dk/docs/20775_profile_for_holdings_requests.htm

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

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

[3] Danish ISO 18626 profile for ILL transactions

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

[4] SRU/SRW (Search and Retrieve URL/Web Service)

http://www.loc.gov/standards/sru/

 

 

Annex A: Example of response

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

<sru:searchRetrieveResponse xmlns:sru="http://www.loc.gov/zing/srw/">

<sru:version>1.2</sru:version>

<sru:numberOfRecords>1</sru:numberOfRecords>

<sru:records>

  <sru:record>

   <sru:recordSchema> info:srw/schema/5/iso20775-v1.0</sru:recordSchema>

   <sru:recordPacking>xml</sru:recordPacking>

   <sru:recordData>

    <holdings xsi:noNamespaceSchemaLocation="http://www.loc.gov/standards/iso20775/ISOholdings_V1.0.xsd" xmlns:n1="http://www.altova.com/samplexml/other-namespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

     <holding>

      <institutionIdentifier>

       <value>DK-777777</value>

       <typeOrSource>

        <text>ISIL</text>

       </typeOrSource>

      </institutionIdentifier>

      <holdingSimple>

       <copiesSummary>

        <copiesCount>1</copiesCount>

        <status>

         <availableCount>10</availableCount>

         <availableFor>1</availableFor>

         <earliestDispatchDate>2014-12-17T09:30:47Z</earliestDispatchDate>

        </status>

       </copiesSummary>

      </holdingSimple>

     </holding>

     <resource>

      <resourceIdentifier>

       <value>12345678</value>

       <typeOrSource>

        <text>SUFFICIENT</text>

       </typeOrSource>

      </resourceIdentifier>

     </resource>

    </holdings>

   </sru:recordData>

  </sru:record>

</sru:records>

</sru:searchRetrieveResponse>

 

Note: Annex A: Example of response corrected 27 October 2014.