2018-05-17 Resource Access Meeting Notes
- Emma Boettcher
Date
Attendees
- Joanne Leary
- Cheryl Malmborg
- Deb Lamb
- Schwill, Carsten
- Rameka Barnes
- Anya
- Emma Boettcher
- Jana Freytag
- Darcy Branchini
- Sharon Wiles-Young
- Tania Hewes
- Mark Canney
- Kimie Kester
- William Weare
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | Housekeeping |
| |
| 15min | Printing slips | Review printing slips ("staff slips") | |
| 40min | Service Points Demo | Present on patron notices - use cases & decisions from WOLFcon | |
Notes
Staff slips
- Some slips available out of the box - can be edited. Can also create and delete new slips
- Define triggers & conditions for staff slips
- Template may need contact information for a given location - not different slips & triggers, but one slip with a token that applies the appropriate location
- Hold slip will be first submitted story
- Printing from a browser
- Rich text editor
Patron notices
Three options:
- Combine logic and template - but progression of notices might be unclear
- Separate logic and template - logic of when to send notices is in loan policy, but notices are drafted separately. Clarifies progression.
- If there is a workflow engine: could describe triggers and events for notices through that - the trigger is overdue, and the events to follow would be the notices.
Workflow engine also accommodates conditions (patron type, loan type, loan policy)
Workflow engine would in theory be flexible enough to accommodate fines & fees, but might not be the best place for that. (Would it be able to provide the legal assurance that patron notices go out as fines and fees are applied?)
Some institutions will need to print automatic check-in receipts.
Would like to include logos or signatures in notices - for a location or for a library (not at the campus or institution level)
Important that notices can be consolidated, so that patrons receive one notice about overdue items, not five (even if their items are from different libraries or locations). Better UX for the patron. However, should not consolidate different types of notices - separate recall from overdue, for example.
Next steps
Darcy will come back to the group with information about templates, which can be done even if workflow engine is uncertain.