Date
Attendees
Discussion Items
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5min | Housekeeping |
| ||
| 10min | Requests | Circle back on Request questions | Revisit this ppt with request questions (https://docs.google.com/presentation/d/1hNYBxUdy3pGKKpo5BkY7bJFfBEVdEG1idCecY1xVwko/edit#slide=id.p): - We previously said we wanted to capture all requests on Loan actions rather than just those that changed the due date. Turns out this makes fixing the Requests on Loan Details bug much more difficult. In light of the fact that we are now considering a more general "circulation log" solution for detailed circ history, can we address this bug by only displaying requests that change the due date? - Update on the "Pickup expired" status. I spoke with the developers and this will require an architectural change. The current job that sets request status when requests expire cannot update Item status. We need to move scheduling to OKAPI to make that happen. It looks like other features (such as time-based patron notices) will also require scheduling in OKAPI so we have decided to go ahead and make that happen. I'll update again when that has progressed further. | |
| 15min | Circ behavior for On order, In process items | Emma Boettcher | Does the system (warn or prevent) the (check out or check in) of items that are (On order or In process) (In process has been discussed re: check in, but the other combinations have not) | |
| 30min | Damaged and missing pieces | Emma Boettcher | Determine requirements for recording data about missing pieces & damage in Inventory (e.g., repeatable fields, is damage yes/no or free text, etc.) |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision | |