2025-03-19 Meeting notes
Date
Mar 19, 2025
Participants
@Maura Byrne
@Laurence Mini
@Erin Weller
@Amelia Sutton
@Christine Tobias
@Tara Barnett
@Thomas Trutt
Goals
Discuss printing features that had been brought up in App-Interaction SIG (FOLIO-3742 - Printing in FOLIO)
Here is a link to a spreadsheet created fair bit ago, where people wrote out use cases for printing. The ones listed below look to be the ones User Management would be most interested in.
To give a staff member a part of a record - a loan history, request history, fee/fine history - in order to research or trouble-shoot an issue.
To give a patron a part of their record - loan history, request history, fee/fine history - in order that they can have a record of what transactions have occurred, outside of what they can view for themselves via a discovery layer interface.
To give a user a check-in history - a patron returning books may ask to have them returned right then and to be given a receipt, esp. If they have disputed returns in the past (e.g., claim returned.) The check-in app will generate a list of returns - being able to quickly/efficiently print that list for a patron is a need.
To give a patron everything of their record - due to GDPR
every data which is stored in FOLIO (except internal comments):
general data incl. address, loans, fees&fines, requests, proxy data, etc.
Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
5 min | Note-taker |
|
|
10 min | Session proposals for WOLF Con | Maura | https://cfp.sched.com/speaker/6WCTz8koYs/event WOLFcon Topics Discussion
|
45 min | Discuss printing features | Amelia | Printing in FOLIO We want to expand the ability to print information in FOLIO easily. Current functionality is very limited. There are 4 specific areas that pertain to Users (See goals above). Discussed the 4 areas. Bullet points 2 and 3 are useful but not a high priority. Bullet point 4 is needed for GDPR but not for those of us in the meeting. |
| Reviewed old Jira tickets | Amelia | https://folio-org.atlassian.net/browse/UIU-3051 - Is this a priority? Those of us in meeting do not use the User field so this is not a high priority for us. https://folio-org.atlassian.net/browse/UIU-3231 - Keep this at the low priority it is currently set at. https://folio-org.atlassian.net/browse/MODUSERBL-12 - Could be useful. Could simplify a lot of record update processes but not really necessary and not a high priority. https://folio-org.atlassian.net/browse/UXPROD-552 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-553 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-554 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-556 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-778 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-2444 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/UXPROD-3077 - very old, no interest in developing, closing it https://folio-org.atlassian.net/browse/FOLIO-2052 - This is a priority as we’re interested in bulk deleting patron records. Maybe this should fall under Bulk Edit. Amelia will add this to the UM Gap List. https://folio-org.atlassian.net/browse/UIU-1813 - Most of this could be covered by Custom Fields. Might be nice to filter users that shouldn’t be deleted. Closing this ticket. https://folio-org.atlassian.net/browse/MODUSERS-229 When we look at Bulk Delete we can look at this ticket as well and maybe link them or close one. https://folio-org.atlassian.net/browse/MODUIMP-34 No need for this. Closing. |