|Planned Release (if known)|
- No one on the call had objections to putting requests at the end of the queue when moving from one item to another as long as they can be manually reordered and the request creation date is unchanged and visible
- Just in case Chalmers really objected to this idea, we discussed the rush request alternative briefly as well
- General sense was there would be cases where you would want to reorder a request but not do a rush request.
- More discussion is needed on use cases, but a couple were offered:
- Someone is in position 2 of the queue calls and says, "I want to be in the queue, but will be out of town for a while, can you move me to the bottom"
- Library requests an item for document delivery of a chapter of a book for the China campus. They want it at the top of the queue but don't want to "rip it away" from the person who has it now.
- Overall, SIG would prioritize manual reorder of the queue and think rush requests would be an additional feature down the road
- Carsten said he was still very interested in instance/title level requests which would reduce the need to move requests from one item to another. Chalmers really wants this to. We plan to start a subgroup to gather requirements on this topic, but it hasn't been flagged cap-mvp.
- Carsten wondered what patrons would think if they saw their queue position changing. Andrea and others on the call said it hasn't been an issue for them (and some institutions don't show queue position to patrons)
|Loans||Emma Boettcher ||Q4||On declared lost and aged to lost items, the SIG would like to allow (with staff confirmation and/or override) the standard loans actions: renew, change due date, declared lost, claim returned. ||Impact on fines/fees mentioned but not discussed|
Being able to claim returned was not discussed to the same degree as renew and change due date, may be worth a quick revisit
Erin Nettifee – active/not active