Difference between revisions of "DAIA extensions"
(→Excerpt) |
(→Request) |
||
| Line 12: | Line 12: | ||
: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. -- [[User:JakobVoss|JakobVoss]] 02:12, 29 September 2009 (PDT) | :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. -- [[User:JakobVoss|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 == | == Recall == | ||
Revision as of 14:31, 29 September 2009
This page collects some proposed service types as extension to the Document Availability Information API.
Request
http://purl.org/NET/daia-ext/request
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
http://purl.org/NET/daia-ext/recall
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)
Deliver
http://purl.org/NET/daia-ext/deliver
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.
Excerpt
http://purl.org/NET/daia-ext/excerpt
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
