Date
Attendees
...
Discussion Items
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia |
| ||
| 30min | circ log | Decide what actions and what information about those actions relevant to notices is worth recording in circ log | ||
| 10min | fast add questions | Suppress from discovery:
Fast add button/action wording:
| ||
| 10min | live libraries report | Molly Driscoll | talk about issues being reported by the live libraries |
...
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
It's Jana Freytag's first meeting as convener! Woohoo!
...
Talking about notices - what actions are taken and how they are described.
- Actions are pretty simple - notices basically can only be sent. But what should go in the description? Things like template (pieces) as well as the triggering event that caused the notice to go out.
- Erin - not really
...
- listed, but I'd like to see when failures happened. Emma - FOLIO isn't there yet, right Darcy? Darcy - correct - there's errors due to systems, like the server, and then failure due to bounced email. System issues are tricky because of how many places FOLIO could be run (like AWS, locally, etc.)
- Darcy - a thin thread is a list of what is sent. Errors would come after.
- Andrea - is it possible to create a user without an email address? Darcy - good question. Brooks - email is not required. So Andrea - that's an error that would be good to get sooner rather than later - the absence of communication pathways. Darcy - the system knows about those errors, it's more that integrating it into the log can be harder.