2020-08-17 Resource Access Meeting Notes
Date
Attendees
Discussion Items
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia | From the PC: The Reporting SIG is seeking a Test Data Developer for the LDP and an SQL Developer for Resource Access and User Management reports. Please see details on the Technical Skills in Demand page. |
| |
| 15Min | Circ log | circ log miscellaneous questions | ||
| 15Min | Calendar Behavior | UI issues | ||
| 10Min | live libraries issues report | live libraries issues report |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
|---|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
| Circ Log | Emma Boettcher | Record due date when recording Aged to lost action Add # of open requests when recording aged to lost, marked as missing, claimed returned, declared lost Pursue UI option to initially hide many items on one notice | ||||
Notes
1. Emma on remaining questions about circulation log
- aged to lost: what needs to be in the description? anything except user, item and date?
since it's an automated process, there are no staff notes/additional information
notices, billing, blocks connected to the process are separate actions
Joanne: we would want to know the due date
Andrea: if recalled, would it be the original due date showing or actual due date? Emma: actual due date
it would help to know if the item has a recall request on it
Andrea: is it useful to have number of open requests? to let other patrons know the request can't be fulfilled
Emma: there should be a report on that in the backlog, but might be good to have it here in addition
the number of open requests should also show on marked missing, claimed returned and declared lost
Joanne: but we need to understand that the log only does show a snapshot at the time of the action - is a link to the loan policy needed from the loan-related actions? we decided on linking to notice policy from notice actions
Joanne: nice to have, but not vital
the group agrees
we link to the loan details and you could always get to the loan policy from there
might be especially useful if loan policy has changed temporarily (like for an item that was on reserve) - how to display one notice for multiple items?
Darcy's suggestion is to be able to open a row of a notice action to display the items in that notice below
David: what if I want to know if the notice for a certain item was sent? Darcy: we would get to a notice action from an individual item search
it's just that the display would be more manageable, but doesn't affect the search
2. Brooks on Calendar UI issues
- when displaying calendars for a certain service point the list is not in date order
- regular hours: you can enter dates, but time is recorded as well (UTC+0) - which leads to the same problem as in the fixed due date schedules: there is a 24 hour gap between two time spans
- exception calendar shows wrong times and empty boxes, which might be connected to the latter problem
but dates are calculated properly
Cheryl: will try to reproduce, would be easier to fix if we redesign the entry mechanism to be more text-based
Cheryl will put some information together and share on the Slack channel to be discussed at a later meeting
3. Molly on live libraries issues (update from support SIG)
update on UICAL-110 (calendar crashing and opening hours not displaying at Chalmers): could be pinpointed to an entry that had an exception but no opening dates
4. Darcy on bug fixes for automated patron blocks
blocking criteria are checked at check-out, but currently existing possible block reasons (like existing fees/fines) are not picked up when implementing this feature
to set priority, who is live with Folio now and plans to use automated patron blocks with the Goldenrod release?
no from Simmons
no clear answer from Missouri State
yes for Lehigh (they went live today, congratulations!)
5. Jana will send out invites for upcoming meetings, and the ones sent out by Andrea will be cancelled