Old notes

• Place hold request
• Request campus book delivery (not sure if this is usually the ILS or the ILL software) [ejl]
  o Various forms of delivery: between branches, ILL, direct borrowing
• Recall an item
• Renew loan
• Access to e-version or digitized version [dm]
  o more of an issue as more gets digitized; "best copy issue" relevant here

Use cases

• Hold the item
• Get the item from wherever it is (online, ILL, document delivery, storage, other patron)
  • request might fail
• Find out what you're allowed to do / if you're allowed a given request
• renew loan?
• Given a citation (or a bib item or an article, etc.), find out if we have it and where we can get it (i.e. OpenURL resolver. What do they do to find volume info in ILS?)

In this set of functions, we often have to deal with side effects, and authentication and authorization (who are you, and what are you allowed to do?) We wouldn't allow just anyone to access these functions. Questions of whether client is trusted.

Two general approaches: ask for a service, get a reply; or just hand off to ILS.
If we don't just do handoff, or trust the client, we need to deal with authentication.

Functions

HoldTitle – chooses an available item of that title, and holds it. Takes a bibid.

HoldVolume – holds a particular item (like HoldTitle, but where you need to specify at the sub-title level, e.g. serial volume) – can hold any item that's an instance of the volume. Takes either a volume ID (if available), or an item id that's an instance of that volume.

HoldItem – Take an item id, and holds that.

HoldCancel – cancel this hold request. (Would need some id for the hold, or enough arguments like person and item of bib id to figure out which hold to cancel)

• • could take a list of items, not just one. Return values would be more complex.

RecallTitle,
RecallVolume
RecallItem
RecallCancel – require a return of an item and get it to me

OrderDeliveryTitle?
OrderDeliveryVolume?
OrderDeliveryItem
OrderDeliveryCancel – deliver a non-checked-out item to a particular location.

RenewItem? – I have an item, I want to renew it

GetFullText – Retrieve a pointer to an electronic copy. Does this need to involve an ILS request?

Takes a bib or item id, and possibly an identity, returns a URL (or set of URLs?) to an electronic (fulltext?) copy (or says none is available). (Might be retrieved from a bib 856, or a holdings record,

BorrowFromElsewhere*? – Does this need to involve an ILS request? Possibly for a "respond-to-ILL-request" operation.

WhatCanIDo – Given an id (bib? item?) tells me (somehow) what I can do with it

Definitions:

• Title: A bibliographic work (that has a bib record and bibid; e.g. a book, recording, or serial)
• Volume: A component part of a Bib that can have multiple copies (e.g. 1997 volume of a serial; v.3 of a "three-decker" novel)
• Item: A particular piece of inventory that can circulate

Bindings:

Application handoff – all we do is tell the OPAC to do its thing
(might be generic on a Title, or could specify verb or item wanted)
Xserver – put a veneer (object/procedure library or protocol) on it?
(and possibly generic enough that there could be other systems
that implement those same functions?)
NCIP?

Will NCIP give us any help here? (Terry thinks there are services there we can use)

Who will work more on this: Dave K and Emily (will look into Xserver type binding), Patricia (will look into handoff), Terry (will look into NCIP binding), David B

Patricia will look into specifying a getfulltext function