2024-10-17 Agenda and meeting notes
- Thomas Trutt
Section 3: Check-in and Check-out
Discussion Items:
Administrative topics
Check-in UI
Modal vs dropdown - benefits and downsides
Is another check-out status needed?
implications downstream
what is the goal of this status?
Request status when checked out -
new status needed - Open - checked out to patron
UI implications - filters / etc
Request Check-in
Is the shelf expiration date recalculated
Is a new request status needed? Will “Open - available for pickup” surface
benefits and consequences.
Reporting needs (moved to the next meeting)
do we need any other data collected than what is currently collected?
Meeting notes:
The team decided on a drop-down option for the check-in user interface, featuring three default settings: return to stacks, return to hold shelf, and ask for action. A new request status, "Open checked out to patron," was introduced, with plans to integrate it into the request status filter. The discussion touched on circulation workflows, specifically how to handle items returned at different service points without adding complex business logic for edge cases. Reporting needs were deferred to the next meeting, during which mockups for request app filters and edit forms will also be reviewed. Action items include implementing the drop-down UI change and preparing mockups for future discussions. All participants were tasked with considering reporting needs ahead of the next meeting.
Check-in UI Discussion (08:17 - 18:09)
Discussed two options for check-in UI: modal dialog box or drop-down within check-in UI
Decided on a drop-down option with default settings at service point level
The drop-down option will allow users to select their preferred action for check-ins, streamlining the process.
Default settings at the service point level will cater to different library needs and workflows, enhancing user experience.
The implementation aims to reduce repetitive confirmations while maintaining flexibility for varying operational requirements.
Agreed on three options for the drop-down: return to stacks, return to hold shelf, and ask for action
Request Status and UI Changes (18:09 - 27:40)
Discussed adding a new request status for items checked out to patrons
Agreed on 'Open checked out to patron' as the new status
Discussed UI implications, including adding the new status to the request status filter
Circulation Workflow and Edge Cases (27:43 - 36:44)
Discussed scenarios where items might be returned at different service points
Items may be checked out at one service point and returned at another, leading to potential confusion about their status.
This scenario could result in double notices being sent to patrons if the system does not recognize the item's prior status.
Libraries with multiple locations may need to implement business logic to manage notifications and status updates effectively when items are returned to different service points.
Considered implications for hold expiration dates and notifications
Decided not to add complex business logic for edge cases
Reporting Needs and Future Discussions (36:45 - 46:34)
Pushed discussion on reporting needs to the next meeting
Planned to review request app filters and table columns in the next meeting
Discussed potential changes to the new request and edit request forms
Slip Editor and Token Types (46:34 - 55:22)
Reviewed mockups for slip editor with multi-column layout
Discussed customizable token types for request types
Planned to discuss circulation log data in the next meeting
Potential UI changes:
Screen | Image | Notes / Comments |
|---|---|---|
Check-in Optional Dialog |
| Preferred wording:
|
Check-in Optional Dropdown |
| Dropdown will default to service point setting |
Dropdown options |
| Options:
Ask for action activates the dialog box. |
Service point settings |
| Needs reviewed |
Checkout - w/ Alerts column |
| Needs reviewed |
|
|
|
Decisions:
Action Items: