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)
...
- Slide 3: For generating a due date/time, Check-outs and Check-ins are only concerned with open-closed hours for Service Points, not Locations? Correct, this was already decided.
- Slide 4: We discussed this before and decided end of day is 11:59:59 PM for long-term loans regardless of Service Point hours. (Andrea remembers that there may be a post-v1 feature where the library could set this for themselves.)
- Slide 5: We already discussed long-term loans. Short-term loans are due <missed this>.
- Slide 6: Does Skip closed days in intervening period only apply to day calculations, not hour/min calculations? RA SIG says that we can skip this.
- Sean ran out of time to go over use cases, but needs to redo them anyway based on decision from Slide 6.
Notice Logic
- Have had many conversations about where notices should sit–have decided on Notice Policies (which Darcy showed us a mock-up) divided up by functional area.
- Actual notices reside elsewhere.
- Discussed that it doesn't make sense to have all of the notices together as one policy. It makes sense to have Loan and Fee/Fine notices together.
- It seems like recalls could be part of Loan notices rather than Request notices.