ISO 18626:2021

INTERNATIONAL ISO
STANDARD 18626
Third edition
2021-12
Information and documentation —
Interlibrary loan transactions
Information et documentation — Transactions de prêt
interbibliothèques
Reference number
© ISO 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Messages . 3
4.1 General . 3
4.2 Request . 4
4.3 Request Confirmation . 8
4.4 Supplying Agency Message . 8
4.5 Supplying Agency Message Confirmation . 11
4.6 Requesting Agency Message . 11
4.7 Requesting Agency Message Confirmation .12
4.8 Complex Types .12
4.9 Closed Codes . 13
4.10 Error Data . 16
5 Format and transport .17
5.1 Format . 17
5.2 Transport . 17
5.2.1 General . 17
5.2.2 Applications acting as initiators . 17
5.2.3 Applications acting as responders. 18
5.2.4 HTTP/HTTPS message headers . 18
5.2.5 Data privacy protection . 18
5.2.6 Character Representation . 18
6 Conformance requirements .19
Annex A (informative) Information website .20
Annex B (informative) Open Codes .21
Annex C (informative) XML schemas .28
Annex D (informative) Guidelines — Use cases .29
Annex E (informative) Supplying library’s internal unique record ID .37
Annex F (informative) Profiles of ISO 18626 .38
Annex G (informative) Handling consortia.39
Annex H (informative) Retry - negotiations between the requesting and supplying libraries .40
Bibliography .42
iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 46, Information and documentation,
Subcommittee SC 4, Technical interoperability.
This third edition cancels and replaces the second edition (ISO 18626:2017), which has been technically
revised.
The main changes compared to the previous edition are as follows.
— Several elements have been added to handle identified use cases. As part of this, SentVia has been
renamed DeliveryMethod, this element is now used in both the Request and Supplying Agency
Messages. This is the only elimination of an element and has been done after consultation with
implementers.
— Annex B has been rewritten to clarify the use of open codes.
— Annex D has been changed from including several use cases to one sample use case and a has been
linked to additional use cases at the website (see Annex A).
— Annex F has been added with guidelines about the use of profiles with ISO 18626.
— Annex G has been added with guidelines about consortia.
— Annex H has been added with guidelines about handling negotiations using “retry” when the
supplier cannot fulfil the first request.
— A RetryInfo section to Supplying Agency Message has been added.
— ServiceInfo/PreferredFormat has been renamed to ServiceInfo/ItemFormat and renamed
DeliveryInfo/DeliveredFormat to DeliveryInfo/ItemFormat so that we only need one Open Code list
for Formats.
iv
— PhysicalAddress/Region has been changed from StandardCodes to free-text field to bring the
PhysicalAddress structure in line with the PhysicalAddress structure used in NCIP (to simplify
implementation).
— For requests, the element PreferredEdition has been added. For the purposes of this document, the
element AnyEdition has been retained to ensure backward compatibility.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
v
Introduction
This document is intended to succeed the old ISO interlibrary lending protocol (consisting of ISO 10160,
ISO 10161-1 and ISO 10161-2). Unlike its predecessors, this document is well suited to the modern,
web-based technological environment, which is based on XML and web services. Another important
difference between the two standards is that while ISO 10160 is based on an outdated 1980s model of
ILL transactions, its successor relies on and supports a modern, much simpler interlibrary loan (ILL)
procedure.
This document specifies three simple messages: a Request, a Supplying Library Message and a
Requesting Library Message. Implementer experiences gathered from the previous edition of this ILL
protocol indicates that it is easier to implement than ISO 10160 and that the functionality provided
meets the requirements of libraries’ current ILL practices.
This document is the first part of a more general strategic initiative to standardize resource sharing in
ISO/TC46/SC4. As part of this intention, the committee has aligned element names, transport and XML
[7]
schema with similar functions in ANSI/NISO Z39.83 .
In the next version of this document, AnyEdition will be deprecated in favour of PreferredEdition. It is
recommended to upgrade from AnyEdition to PreferredEdition without unnecessary delay.
For additional information about implementation of this document, see Annex A.
vi
INTERNATIONAL STANDARD ISO 18626:2021(E)
Information and documentation — Interlibrary loan
transactions
1 Scope
This document specifies the transactions between libraries or libraries and other agencies to handle
requests for library items and the following exchange of messages.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 2108, Information and documentation — International Standard Book Number (ISBN)
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 3297, Information and documentation — International standard serial number (ISSN)
ISO 4217, Codes for the representation of currencies
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
ISO/IEC 10646, Information technology — Universal coded character set (UCS)
ISO 10957, Information and documentation — International standard music number (ISMN)
ISO 15511, Information and documentation — International standard identifier for libraries and related
organizations (ISIL)
ISO 20247, Information and documentation — International library item identifier(ILII)
ISO 26324, Information and documentation — Digital object identifier system
ISO 27729, Information and documentation — International standard name identifier (ISNI)
RFC 3629, UTF-8, a transformation format of ISO 10646
RFC 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
RFC 7540, Hypertext Transfer Protocol Version 2 (HTTP/2)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp/
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
agency
library (3.2), library-related organization (3.5) or other agencies such as an archive or a museum or a
commercial document supplier
3.2
library
organization, or part of an organization, the main aim of which is to maintain a collection and to
facilitate, by services of a staff, the use of such documents as are required to meet the informational,
research, educational or recreational needs of its users
[SOURCE: ISO 2789:2013, 2.1.6]
3.3
library consortium
local, regional, or national cooperative association of libraries (3.2) that provides for the systematic
and effective coordination of the resources of school, public, academic, or special libraries, information
centres and other agencies, for improving services to the clientele of such libraries
3.4
library items
books, journals, articles, music, etc. or copies of these in physical or digital format
3.5
library-related organization
institution, company, consortium or other organization which handles ILL requests and/or receives
requested library items (3.4) on behalf of one or more libraries (3.2)
3.6
requesting agency
agency (3.1), which may send requests for library items (3.4) and receive them from the supplying agency
(3.7)
3.7
supplying agency
agency (3.1), which receives requests for library items (3.4) and delivers them to the requesting agency
(3.6)
3.8
uniform resource identifier
URI
compact sequence of characters that identifies an abstract or physical resource
[SOURCE: ISO/IEC 12785-1:2009, 3.23]
3.9
uniform resource locator
URL
subset of URIs that provide a means of locating a resource by describing its primary access mechanism
[SOURCE: ISO/IEC 12785-1:2009, 3.24]
3.10
uniform resource name
URN
persistent, location-independent, resource identifier used for recognition of, and access to,
characteristics of the resource or the resource itself
[SOURCE: RFC 8141]
4 Messages
4.1 General
This document specifies three messages and responses for handling interlibrary loan transactions:
— Request (see Table 1) and Request Confirmation (see Table 2);
— Supplying Agency Message (see Table 3) and Supplying Agency Message Confirmation (see Table 4);
— Requesting Agency Message (see Table 5) and Requesting Agency Message Confirmation (see
Table 6).
See additional information on guidelines about the use of this document in Annex D. Annex D is
illustrative and does not cover all relevant use cases.
For Request, Supplying Agency Message and Requesting Agency Message, a confirmation message is
sent immediately (see 4.3, 4.5 and 4.7). The Request Confirmation message (see Table 2) is not a positive
or negative response to the request; it indicates only that the Request message has been received. If the
Request message contains problems, the Request Confirmation message shall include Error Data (see
4.10).
Codes used in tables are as follows:
— R: Repeatable;
— M: Mandatory;
— CT: Complex Type;
— OC: Open Code List (i.e. Scheme Value Pair);
— CC: Closed Code List (i.e. the code list is part of the ILL standard);
— SC: Standard Code List.
Open Code Lists are predefined schemes, consisting of an enumerated list of possible values for a given
data element that should be supported by applications conformant with this document. The Open Code
Lists of values are not comprehensive and implementer groups may develop additional schemes for
these enumerated types to cover their implementation requirements. Thus, an application may choose
to support additional schemes for one or more Open Code Lists. Core lists of values to be supported by
all implementations are defined in Annex B.
The lists of values may be derived from standard lists of codes or other registries.
Standard Code Lists are based on code lists published in standards.
New schemes may be added to the Open Code List as described in Annex B.
Complex Types are listed and defined in 4.8.
Closed Code Lists (see 4.9) are a normative part of this document and shall be supported by applications
conformant with this document. They are similar to Open Code Lists, except that Closed Code Lists
of values are expected to be relatively comprehensive and stable. However, new closed code scheme
elements and code values may be added to the future versions of this document.
Date and time shall always be provided in the form YYYY -MM -DDThh: mm: ssZ as specified by ISO 8601-1.
Local date and time should not be used. When time is not significant, e.g. when a due date is given, use
23:59:59Z to indicate the time, for example, 2013-05-15T23:59:59Z.
Use of the country code referenced in Table 7 shall be as specified in ISO 3166-1. Use of the currency
symbols referenced in Table 7 shall be as specified in ISO 4217. Use of the ISNI code referenced in Table 1
shall be as specified in ISO 27729.
Use of the identifiers in Table B.1 shall be according to the referred standards: ISIL according to
ISO 15511, ISBN according to ISO 2108, ISSN according to ISO 3297, ISMN according to ISO 10957, ILII
according to ISO 20247, and DOI according to ISO 26324.
4.2 Request
The Request contains information about the item and service requested.
The Request is sent from the requesting agency to the supplying agency.
The Request contains some or all of the following groups of data elements as shown in Table 1.
— Header: administrative information
— BibliographicInfo: details of the item being requested
— PublicationInfo: information about the publication
— ServiceInfo: details of the service being requested
— SupplierInfo: list of potential suppliers
— RequestedDeliveryInfo: where and how to send the item
— RequestingAgencyInfo: details about the requesting agency
— PatronInfo: details about the patron
— BillingInfo: how to charge the requesting agency
Table 1 — Request
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of supplying library CT
(Complex Type AgencyId)
SupplyingAgencyId shall be provided except for RequestSub-
Type = PatronRequest and TransferRequest
RequestingAgencyId Identification of requesting library M
(Complex Type AgencyId) CT
ConsortialId Identification of the consortium with which the request is associated CT
For additional information on consortia, see Annex G
(Complex Type AgencyId)
MultipleItemRequestId Identification of MultipleItemRequest
Timestamp Date and time of the transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification or number M
RequestingAgencyAuthenti- Authentication in supplying library system of the requesting library CT
cation (Complex Type)
BibliographicInfo Bibliographic information about the requested item M
Table 1 (continued)
Element Definition Codes
SupplierUniqueRecordId SupplierUniqueRecordId should be used for the supplying library’s
internal unique identifier for the requested item, acquired from a
preceding automatic holdings request. If this identifier is used, there
should be no other identifiers in BibliographicInfo
More information can be found in Annex E
Title Title of the requested item
Author Author of the requested item
AuthorId ISNI name identifier of the author
Ref.: ISO 27729
Subtitle Subtitle of the requested item
SeriesTitle Title of the series
Edition Number or name of the edition
TitleOfComponent Title of the component part (e.g. article)
AuthorOfComponent Author of the component part
Volume Volume number R
Issue Issue number
PagesRequested Page from and page to
EstimatedNoPages Expected number of pages
BibliographicItemId Identification of a physical or electronic object R
(Complex Type) CT
Sponsor Person or organization sponsoring the publication
InformationSource Description of where bibliographic information was found
BibliographicRecordId Identification of a bibliographic record CT
(Complex Type) R
PublicationInfo Information about the publication
Publisher Name of the publisher
PublisherId ISNI name identifier of the publisher
Ref.: ISO 27729
PublicationType Type of publication OC
PublicationDate Date of publication
For serials and serial articles, this should be the publication date of
the component part such as issue, not the date when the serial was
first issued
PlaceOfPublication Place of publication, e.g. a city

