| Requests | | Unknown | Reviewed wireframes for configurable whitelist: - Decided wireframes makes sense
- Some questioned priority and felt they might just enable all kinds of requests for all item states and then use request policies to limit what can be done
- Others felt this would be useful and is better than what they have today
| - A few people thought it would be nice to be able to do this configuration by location or library (as opposed to by tenant)
- But people also felt that different configurations with a single tenant invited a great deal of complexity for the system and patrons
- In the end we agreed by tenant made sense
|
| Requests | Cate Boerema (Deactivated) | Q2 2019 | Revisited decision about which requests should display in the loan action history table: - In light of the fact that we are designing a "circ log" with detailed info about requests on items by patrons, do we really need to display all requests in the loan action history?
- This is complex development
- Developers say it would be much easier to fix the bug if we just showed requests that affect due date
- SIG would still prefer to see all, as requests that don't change the due date can also impact the loan. Holds may make it impossible to renew a loan, for example
- BUT SIG agreed that if we had the circ log easily accessible and also a link to the request queue, it would be fine
|
|