...
...
...
...
...
...
...
...
...
...
...
...
...
...
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 |
Meeting Outcomes
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 | |
| Circ log | Emma Boettcher | Q4 2020 | When a notice is sent, display the name of the template and triggering event in the circulation log |
| ||
Notes
It's Jana Freytag's first meeting as convener! Woohoo!
Circulation Log -
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. Logging needs a lot of improvements in general. That's slated for Q4 as work specific to notices.
- Darcy - we're not keeping track of the history of template changes. So if a template changes, you might not see what was sent.
- Erin - so what exactly is FOLIO keeping in terms of information about notices going out? Darcy - not sure. Still some confusion about what is actually stored and how the notice system is architected.
- Mark - are we able to store item information that goes out? What I really want to know is what item triggered the notice. Emma - for the circulation log, the item barcode should be tracked when it applies to one of the events. And then we said it should be linked to the loan details (if applicable.)
- Darcy - does anyone have strong feelings about it? Erin - I think subject or description are appropriate. As long as it's documented. Mary - we've sometimes had to get lawyers involved when there are disputes. So we absolutely need audit information at UMass. Because they have to follow public retention rules.
- Darcy - what about privacy concerns? Cornelia - what are the anonymization features?
- Darcy - Emma, can you remind me, can you get to this from the user record? Emma - you'd be able to look up a particular user in the app. We haven't yet discussed the anonymization of the information yet.
- Cornelia - if I anonymize the loan, I can't see it for the loan in the log, so I shouldn't see it for notices. Jana - if there is a fine/fee attached, you would still see info. But once that's done, it should be anonymized. Emma - we need to make sure the anonymization functions hit the circ log app as well.
- discussion about what can be in a row.... e.g., one notice could have a lot of barcodes in it. so does that become one row, or many rows? Not sure - hard to picture - should we mock it up for a future meeting for discussion? Darcy - yah - what about items that don't have barcodes? Like just charges that aren't in inventory.
- Emma summarized what would be included. Andrea thinks name makes more sense then subject for inclusion. (Sorry, I got a Slack convo I needed to respond to, and lost some of the details here.)
Cate
- Questions about Fast Add
- Supporting default setting of Suppress from Discovery. Where should that setting go? There's options on Instance, Holdings, Items.
- Adding it to Instance doesn't propagate any settings downward in FOLIO - but that doesn't necessarily mean anything about the extract.
- Cate - the current design creates a brand new Instance / Holding / Item - you can't attach it to an existing Instance. Joanne - correct - right, we put fast adds on their own Bib records.
- Cate - so the goal is to have the item not show up. But we need to ask around about intended metadata management intended function - not sure if the cascade is an intended feature.
- Cate - I also need to talk to Kelly Drake about course reserves too. Erin - she's planning a new small group soon, too.
- Also, should the button on Fast Add have different wording, because it creates new records?
- Group had mixed opinions - no one felt super strongly that it needed to change. So Cate will leave it since the story is already being worked on.
Molly
- Molly is on the Support SIG Home.
- Group is reviewing a Jira from Chalmers - UICAL-110 - making group aware of it.
Brooks
- Another awareness - issue they saw with fixed due date schedules. Because the end date and start date of succeeding schedules didn't overlap, the system ends up with a 24 hour gap with no valid schedule. So make sure the dates have an overlap.