...
Discussion Items
| Time | Item | Who | Description | Goals/Info/notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2min | Administrivia |
| Note taker: | |||||||||
| 30Min | Title level Request | Stephanie Buck | Update on TLR
| |||||||||
| 30Min | Hold Shelf Expiration Date Should Respect Closed Library Dates |
Issue: 'Requests currently ignore calendars, so hold expiration dates expire on dates libraries are closed. |
Meeting Notes
Upüdate on TLR:
...
Update on TLR:
- See update in slide deck
- for Lotus:
- UXPROD-3330
- UXPROD-1796
- New Requirement discovered
- Wiki page for tracking TLR Features to track: Title level requests - features and info
- TLR is available in snapshot next week
- All should be ready to implement with the morning glory release
- for Lotus:
- Questions:
- What is the status of Multi volumes? - not yet a title level request but an item level request
- Brooks: There may be a subgroup needed with MM and RA to make the distinction programmatically for multi volume resources in regard to the TLR and otherwise
- Jana will reach out to the MM conveners to visit the MM SIG to present the problem with multi volumes to them and get a subgroup formed
- Are notices available or needed? - Steph checks with Vega on this
- How are permissions set for patrons requestion through the discovery layer? (to restrict certain groups of people from placing holds on certain
- who can request what from where
- Can be managed through the Circ rules
- A location based request is speced out but is yet to be developed Jira Issue:
- What is the status of Multi volumes? - not yet a title level request but an item level request