Date
...
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:
Permission management - Erin Nettifee - New permissions management proposal from App Interaction
...
Question about notice policies - Erin Weller
Does each notice need its own policy? Short answer = no, but each circ rule should have exactly one policy associated with it. Brooks Travis showed screen to demo what Missouri State is doing.
Aged to lost notices = implemented in Iris.
Check-in/out notices batched by session. Not possible to set a delay (e.g. send notices one hour after check-in/out) One way to artificially create a delay is to use SettingsàCirculationàGeneral Settings and configure the time out for a session to equal your delay, then don’t end session until you’re ready for notices to go out.
Types of notices:
- Loan notices = sent to borrower
- Request notices = sent to requestor
- Fee/fine notices