ServiceInfo Information about the requested service M
RequestType Type of request (New, Retry or Reminder) CC
If no request type is specified, the default is “New”
For additional information on the use of Retry, see Annex H
RequestSubType Sub type to qualify the request R
CC
RequestingAgencyPrevious- Requesting agency’s previous request number when a retry is sent.
RequestId The Retry request may include updated data based on ReasonRetry
Table 1 (continued)
Element Definition Codes
ServiceType Type of service. Values: Copy, Loan or CopyOrLoan. If Copy is request- M
ed, then the requesting library is interested only in a copy. If Loan is CC
requested, then the requesting library is interested only in a loan. If
CopyOrLoan is requested, then the requesting library is
willing to accept either a copy or a loan
ServiceLevel Level of service OC
If the requesting library is willing and is able to accept any service
level, then the requesting library shall not include this element in the
message
ItemFormat Format of medium requested OC
If the requesting library is willing and is able to accept any format,
then the requesting library shall not include this element in the mes-
sage
NeedBeforeDate The request is not relevant after the stated date/time
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
If the requesting library is willing and is able to accept the requested
item at any time, then the requesting library shall not include this
element in the message
CopyrightCompliance The requesting library’s copyright compliance OC
AnyEdition Values Y or N. Yes for yes to any edition. No if only the specified
edition is acceptable
PreferredEdition The edition the borrower would prefer to receive. Values are ThisEdi- CC
tion, AnyEdition, or the MostRecentEdition
LoanCondition Conditions for use of the item OC
Used when submitting a Request Retry, after the supplying library R
indicates there is a loan condition that shall be met
StartDate Start date for a Booking (RequestSubType)
Ref: ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
EndDate End date for a Booking (RequestSubType)
Ref: ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
Note Human readable note
SupplierInfo When a request is sent to a brokering institution, the requesting library R
may provide a list of potential suppliers (in preference order)
intended primarily for requests sent to brokers but may be used in
other circumstances as well
SortOrder Value from 1 to 99 defining the order of preference of use
SupplierCode Code defining a potential supplier CT
(Complex Type AgencyId)
SupplierDescription Textual information about supplier
BibliographicRecordId Identification of a bibliographic record used CT
(Complex Type)
CallNumber Indication of the shelf position of the resource
SummaryHoldings Textual description of summary level holdings
AvailabilityNote Information about availability

