# Presentation: 601674

## ISO ILL Protocol 			The IPIG Generation

- Presentation by
- Barbara Shuh
- ISO Interlibrary Loan Application Standards
- Maintenance Agency

- ZIG  in Leuven					July 2000

## ILL Protocol

- ISO 10160/10161-1
- Peer-to-Peer
- Unconfirmed service
- Originally designed to be supported by OSI stack

**Notes:**
Background:
When one talks of the ILL Protocol, I presume that they are referring on of 2 ISO documents which comprises the Interlibrary Loan Application Standards:  
        ISO 10161-1	Protocol Specification 
Other part 	ISO 10160	Service Definition
        Developed in 1980's in parallel with the work on Z39.50. 
        Standard approved by ISO in 1991
        Ca. 50 Canadian libraries use version 1 implementation
        ILL Protocol Implementors Group (IPIG) participants are working on version 2 implementations

In this forum, I also thought it worthwhile to mention 
Differences between Z39.50 and ISO 10161-1  

Because of the nature of the interlibrary lending business, Interlibrary Loan is never a 1-way conversation.  
        Always 2 partners in a transaction
Nature of business requires prearranged service agreements
THEREFORE:  peer-to-peer communications, not client-server/origin-target

ILL, as an activity, isn't spontaneous
ILL Transaction progress over a period of days or weeks.
In design phase, communications costs were high and librarians, always living close to the line, didn't want to spend the time and money sending back confirmation of messages received.
THEREFORE:  unconfirmed service (not confirmed service)

ISO ILL Protocol was designed to be supported by an OSI stack; 
OSI network infrastructure has never been available to provide operational support for ILL communications.
        Early Canadian implementations used proprietary e-mail.
        IPIG implementors are using Internet networks
IPIG implementators had to find other ways to provide the missing OSI support for Transport, Addressing information, Security 

## IPIG Implementations

- Message transport:  Internet Protocols
- MIME-encoded SMTP
- TCP/IP
- Security
- Prompt-1 response
- Directory information
- External object

**Notes:**
IPIG implementors are using Internet Protocols for Message transport.  There had been much discussion on the relative merits of using store-and-forward communications (e.g., SMTP) versus using a direct connection (using TCP/IP)  In the end, e-mail won:  The IPIG Profile mandates the use of MIME-encoded SMTP  - but many developers have implemented both modes of communication - and allow applications to use both interchangably.

Although implementors were aware of the earlier work done on Profile for the Use of Z39.50 Item Order Extended Service to Transport ILL Protocol APDUs (Z39.50/ILL Profile 1), it was viewed as " an interesting intellectual exercise" - but considered re-inventing the wheel when there was a multitude of stable Internet e-mail applications available. 

Security:
To provide basic security, IPIG implementations are using the Z39.50 Prompt-1 response (but not the challenge.)  Some vendors feel that this does not go far enough, so further controls may be developed as more developers gain experience in this area.

Directories:
Because it was assumed that there was to be a separate but integrated OSI directory service, the ILL Protocol does not include addressing information.  When the directory services failed to materialize, IPIG implementors developed an external object that carries system addresses and pseudonyms with every message.  

This is viewed as an interim measure, and there is currently renewed discussion on developing a common format for the exchange of ILL information.

Borrowed from ZIG: 
        Z39.50 Prompt-1 response
        Register of Z39.50 syntax

## Communications 

**BLDSC**
**ISO ILL **
**Gateway**

**RLG**
**RLIN**

**NLM’s**
**ISO ILL**
**Gateway**

**   ****T e Puna **
**(N.Z.)**

**Local**
**ISO ILL **
**Application**

- BLDSC
- ART System

- Docline

**Communications **
**Network**

**Kinetica**
**(Australia)**

**NAVIS **
**(Canada)**

**   ****LIDDAS**

**CIC**
**Distributed **
**System**

