Date
Attendees
Discussion Items
| Time | Item | Who | Description | Goals | |
|---|---|---|---|---|---|
| 5min | Housekeeping |
| |||
| 10min | Requests | Cate Boerema (Deactivated) | 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.Shelving service point on Requests CSV | - Short term solution for paging pick list report is to export requests csv and filter by item status = paged - We have said we need to be able to filter pick lists by service point and we have service point in the csv but it's the pickup service point for the request, not the reshelving service point. - I assume we need to add the reshelving service point for this purpose (Chalmers thinks we do) - Make sense to everyone? - Do we want to include just the primary one or all service points associated with the item's effective location? |
| 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.) |
...
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 | |||||||||||||||||
| Requests | Q2 2019 |
| There were questions about whether library would usually be part of the location name. Some people said they would do that at their institutions while others hoped they wouldn't have to asking "why should I have to put that all in the name when the location is part of a hierarchy?" Cate pointed out that, in FOLIO today, only the location name displays on Loans, Check out, Requests etc. We don't display all the levels. The ability to display all levels is in
| |||||||||||||||||
| Loans | Emma Boettcher |
| Conversation also turned to whether items with the status Checked out could be checked out, with the suggestion that Checked out items should be able to be checked out. Will need to have follow-up discussion on whether to warn user about checking in and checking out items with particular statuses | |||||||||||||||||
| Loans | Emma Boettcher |
| The minimum accounts for the granularity in current systems; later versions might expand on this to track not just that an item is damaged or has missing pieces, but when that damage was sustained. Structuring the initial version of damaged items as not a flag but a controlled list would support a model similar to creating and selecting material types or loan types later on, |