Table 1 (continued)
Element Definition Codes
RequestedDeliveryInfo A prioritized list of suggested delivery methods, each with its own R
delivery address
SortOrder Value from 1 to 99 according to the order
Address Description of the delivery address CT
(Complex Type ElectronicAddress or PhysicalAddress)
DeliveryMethod The service via which the requested item should be sent OC
If the requesting library is willing and is able to accept any delivery
method, then the requesting library shall not include this element in
the message
CourierName An identified courier to be used if DeliveryMethod value = “Courier” OC
If the requesting library is willing and is able to accept any courier,
then the requesting library shall not include this element in the mes-
sage
RequestingAgencyInfo Details of the requesting agency
Name Name of the requesting agency
ContactName Name of contact. For example, ILL staff member
Address Description of how to contact the requesting agency CT
(Complex Type ElectronicAddress or PhysicalAddress) R

PatronInfo Details of the patron for whom the request is being made
Only used according to 5.2.5.
PatronId Identification of the patron
Surname Surname of the patron
GivenName First name of the patron
PatronType Type of patron OC
SendToPatron Only used with value “Y” if requesting library asks the supplying
library to send the requested resource directly to the patron
Address Description of how to contact the patron. CT
(Complex Type ElectronicAddress or PhysicalAddress) R

BillingInfo Information about how the requesting agency expects to be billed for
and pay for the item
PaymentMethod The preferred payment method OC
If the requesting library is willing and is able to accept any payment
method, then the requesting library shall not include this element in
the message
MaximumCosts The highest amount the requesting agency is prepared to pay for the CT
service
(Complex Type Costs)
If the requesting library has no maximum costs, then the requesting
library shall not include this element in the message.
BillingMethod Preferred billing method OC
BillingName Name of the contact person in finance department, etc.
Address Description of the billing address CT
(Complex Type ElectronicAddress or PhysicalAddress)
4.3 Request Confirmation
Table 2 — Request Confirmation
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of the supplying library CT
(Complex Type AgencyId)
RequestingAgencyId Identification of the requesting library CT
(Complex Type AgencyId)
Timestamp Date and time of the confirmation transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification
TimestampReceived Date and time of the confirmed request transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
MessageStatus Value “OK” or “ERROR” M
ErrorData If there are any errors, an error message is included; refer to 4.10. R
4.4 Supplying Agency Message
Supplying Agency Message is a message sent from the supplying library to the requesting library.
The message may be in response to a request or a message from the requesting library or a message
initiated by the supplying library. In all these cases, the same message is used.
The message contains the following groups of data elements as shown in Table 3.
— Header: administrative information
— MessageInfo: responses and notes
— StatusInfo: current status; i.e. status after any changes because of the message being sent
— RetryInfo: information when Status = RetryPossible
— DeliveryInfo: information about the shipped item
— ShippingInfo: information about the shipment
— ReturnInfo: if the supplier asks the requesting library to return the item to another address
Table 3 — Supplying Agency Message
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of the supplying library M
(Complex Type AgencyId) CT
RequestingAgencyId Identification of the requesting library M
(Complex Type AgencyId) CT
Timestamp Date and time of the transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification or number M
SupplyingAgencyRequestId Supplying library’s request identification or number

