Changes

::So are you suggesting this shouldn't be a service of it's own, but instead should just be indicated in the 'delay' and user-displayable comments on the actual end-purpose service, that a 'recall' is possible? One thing is that in my library I am told that the user wants to know if they will be recalling the item from someone else or not before making the request.

:::This should better be encoded in the 'delay' and 'queue' attributes. If I understand you right, you want to encode whether an item is hold by someone else or is not available for some other reason. If we start encoding this, we can build an ontology of reasons why I cannot get a book (someone else holds it, it's a the bookbinder, the cat of the librarian is sitton on it...) which is not purpose of core DAIA. Maybe you could add a custom 'reason' field to unavailable or an 'obstacle' field to available/unavailable. -- [[User:JakobVoss|JakobVoss]] 01:39, 23 October 2009 (PDT)

=== Deliver ===