***Library Consortia***
**Big 12 **
**Plus**

***   ******Bibliographic Utilities***
**OCLC **
**Central ILL,**
**DRSS**
**	**

*National Libraries*

**Notes:**
Update on IPIG implementations:
        Achieving a critical mass of protocol users
Local:
        epixtech = RSS (Resource Sharing System)
        Chinook Regional Library system (Alberta, Canada) was first library to use IPIG generation system to communicate with NLC
        Simon Fraser University  (Vancouver, British Columbia, Canada)
        Fretwell-Downing = VDX (Virtual Document Exchange)
        now being marketed by Geac for their North American customers (beta tests at New York University?)
        University of Toronto plans to implementing VDX in Fall 2000; other Ontario University libraries negotiating a consortial licence for VDX
        Perkins and Associates' CLIO
        CLIO licensed by Endeavor to be repackaged with Endeavor products
        Pigasus = Wings
        integrated into ILL management software used by Relais, the electronic document delivery software owned by EBSCO
        used by regional research branch libraries  in Agriculture Canada
        RLG = ILL Manager
        Operational release in April 2000
        First implementers are  libraries participating in RLG’s Shares program
        TLC = Library.Request
        one of the first of the IPIG implementations released 
        being used by NLM as front end to 
        TLC also provides a basic ILL Protocol tool-kit that has been used by many of the other developers.

Bibliographic Utilities
        OCLC
        RLG
        Sabinet
        utility serving Southern African
        using OCLC DRSS software

Library Consortia
        LIDDAS (Local Interlending and Document Delivery Administration System) 
        consortium of Australian university libraries
        using FDI's VDX
        CIC
        11 large university libraries in U.S. mid-west (Big 10 + the University of Chicago) 
        worked with OCLC to develop a new "distributed ILL system which conforms to the ILL Protocol 
        MnSCU PALS
        Minnesota State Colleges and Universities
        Used TLC's toolkit to facilitate development
        EDDIS (Electronic Document Delivery, the Integrated Solution)
        e-LIB project
        using FDI's VDX
        University of East Anglia, BIDS (Bath Information Data Services), Lancaster University, University of Sterling
        LASER (London and South East Region (?))
        V3.Online networked service for resource sharing and interlending requesting
        Using FDI's VDX
National Libraries
        National Library of Canada:  NAVIS
        using ILL protocol since 1987
        exchanging messages directly with IPIG -based applications June 1, 2000
        used TLC's toolkit to facilitate upgrade to IPIG profile.
        National Library of New Zealand:  Te Puna
        Implemented FDI's VDX; online in spring of 1999
        National Library of Australia:  Kinetica
        Implemented FDI's VDX; online in summer of 1999
        ???The Royal Library, National Library of Sweden
        making decisions about the software to use???

Handling Legacy systems
        British Library Document Supply Centre BLDSC:  ART system
        developed gateway ARTISO to legacy system (Automated Request Transmission)
        contract with Fretwell-Downing (FDI)
        Now in interoperability testing with a university library in the UK (Lancaster University Library)
        National Library of Medicine:  Docline
        CISTI:  IntelliDOC
        NLM & CISTI using TLC's Library.Request as a front end

## Moving Onward...

- Fine-tune interoperability testing scenarios
- Develop a network of ILL directories
- Revise the ISO ILL Protocol with the lessons learned

## White Papers

- Supporting Communications Services
- Confirmed vs. Unconfirmed
- Undo Functionality
- Ease of Implementation
- Security/Authentication, Encryption
- Optional Messages
- Operational Models
- Support of Automation

## Web resources for ILL Protocol

- Interlibrary Loan Application Standards Maintenance Agency web site:
- http://www.nlc-bnc.ca/iso/ill/
- Interlibrary Loan Protocol Implementors Group (IPIG)
- http://www.arl.org/access/naildd/ipig/ipig. shtml

**Notes:**
Contacts:

Questions?