Danish ISO 18626 profile for ILL transactions

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

Publication: 16 July 2014

Last update: 16 July 2014 (after publication of ISO 18626 15 July 2014)

Creator: Leif Andresen

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 18626 Information and documentation -- Interlibrary Loan Transactions [1] and don’t replace ISO 18626.

 

All Mandatory elements are mentioned in the profile. This profile does not prescribe the use of not mandatory elements not mentioned below. Mandatory elements, where the profile does not give additional information to the standard, are just marked with a hyphen. Other elements are included in the profile, if they are expected to be used (this don’t apply to chapter 3.4).

 

2. Scope

The profile is intended for interchange of ILL request and other messages according to ISO 18626 Interlibrary Loan Transactions between Danish Libraries - and between Danish Libraries and the national union catalogue DanBib. The profile shows which parts of the schema it is recommended to deliver. But the profile does not restrict the use of the schema to these parts only.

 

3. Profile description

3.1 General

 

Transport

The profile prescribes the use of https for transport.

 

Library identification

Identification of Danish supplying and requesting libraries (Complex Type AgencyId):

                  AgencyIdType = ISIL

                  AgencyIdValue = <Concrete ISIL Identifier>. Concerning institutions which have been assigned a Danish library code, the syntactical format is DK-XXXXXX, where XXXXX is the Danish library code and if relevant additional identification of bus stop address, see danZIG-specification 03 [2].

 

Identification of supplying and requesting libraries (Complex Type AgencyId) in Greenland and the Faroe Islands and outside Denmark registered in the Danish Union Catalogue DanBib and other Danish special databases with 6 digit codes use this identification:

               AgencyIdType = DNUCNI

               AgencyIdValue = XXXXXX

 

In examples below are only used ISIL as AgencyIdType.

 

Header

For both Request, Supplying Agency Message, and Requesting Agency Message use:

Header

 

SupplyingAgencyId

ISIL

RequestingAgencyId

ISIL

Timestamp

-

RequestingAgencyRequestId

-

 

Conformation messages

The confirmation messages are not mentioned in details in the profile. These messages only contain the needed information and all elements are relevant. It is recommended to contain both SupplyingAgencyId and RequestingAgencyId in the confirmation messages.

 

3.2 Request - for all types

All types of requests defined below are sent with ServiceInfo:

 

ServiceInfo

 

ServiceType

-

ServiceLevel

Levels of service: Values: Normal and Urgent. Urgent only used after agreements between requester and supplier.

PreferredFormat

-

NeedBeforeDate

-

AnyEdition

Y or N

Remark: the library.dk user interface gives the user the possibility to say Yes or No to “Any edition”. This information is used by library.dk to select the best choice of library. But the value of AnyEdition is still valid for the handling in the library receiving the request from library.dk.

 

The elements in SupplierInfo are intended for instructions about forwarded requests and are not used. If a supplier can’t fulfill a request, the request is not forwarded, but answered with negative value of status (e.g. Unfilled).

 

3.3 Request - for general use

 

BibliographicInfo

 

SupplierUniqueRecordId

-

 