Table 3 (continued)
Element Definition Codes
MessageInfo Message from the supplying library to the requesting agency M
ReasonForMessage A code defining the reason for the message M
CC
AnswerYesNo Values Y or N – for Yes or No to respond
Mandatory when ReasonForMessage is RenewResponse or
CancelResponse
Note Human readable note
ReasonUnfilled The reason why the request cannot be filled OC
ReasonRetry The reason why the request cannot be filled unless it is modified or OC
repeated at a future date
For additional information on the use of Retry, see Annex H

StatusInfo Status information M
Status Actual status of the request in the supplying library M
CC
ExpectedDeliveryDate Date and time the supplying library expects to deliver the item.
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
DueDate Date and time the item is expected to be back at the supplying library.
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
LastChange Date and time of the last status change M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ

RetryInfo To be used when supplier status = RetryPossible
LoanCondition Applied when ReasonRetry, MustMeetLoanCondition is used because OC
the supplying library requires that conditions of use be met once the
R
requested item is delivered
Edition Applied when ReasonRetry, ReqEditionNotPoss is used, because the R
edition specified by the requesting library cannot be provided. The
supplying library indicates which edition(s) can be provided
ItemFormat Applied when ReasonRetry, ReqFormatNotPossible is used because OC
the requested format cannot be supplied. The supplying library indi-
R
cates which format(s) can be supplied
Volume Applied when ReasonRetry, MultiVolAvail is used, because these are R
the volumes that can be supplied. The supplying library indicates the
volume or volumes available
ServiceType Applied when ReasonRetry, ReqServTypeNotPossible, is used because CC
the requested service type cannot be supplied. The supplying library
indicates which service type can be supplied
ServiceLevel Applied when Reason Retry, ReqServLevelNotSupp is used, because OC
the requested service level is not supported. The supplying library
R
indicates which service level(s) are supported
DeliveryMethod Applied when ReasonRetry, ReqDelMethodNotSupp is used, because OC
the requested delivery method(s) are not supported. The supplying
R
library indicates which delivery methods are supported
CourierName Applied when Reason Retry, CourierNotSupp is used because the OC
courier specified by the requesting library is not supported. The sup-
R
plying library indicates which courier(s) are supported
Table 3 (continued)
Element Definition Codes
OfferedCosts Applied when ReasonRetry, MaximumCosts, is used because actual CT
costs exceed those specified by the requesting library. The supplying
R
library indicates what the actual cost shall be
(consists of Complex Type Costs)
PaymentMethod Applied when ReasonRetry, ReqPayMethodNotSupp is used, because OC
the requested payment method is not supported. The supplying
R
library indicates which payment method(s) are supported
RetryBefore Date and time before which to send the retry request
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RetryAfter The date and time after which the retry request may be sent
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ

