Date
...
Functional Area | Product Owner | Decision Reached | Reasoning | Link to Supporting Materials | Comments |
|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
Notes
Opening time offset - UI mockup (see Opening_time_offset_UI.pdf)
...
- Discussed why you might need to enter a renewal date when you override a failed renewal
- Item isn't renewable
- Item hasn't reached maximum number of renewals
- Patron blocked
- Patron expired
- User will uncheck the items they don't want to override
- Should Additional information be required? Yes–at some point could make this an institution setting but for now leave it as required
- What if there are multiple due dates for a batch of 130 items? Do a batch for one date, then a batch for another date, etc.
- Need to discuss this further. Emma will send out flowchart and slides–discussion will continue on Thursday.
User record - requests section
- Didn't have time for this