Date
...
Time | Item | Who | Description | Goals |
---|---|---|---|---|
5min | Housekeeping | Andrea Loigman |
| |
10min | Blocks | Holly Mistlebauer | Forgot to ask these two questions when discussing blocks on September 30 | 1) Should patron notices be sent for manual patron blocks? Automated patron blocks? 2) Patty W. (a PO) recently asked me about these types of blocks:
|
15min | Claims returned | Emma Boettcher | User record notes for claims returned | Gather requirements for ending claims process and adding note about claim returned to user record. Decide how many notes fields are needed. |
30min | Requests | Cate Boerema (Deactivated) | Delivery requests: checking in should automatically check out item to requester | For delivery requests, we had a requirement that said that, when the item was checked in, it should be automatically checked out to the requester (when top request in queue is delivery request). The challenge we have run into is that check out can/should be prevented for a variety of reasons:
Given this, we really can't auto-check out items. Instead, we may need to do the following:
Introducing the new request and item state make this feature significantly more complex. Do people have ideas for how to simplify for MVP? If we do decide to introduce the new states, we need to:
|
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
---|---|---|---|---|
Fees/fines | Holly Mistlebauer | Post-MVP | Holly created 2 JIRA issues: UXPROD-2109: Allow for patron notices to be sent on request for manual patron blocks UXPROD-2108: Expand patron blocks to allow blocking of borrowing by material/item type | Informational blocks will be handled by user notes |
Loans | Emma Boettcher | Q4 | Add additional field for patron-facing (notice) information in declared lost & claim returned resolution actions When resolving a claim returned item, create a note on the user record with the outcome of the claim and a link to the loan. | |
Requests | Q4 | Above described solution with new item and request state seemed like best approach to SIG. We updated the request whitelist And we specified some other key requirements in this document: https://docs.google.com/document/d/1iWhEAxd3hvlvqmDgXmbJ2a3A_J2ahQHaMN2RKvDLvWI/edit?usp=sharing I have enough to go on for now. May come back with follow up questions later. |
Notes
- Blocks - Holly Mistlebauer
...