DeliveryInfo Information about the delivery
DateSent Date and time when the item was sent M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
ItemId Value of Barcode(s) or RFID-tag Id of the item(s) being delivered R
URL URL from which to download or access the requested item
DeliveryMethod The service via which the requested item was sent OC
Address The actual address to which the requested item was sent CT
(Complex Type ElectronicAddress or PhysicalAddress)
SentToPatron Value “Y” if the supplying library has sent the item directly to the
patron and value “N” if the supplying library has not sent the item di-
rectly to the patron despite the fact that the requesting library asked
for this service. (see Request/PatronInfo/SendToPatron)
LoanCondition Conditions for use of the item OC
R
ItemFormat Format of the delivered item OC
ServiceType Service type of the delivered item CC
DeliveryCosts Amount the supplying library is charging the requesting library for CT
the item and related service
R
(Complex Type Costs)
PaymentMethod The payment method preferred by the supplying library OC

ShippingInfo Information about the shipment
CourierName Name of courier to be used if DeliveryMethod = “Courier” OC
TrackingId The tracking number(s) assigned by the courier to the package(s) R
containing the item(s) to be shipped
Insurance Value = Y if the package is ensured. Value = N if the package is not
ensured
InsuranceThirdParty Value = Y if a third party is providing insurance. Value = N if insur-
ance is not provided by a third party
ThirdPartyName The company providing insurance for the package containing the
item to be shipped
InsuranceCosts Costs associated with insurance, both the cost to ensure and the CT
amount of coverage
R
(Complex Type Costs)
Table 3 (continued)
Element Definition Codes
ReturnInfo If the supplier asks the requester to return the item to s specific address
ReturnAgencyId Identification of the library to which the item should be returned CT
(on request of the supplying library)
(Complex Type AgencyId)
Name Name of the library to which the item should be returned
PhysicalAddress Address to which the item is to be returned CT
(Consists of Complex Type PhysicalAddress)
4.5 Supplying Agency Message Confirmation
Table 4 — Supplying Agency Message Confirmation
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of the supplying library CT
(Complex Type AgencyId)
RequestingAgencyId Identification of the requesting library CT
(Complex Type AgencyId)
Timestamp Date and time of the confirmation transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification
TimestampReceived Date and time of the confirmed Supplying Agency Message M
transaction
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
MessageStatus Value “OK” or “ERROR” M
ReasonForMessage ReasonForMessage in confirmed Supplying Agency Message CC
ErrorData If there are any errors, an error message is included; refer to 4.10. R
4.6 Requesting Agency Message
Requesting Agency Message is a message from the requesting library to the supplying library.
The message contains the following groups of data elements as shown in Table 5.
— Header: administrative information
— ActiveSection: elements describing what to do
Table 5 — Requesting Agency Message
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of the supplying library M
(Complex Type AgencyId) CT
RequestingAgencyId Identification of the requesting library M
(Complex Type AgencyId) CT
Table 5 (continued)
Element Definition Codes
ConsortialId Identification of the consortium with which the request is associated CT
For additional information on consortia, see Annex G
(Complex Type AgencyId)
Timestamp Date and time of the transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification or number M
SupplyingAgencyRequestId Supplying library’s request identification or number
RequestingAgencyAuthenti- Authentication in supplying library system of the requesting library CT
cation (Complex Type)
ActiveSection Elements describing actions M
Action An action for the request M
CC
Note Human readable note
4.7 Requesting Agency Message Confirmation
Table 6 — Requesting Agency Message Confirmation
Element Definition Codes
Header Administrative information M
SupplyingAgencyId Identification of supplying library CT
(Complex Type AgencyId)
RequestingAgencyId Identification of requesting library CT
(Complex Type AgencyId)
Timestamp Date and time of the confirmation transaction M
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
RequestingAgencyRequestId Requesting library’s request identification
TimestampReceived Date and time of the confirmed Requesting Agency Message M
transaction
Ref. ISO 8601-1
Format: UTC: YYYY -MM -DDThh: mm: ssZ
MessageStatus Value “OK” or “ERROR” M
Action Action in confirmed Receiving Agency Message CC
ErrorData If there are any errors, an error message is included; refer to 4.10. R
4.8 Complex Types
A Complex Type is a set of information linked together describing, for example, identification with type
and value, as shown in Table 7.
Table 7 — Complex Types
Element Definition Codes
AgencyId Identification of the supplying library or the requesting library
AgencyIdType Type of identifier for the library OC
AgencyIdValue Value of the identifier for the library
Table 7 (continued)
Element Definition Codes
BibliographicItemId One or more unique standard identifiers (from different
identifier systems) for the requested resource
BibliographicItemIdenti- Type of bibliographic item identifier OC
fierCode
BibliographicItemIdentifier A unique identifier for the item (e.g. the ISBN)

