DAIA extensions

From Code4Lib
(Redirected from DAIA service types)
Jump to: navigation, search

This page collected some proposed service types and other suggestions as extension to the Document Availability Information API. See Document Service Ontology (DSO) for a more up-to-date approach.

Additional Service types



Request library staff to make a photocopy or scan of a part (chapter or article) of a physical item, which will them be emailed or delivered to the user.

Copying/Scaning as service makes sense. Is the act of copying the relevant service or the fact that you get only a part of the item as copy? -- JakobVoss 02:12, 29 September 2009 (PDT)
In my library, the nature of the service is that you only get part of the item AND you get choose what part. The act of copying isn't the relevant service, although I'm not sure how a library would provide a user-choice part of the item without copying, but if there's a way, that's fine! User:jrochkind
An item may have the fragment attribute but that would mean the library does only have a specific excerpt. So Excert looks like a reasonable service type. -- JakobVoss 01:39, 23 October 2009 (PDT)

Please refer to https://github.com/gbv/dso/issues/1 for further discussion



Request delivery of a physical item, to a circulation desk, an office, or even a home, depending on what the library provides.

Does deliver imply loan? I think a broad "deliver" does not help, but more specific services like "home-deliver", "office-deliver" etc. as subtypes of "loan". Delivering to a circulation desk is not a specific service in my opinion. -- JakobVoss 02:12, 29 September 2009 (PDT)
Why is delivering to a circulation desk not a specific service? I guess I'm trying to figure out how to represent the services that my library actually does offer. Now, I kind of see your vision of services, and I WISH my library offered the kind of services you're thinking of, and in such a way that my software could actually predict them... but it kind of doesn't. And I'm not in charge.
There is a difference between deliver to a circulation desk for use in the rooms of the library (presentation) and for loaning. Deliver to an office or at home is a different kind of service that implies loan. To distinguish deliver to circulation desk and self-pick up with open-access shelving we may need another method. -- JakobVoss 01:39, 23 October 2009 (PDT)
Hmm. I hear you. But we have some items for some patrons that can be checked out, but you've got to go get them from the stacks yourself. There are other items for certain patrons that can be checked out, and you can click a button and have them waiting at the circ desk. There are other items that can be checked out, and you can have them delivered to your office. The end result of all of these things could be considered a 'loan' -- but it matters to the user which of these things are available, the difference in convenience may effect their decision of whether to access the item at this time or not. How should this be encoded in DAIA so it can be presented to the user? I'm trying to take a stab at it, I hear your critique, but I'm still not sure the better way to do it. I see how to create new services simply by creating new URI's for them in DAIA -- you mention 'sub-service', but how can I extend DAIA with a 'sub-service', what does this look like?
  • Similarly: It matters to the user whether they can do 'presentation' by simply going to the stacks and picking it up themselves, and reading it in the library location of their choice, or whether they can only access 'presentation' by filing a request, waiting a certain amount of time, and then viewing the material during certain business hours of a special reading room in that special reading room. (Another actual situation in my actual library). How should this be represented in a DAIA response, so it can be communicated to the user? I am not sure. Any ideas? Jrochkind 19:33, 27 October 2009 (PDT)
Except again, it makes me think of the 'obstacle' field. Maybe an 'obstacle' field is the elegant answer to many of my use cases. Is there a way for me to legally add an 'obstacle' extension to my DAIA response such that it will still validate against the DAIA schema? Not sure if 'obstacle' should be a URI, or a human displayable message -- probably both. Jrochkind 19:48, 27 October 2009 (PDT)

Please refer to https://github.com/gbv/dso/issues/2 for further discussion



ILS 'request' function. Sadly, the typical ILS 'request' function can be used for a variety of actual services, including:

  • recall a checked out item
  • place a 'hold' on an item
  • request an item for delivery to a particular location (circ desk or other)

Where possible, you should not use the 'request' service, but should instead use a service expressing a more specific action availability. However, actually existing ILS's can make it very hard to figure out what more specific actions are available, and it may still be useful to advertise the ILS 'request' function, this service represents that.

Looks like a super-class of all service types with meaning "unknown". In this case we may better make the service field optional so if you can specify an unknown service. -- JakobVoss 02:12, 29 September 2009 (PDT)
That might work, as long as it's possible to specify a user-displayable label for the service. Won't be able to be understood/acted upon by software, but the user can still be told this is, say, a generic 'Request'.



Recall a checked out item, which will typically then be placed on hold for you.

Placed for you for what purpose? -- JakobVoss 02:12, 29 September 2009 (PDT)
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. -- JakobVoss 01:39, 23 October 2009 (PDT)
Yes, I think I can buy this, seems workable, thanks for explaining. Although I'd clarify I don't want to say why an item _isn't_ available. I in fact want to say that an item IS available, after a specified delay, but you can't just take it off the stacks, the only way you can get it is by pressing a button. This is in general something I'm not sure how to do in DAIA, a thread throughout these new services. It's not always enough to say that 'loan' is available, sometimes I need to make sure a user knows they can't just pull it off the stacks themselves, the ONLY way to access 'loan' is to access this link here. I'm not sure how to do that in DAIA, so the system can make sure to let the user know this? Or maybe it's just indicated by 'loan' being available but NOT 'presentation'. My end system consuming DAIA knows that if 'loan' is avaialable but not 'presentation', it should warn the user "don't go try to pull this off the stacks yourself, follow this link instead." Or maybe I DO need an 'obstacle' field, I kind of like that. But I don't think the current DAIA schema gives me any way to add such an 'obstacle' field while still having XML that validates against the DAIA schema? Jrochkind 19:41, 27 October 2009 (PDT)
Additionally, I've been told that in my library users want to know if by accessing 'loan' they are going to be triggering an early return from someone who has it out now. Some users will decide they don't want the book that bad (especially cause the person who they got it from can then trigger an early return for THEM, the chances of them being able to keep it long are not that great. Not sure what to do with this either. Except it again makes me think of an 'obstacle' field maybe. Jrochkind 19:27, 27 October 2009 (PDT)