2021-04-19 Resource Access Meeting Notes
Date
Attendees
Robert Scheier
Discussion Items
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia | Welcome to all the new members. Please take a minute to look at this page and add your info here: Resource Access SIG |
| |
| 30Min | Title Level Requests | Feedback on proposed UI, and process for managing title level requests |
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 | |
Notes:
- Introduction round - new SIG members and all others
- TLR - new UI developments since last week
- The title info was added
- The requester should be associated with TLR
- Request statuses were added
- Suggestion in Chat (Erin): 'It almost feels like there should be a TLR app' - this was dismissed because that would be a too complex structure
- If there is an item level request and a TLR that predates it, it should be a higher priority
- Brooks: TLR and ILR should be in a unified request queue (with options to reorder, edit,..)
- A look at other systems like Voyager and Koha were taken in consideration
- Material type: At what level is the material type included in the invoice?
- The material type will be considered in the circ rules/loan policy
- Andrea: How does the system handle multi volumes?
- We need a way of indicating what type (loan, material) allows TLR and ILR
- It was thought not to be a good idea to indicate this in the loan type/Circ rule because it is all about the item level there
- Suggestion in Chat (Bob): Why not turn TLR into ILR that picks up the next available? - This was dismissed, because it was already decided, that a TLR is needed
- Outcome: Kelly and Kimie will bring this back to us in 14 days and in the meantime will meet with Brooks and discuss this further