NISO Circulation Interchange Protocol

A Standard in Development

Pat Stevens, OCLC July 13, 2000

Topics

BackgroundWork to date

Approach Progress

Challenges

What Do Users Want?

Simple accessReliable, fast delivery

I.e., services like Amazon.com

More Specifically...

Easy, powerful, one-stop search and find

“Request” requiring minimal keyingAbility to track request (e.g. UPS)Guaranteed, fast deliveryIntegrated management of their loans

(from local collection and outside…)

Make it Easy! (example)

John Smith - items charged:

British Art in the 20th Century Due 8/15/00[borrowed from local collection]

Bradshaw, T. Bloomsbury Artists Due 7/30/00[requested and borrowed directly from consortial partner]

Holroyd, M. The Art of Dora Carrington Due 7/15/00[not in local collection or consortium; borrowed from unaffiliated library via traditional ILL]

Gombrich, E. History of Art Due 7/10/00 10:00 pm[E-book, charged for use online]

New Supply Models

Local Library

Consortial Partners

Unaffiliated institutions

Vendors & Systems - potential uses of protocol

ILS/Circ Sys

ILS/Circ Sys

ILLILL ILLILL

ILS/Circ Sys

ILS/Circ Sys

ILS/Circ Sys

ILS/Circ Sys

SelfService

SelfService

ILS/Circ Sys

ILS/Circ Sys

The Standard and Scope

A repertoire of messages & associated rules of syntax and semantics

Between and among computer-based applications to effect circulation to support controlled access to certain

electronic resources or other library services

Not to define circulation functions

Supports 3 application areas

Direct consortial borrowingCirculation/Interlibrary Loan

InteractionSelf-service Circulation

The standard’s test bedIt must support these, may support

others

Standards environment

3M Standard Interchange ProtocolISO 8459-4:1997 Bibliographic Data

Element Directory: Part 4: Circulation Application

ISO 10160/61 Interlibrary Loan Application Service Definition & Protocol Specification

ANSI/NISO Z39.50-1995 Information Retrieval: Application Service Definition and Protocol (ISO 23950)

3M SIP

De facto standard for self checkoutExtended to support other functionsAllows the committee to build from a

base of practical applications3M and other vendors experienced

with the SIP are active participants

A Goal -- as possible

Use existing definitions and terminology

Permit developers to meld standards into a single application

Technical Assumptions and Design Principles

Keep it simple and within purposeConfirmed Service -- Pairs of messages

Initiation -- response pairs Each message carries full context

necessary for processing Requires connection-oriented transport

Simple State Table governs messaging not circulation

Message Syntax, Transport Protocol and Encoding

Message Syntax and Encoding Syntax -- XML DTD Message encoding -- XML following DTD

Transport To be decided at August, 2000 meeting

Directly on top of TCP/IPWrapped in another protocol

3 Service Types

Lookup tell me something about

Update please take an actionNotification I have taken an action

Messages

about 3 things (objects) Users Items Agencies (Libraries)

Lookup Services

Lookup Lookup Agency Lookup Item Lookup User Authenticate User

Not Authorize UserAuthorization request implicit in an update

Lookups require a Unique ID

Lookup Response

Did not Understand MessageUnderstood Message

Cannot Supply Information and Reason Can Supply and the Information

Unique ID’s

Agency ID’s Registration scheme Value in Scheme Example OCLC and OCLC Symbol

User ID and Item ID are compound Include the Agency ID

Update Services

CheckOut Item and Undo Checkout Item

CheckIn Item Recall Item and Cancel Recall Item Renew Item and Cancel Renew ItemRequest Item and Request ItemSend User NoticeTypical Circulation Transactions

Update Services continued

Create Agency and Update AgencyCreate Item and Update ItemCreate User and Update UserUpdate User Fiscal AccountCreate Services used for new objectsUpdate Services include modify and

delete

Update Responses

Did Not Understand MessageUnderstood Message

Cannot take Action Requested with Reason

Did Take ActionResponse includes information on action

taken,Examples: Due Date, Item or User ID

Notification Services

Item CheckedOutItem Checked InItem Recalled and Item Recalled CancelledItem Renewed and Item Renewed

CancelledItem RequestedUser Fiscal Account UpdatedUser Notice Sent

Notification Service ...

Agency Created and Agency UpdatedItem Created and Item UpdatedUser Created and User Updated

Notification Service Response

Did not understand messageUnderstood message

Messages defined in a DTD

Each service has 2 messages Initiation and Response

All messages have Header and Body

Header provides identifying information

Body provides detailsExtensibility a goal

Checkout Message

<NCIPMessages> <CheckOutItem>

<InitiationHeader> <FromSystemID>data</FromSystemID> <FromSystemAuthentication>data</ FromSystemAuthentication> <FromAgencyID>data</FromAgencyID> <FromAgencyAuthentication>data</FromAgencyAuthentication> <ToSystemID>data</ToSystemID> <ToAgencyID>data</ToAgencyID> </InitiationHeader>

<AuthenticationValue> <Ordinal>data</Ordinal> <AuthenticationInput>data</AuthenticationInput> </AuthenticationValue>

Checkout Message continued

<UniqueUserID> <UniqueAgencyID> <Scheme>data</Scheme> <Value>data</Value> </UniqueAgencyID> <Value>data</Value></UniqueUserID>

<UniqueItemID> <UniqueAgencyID> <Scheme>data</Scheme> <Value>data</Value></UniqueAgencyID> <Value>data</Value></UniqueItemID>

Checkout Message continued

<UserElementId> <UserElementName>data</UserElementName> <UserLookUpType>data<UserLookUpType></UserElementID>

<ItemElementId> <UserElementName>data</UserElementName> <UserLookUpType>data<UserLookUpType></ItemElementId>

Checkout Message continued

<FeeAmountAcknowledged> <CurrencyCode> <Scheme>data</Scheme> <Value>data</Value> </CurrencyCode> <CurrencyValue>data</CurrencyValue> </FeeAmountAcknowledged>

</CheckOutItem></NCIPMessages>

Approach

GOAL -- Draft Standard for Trial UseAllow for implementations prior to ballotIdentify early implementers

Implementers invited to August meetingDevelop tests

Message level testing Application level testing

DSFTU - August 2000

Structure of standard

Protocol: services, high-level objects, message state

Cross Application profile: specifies encoding via XML schema for messages, data objects, transport

3 Application-specific profiles: Self-Service, Direct Consortial

Borrowing, ILL to Circulation

Challenges

Allowing for local practice Within libraries and consortia Allowing for international use

Moving target Technology Library practice

Allowing for new applications

Questions?

pat_stevens@oclc.org