200
edits
Changes
→Recall
::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)
:::: 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? [[User:Jrochkind|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. [[User:Jrochkind|Jrochkind]] 19:27, 27 October 2009 (PDT)