For Danish libraries til the supplying library’s internal unique identifier (SupplierUniqueRecordId( be procured with holdings request, with ISO 20775 Schema for holdings information [3] (see "Danish ISO 20775 profile for holdings requests" [4]) or Z39.50 Holdings Schema [5] (see danZIG Profile Specification 2007 [6]).

 

3.3.1 Request for general use – without additional information

 

For holdings information delivered by ISO 20775 where the values of holdings.resource.resourceIdentifier.typeOrSource.text is SUFFICIENT the request is sent with no additional information.

 

3.3.2 Request for general use – with additional information

 

For parts of bibliographic items identified with SupplierUniqueRecordId, the parts must be additional identified with elements from BibliographicInfo and PublicationInfo.

 

For holdings information delivered by ISO 20775 where the values of holdings.resource.resourceIdentifier.typeOrSource.text is INSUFFICIENT the request is sent with some additional information.

 

BibliographicInfo

 

TitleOfComponent

-

AuthorOfComponent

-

Volume

-

Issue

-

PagesRequested

-

EstimatedNoPages

-

PublicationInfo

-

PublicationDate

-

 

3.4 Request - for not unique identified material

 

If the requester can’t identify the wanted title in the National Union Catalogue or in a Danish Library, the standard can nevertheless be used for send a request. In these cases most possible elements in BibliographicInfo (expect SupplierUniqueRecordId) and PublicationInfo are filled in.

 

 

3.5 Supplying Agency Message

 

MessageInfo

 

ReasonForMessage

Codes:

RequestResponse

StatusRequestResponse

RenewResponse

CancelResponse

StatusChange

Notification (normally not used)

AnswerYesNo

-

RetryAfter

-

 

StatusInfo

 

Status

Status’s:

RequestReceived (normally not used)

ExpectToSupply

WillSupply

Loaned

Overdue

Recalled

RetryPossible

Unfilled

CopyCompleted LoanCompleted (normally only used on request)

CompletedWithoutReturn

Cancelled

ExpectedDeliveryDate

-

DueDate

-

LastChange

-

 

 

DeliveryInfo

 

DateSent

-

ItemId

Highly recommended: Value of Barcode or RFID-tag Id of the item being delivered

 

 

It is recommended to store information about closed requests in 12 months. In this period the supplier is expected to give answer with these values of Status:

Unfilled

CopyCompleted

LoanCompleted

CompletedWithoutReturn

Cancelled

 

Remark the Danish rule [7] that prescribe, that all information about a borrower shall be removed not later than four weeks after the loan is completed (returned and fees paid).

 

3.6 Requesting Agency Message

ActiveSection

Elements describing actions

Action

Actions:

StatusRequest

Received

Cancel

Renew

ShippedReturn (normally not used)

ShippedForward (normally not used)

Notification (normally not used)

 

 

4. References

 

[1] ISO 18626 Information and documentation -- Interlibrary Loan Transactions

http://www.iso.org/iso/search.htm?qt=18626&sort_by=rel&type=simple&published=on&active_tab=standards.

Informational website about ISO 18626

http://illtransactions.org/

 

[2] NCIP Implementation Guidelines: Collaboration between Danish libraries and other agencies: Agency Subdivision - Unique Agency Id

http://www.bs.dk/publikationer/andre/danzig/03/html/entire_publication.htm

 

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

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

 

[4] Danish ISO 20775 profile for holdings requests

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

 

[5] Z39.50 Holdings Schema. Version 1.4. November 2002

http://www.loc.gov/z3950/agency/defns/holdings1-4.html

 

[6] danZIG Profile Specification 2007. 6. C Holdings Information Search and Retrieval

http://www.bs.dk/publikationer/andre/danzig/01/html/chapter06.htm

 

[7] 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

 

Informative Annex

Handling in local library system

 

Using the transactions for development of new procedures in the local libraries is not part of the guidelines. But The Danish Agency for Culture and the authors of the profile hopes, that the vendors of library systems will use the possibility for make more effective solutions for the borrowers.

 

Separation of normal requests with verification in the National Union Catalogue and not verified in Denmark can be done on the occurrence of the element SupplierUniqueRecordId in the Request.

 

Automatic control of requests not fulfilled in expected time: Based on received ExpectedDeliveryDate the requester can send Requesting Agency Message with Action StatusRequest. If the new ExpectedDeliveryDate is acceptable, the information is just stored, so the borrower can see it in Borrower Status screen. If the new ExpectedDeliveryDate is not acceptable, as message a given to a librarian for decision about reaction.

 

 

Annex B

 

Informative Annex

Examples of transaction XML files

 

Request with just SupplierUniqueRecordId; without additional information:

http://biblstandard.dk/ill/dk/examples/request-without-additional-information.xml

 

Request with SupplierUniqueRecordId and additional information:

http://biblstandard.dk/ill/dk/examples/request-with-additional-information.xml

 

Request without SupplierUniqueRecordId and with metadata for requested title:

http://biblstandard.dk/ill/dk/examples/request-non-unique-identified-material.xml

 

 

Request confirmation without error:

http://biblstandard.dk/ill/dk/examples/request-confirmation.xml

 

Request confirmation with an error:

http://biblstandard.dk/ill/dk/examples/request-confirmation-with-error.xml

 

Supplying Agency message with delivery next day (WillSupply):

http://biblstandard.dk/ill/dk/examples/supplying-agency-message-delivery-next-day.xml

 

Supplying Agency message with shipped information (Loaned) and barcode/RFID-itemID:

http://biblstandard.dk/ill/dk/examples/supplying-agency-message-message-about-loan.xml

 

Supplying Agency message with changed status (Recalled):

http://biblstandard.dk/ill/dk/examples/supplying-agency-message-message-about-recall.xml

 

Supplying Agency message with negative answer (Unfilled):

http://biblstandard.dk/ill/dk/examples/supplying-agency-message-no-delivery.xml

 

Supplying Agency message confirmation:

http://biblstandard.dk/ill/dk/examples/supplying-agency-message-confirmation.xml

 

Requesting Agency message asking for Renew:

http://biblstandard.dk/ill/dk/examples/requesting-agency-message.xml

 

Requesting Agency message confirmation:

http://biblstandard.dk/ill/dk/examples/requesting-agency-message-confirmation.xml