BibliographicRecordId One or more unique identifiers (from different identifier systems) for the
record related to the requested resource
BibliographicRecordIdenti- Type of bibliographic record identifier OC
fierCode
BibliographicRecordIdentifier A unique identifier for the record (e.g. the OCLC record number or LC
control number)
Costs The cost for the request
CurrencyCode Currency symbol as specified in ISO 4217 SC
MonetaryValue Amount of money
CostType Type of cost OC
ElectronicAddress Electronic address
ElectronicAddressType Type of electronic address OC
ElectronicAddressData Value of the electronic address

RequestingAgencyAuthen- Authentication in supplying library system of the requesting library
tication
AccountId The customer number in supplying library database of other libraries
SecurityCode Password, PIN code or similar function

PhysicalAddress Mailing address
Line1 Address – first line
Line2 Address – second line
Locality Locality of the library/agency or the contact person
PostalCode Postal code according to the rules of the country
Region Word or phrase identifying a large area within a country including
province, state and department
Country Country code as specified in ISO 3166-1 SC
4.9 Closed Codes
Closed code elements and code values, as shown in Table 8, are vitally important to the Interlibrary
Loan protocol. All of them shall be supported by applications conformant to this document.
Table 8 — Closed Codes
Elements Code values Description
RequestType New The requesting library sends a new request
Table 8 (continued)
Elements Code values Description
Retry The requesting library sends the request again. The
Retry request may include updated or additional infor-
mation based on status RetryPossible and RetryInfo
Reminder The requesting library sends the request again with
the intention to remind the supplying library about the
request
RequestSubType BookingRequest Request for a specific period. Used together with
StartDate and if relevant, an EndDate
MultipleItemRequest Bundle up more than one request for same
bibliographic item
PatronRequest Insertion of a patron initiated request from a patron
OPAC or search portal to the patron's local ILL system
TransferRequest Intermediary service: handover of management of an
ILL request from one ILL system to another
SupplyingLibrarysChoice A service defined by the supplying library, which the
requesting library can select
ServiceType Copy The requesting library asks for a copy of the
requested item
Loan The requesting library asks for a loan
CopyOrLoan The requesting library accepts both a copy and loan of
the requested item
PreferredEdition MostRecentEdition The requesting library asks for the newest published
edition
ThisEdition The requesting library asks only for the edition as
specified in the Edition element
AnyEdition The requesting library will accept any edition
ReasonForMessage RequestResponse Supplying library answers a
...