Date
Attendees
Discussion Items
| Time | Item | Who | Description | Goals/Info |
|---|---|---|---|---|
| 2min | Administrivia |
| ||
| 20 Min | Change due date - Requests | Discuss interaction between "change due date" and requests: (per https://folio-project.slack.com/archives/C3G05TF3R/p1614846070059800 : | Brooks will write up a feature for this functionality and bring it back to the group. | |
| 15Min | Missing features? | We did a Gap analysis and found some missing features we would like to bring to the group. |
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 | |
Notes
TOPIC #1 Brooks Travis Discuss interaction between "change due date" and requests
Group discussed an issue identified by Lisa Perchermeier, Leipzig University Library, who recommended adding a feature that would display information like "there is an active pending hold request on the item" and a confirm button before the due date is changed.
When using change due date, the system let’s the staff user know – do you realize there is a request on this item and you are trying to change the date.
Due date change happens very quickly with no stopper to tell staff that they are changing a due date on a requested item.
Duke doesn’t consider it a go live thing, but it is a nice feature. Same for Chicago. Not a go live for Leipzig either.
Brooks will write this up as a feature and share UXPROD once he has it.
TOPIC #2 Jana Freytag German Librarians did a gap analysis and identified missing features in FOLIO. They created a spreadsheet to share with the group. Possibly a way the group can brainstorm other missing features that members discover. These are features they need for go live.
--UXPROD-2877 Feature exists?
Refuse check in if item is not at primary service point for home location
--UXPROD-2015 Feature exists?
Fees/Fines implementing reminder fee for German Libraries. Note goes out to patron and at that moment a fee is charged on the patron’s account. Brooks says they are a fan because this would solve a problem for them.
Erin suggested putting this gap list out and having people look at these items again. Some of these may be features the German libraries may have to develop themselves.
--Automatic slip printing including printer management A feature is needed (Darcy).
This would be for receipts, pick slips, hold requests, etc. Everything would be printed on a certain printer. Not really scheduled printing; As soon as a request is made, send it to the network printer, (for example, hold request). We want something that bypasses the browser print dialogue box. Brooks says he can’t see a way of implementing this without having FOLIO talking directly to the printers from the server side.
We’d all find this useful, but not sure how many of us could live without it. Interest in this at Cornell. Some folks actually even seem to think it's a pretty big deal, so we might end up ranking this fairly highly.
--UXPROD-1041 Anonymization of request data. A feature is needed (Brooks)
Extremely important for Chalmers. Also for Swedish Library, joining their community. Brooks will update the PO rank on this. He may change some of the tags on it and write up some stories.
--Notices. A feature is needed (Darcy).
Different layers for the types of notices – email, sms, mail. Needs to be configurable by delivery method. Not captured yet. Has been talked about previously, but no action taken yet.
--Bulk editing via UI A feature is needed (Kelly)
Example, change loan date for all patrons via UI. What is the workaround right now? Adapting an API and building a file to load data into that API or writing a sophisticated SQL (not preferred). When you change a loan date you also must go to scheduled notice table and change all the scheduled notice dates. It would be nice to be able to have something in the UI so you could schedule this and define your criteria for what loans should be involved. Changing the notices is where it would get tricky. Writing some workaround documentation. If anyone scripts something for this it should be shared with everyone. We do want it in a UI. Grouping this under bulk editing may not be quite right. No UI to loans outside of the user record. No bulk UI to loans. There is the Circ Log, which may be a way to extend that. When you migrate data, it doesn’t exist in the Circ Log. There is an API into the Circ Log. Or if you use the business logic you could do it.
--UXPROD-2814 Brooks will take this to User Management for discussion
In addition to pop up notes it would be good to show user notes at check out in the account summary on the left side. Being discussed in User Management. When discussed in the past, certain user notes needed to generate a pop-up so that staff would stop because a patron needs to do something before the staff member proceeds. Two things here. A certain kind of note does pop-up and have other kinds of notes show on the left-hand side. And then as a workflow decision you decide which types of notes you will use. When you create the note, you say whether it will be a pop-up or not. Notes modal on the user record is the same component used in eholdings. Some notes are shared by other components. They would like a fixed field on the display on the checkout screen. Perhaps a flag to designate where to display the note. We want certain kinds of notes to be pop-up. On left-hand side we want a display that shows how many notes there are and a link to those notes.
--UXPROD-2016 Ability to override for certain loan functions Feature exists
For example, renewal of hold request in an extraordinary circumstance. Cannot override renewal of an item with a hold. Not sure where this interacts with user permissions. Perhaps this situation wasn’t covered previously because it wasn’t thought about.
--UXPROD-1275_Offline checkouts This wasn’t discussed.
--UXPROD-845 Cash drawer. This feature is scheduled for Juniper.
This is balancing at the service point level and user level. Doesn’t really match a cash drawer like in a retail setting. Assumes one cash drawer at a service point. Doesn’t recognize that there may be 3 different desks each with their own cash.
--Reminder fees are charged as soon as they are incurred. No Feature. See UXPROD 2015.
Fees are charged the moment they are overdue, not totaled when the book is returned. Each day patrons can see the amount of fees that have occurred. Some libraries do this each day depending on their policies, and there may be different fee amounts for the first few days and a different rate for subsequent days.
--UXPROD-2950 Overdue fine policies with staggered fees. Feature created on March 9, 2021 by Holly
--Permissions – need to be more granular. Erin will ask Craig McNally (Ebsco) about it
Staff can see other staff members but not users. Or employees can only see users. Erin says she’s heard this will not be technically possible. Could set CRUD permission on certain records. View versus edit. This is a record level setting. No way to do this for 60,000 users. Can’t see this happening any time soon. Take it to App interactions? They are having discussion about relabeling permission sets. It could be brought up there or with Craig McNally (technical architect with Ebsco).
Discussion on this gap analysis will continue at future meetings.
Thursday’s meeting will discuss training efforts at individual institutions. Are there approaches you could share? Andy Horbal says yes, we have to be training, we’re going live on July 1. He would like to hear from anyone else who is going live. Erin Weller at MSU would love to hear what other folks are doing. Andy can talk about what they are doing at Cornell. If anyone else is doing training, please share your info at Thursday's meeting.