|10min||Slips||Darcy Branchini||Pick slips - by service point, location?||Can pick slips be printed for the logged in user's associated service point? Or should a prompt appear to choose a specific service point or location at the time a user decides to print them? And if it's location, at what level? Specific locations seem too granular and would force a user to choose several. Is library the right level?|
|20min||Notices||Darcy Branchini||Part 2 - Review automated fee/fine notices||Confirm triggering events for notices related to automated fines. Overdue fine, overdue fine + renewed, aged to lost fine, aged to lost fine + returned, aged to lost fine + replaced and action taken on fine (payment, waive, refund, transfer).|
|15min||Inventory display||Andrea Loigman||Thin thread for inventory display||Charlotte and Martina have proposed thin thread for Inventory display for us. We need to confirm that this will work for us. https://docs.google.com/document/d/1Dd9Q0H66T-lnQR9H2ilvw3IIhqlN9isVlFVPTs5FE8k/edit|
|Planned Release (if known)|
|Pick slips should be printed at logged in user's primary service point.||Screen needs to show that service point.|
Triggering events for notices related to automated fines: Overdue fine charged, Overdue fine + renewal, Aged to lost status, Aged to lost fine charged, Aged to lost fine + returned, Aged to lost fine + replaced.
Notices for action taken on Fine: Fine paid, Fine waived, Fine refunded, Fine transferred. Might be automated. Default is no notice, but can choose the option to send.
|Renewal should be treated as a return but with a different notice.|
|Proposed new Inventory display will work for this group.|