2025-04-17 Reserves Meeting notes
Date
Apr 17, 2025
Recordings
NOTE: RESOURCE ACCESS SIG USES EITHER ZOOM’S AI NOTES FUNCTIONALITY OR MICROSOFT COPILOT TO PROCESS THE TRANSCRIPT. If you would prefer that we do not use AI any session you attend, we are happy to! Please alert the convener at the start of the meeting.
Find all recordings here: Resource Access SIG (FOLIO) | FOLIO Meeting Recordings (pw: folio-lsp)
Zoom
Join our Cloud HD Video Meeting (pw: folio-lsp)
Participants
Olga Kalachinskaya
Thomas Trutt
Amelia Sutton
Robert Heaton
Shannon Cunningham
Erin Weller
Paivi Rentz
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Administrivia | Olga Kalachinskaya |
For reference: Jira tickets labelled “Courses that are not closed” UXPROD Template to use for new feature requests |
30 min | Review of the draft tickets of the new features if any prepared | RA-Reserves members | If you added any new features' suggestions to the Google sheet, please consider creating a Jira ticket for it using the UXPROD Template and we can review it at the meeting. |
25 min | Review of the edits to the existing tickets if any prepared | RA-Reserves members | Please remember to pick one of the existing UXPROD tickets from the Google sheet and consider what edits it might need. Add your name to the “Reviewed By” column of that ticket. |
🗣️ Discussion Points:
WolfCon Submissions (11:07:52 - 11:09:05):
Thomas encouraged the group to consider submitting presentations or working groups for WolfCon, with the deadline approaching on April 25th.
He highlighted the availability of remote presentation options due to travel restrictions and budget cuts, making it easier for those unable to attend in person.
Review of Tickets (11:11:16 - 11:29:48):
Introduction (11:11:16 - 11:11:37):
Olga initiated the review of tickets.
The focus was on JIRA-2955, which had been divided into three separate tickets for better manageability.
Export Courses Info (11:12:04 - 11:13:58):
Olga presented the first ticket, which involved exporting course information to a CSV file.
The export would include all fields related to the selected courses, useful for record-keeping, placing on circulation desks, and reporting comparisons.
Thomas suggested sharing the ticket details in the chat for a quick review.
The group discussed the language and functionality of the export button, ensuring it was clear and user-friendly.
Export Items Info (11:15:11 - 11:16:40):
The second ticket focused on exporting item information attached to courses.
This export would also be to a CSV file, with a button added to the course detail page.
The use cases were similar to the previous ticket, emphasizing the need for detailed item information for various administrative purposes.
Olga shared a screenshot to illustrate the proposed changes, ensuring everyone understood the functionality.
Export Courses and Items Info (11:17:13 - 11:18:21):
The third ticket combined the export functionality for both courses and items.
Olga proposed naming conventions to differentiate between the export buttons. This export might have potential high data volume for some libraries.
Thomas suggested consulting with UX experts like Kimmy for naming and UI consistency.
The group agreed that the names could be updated later based on feedback from the development team and UX experts.
Review of UXPROD-4869 (11:24:15 - 11:29:48):
The ticket involved moving the "Add Item" button to the top of the list for better usability.
Olga reviewed the proposed changes, including mock-ups and potential UX feedback.
The group discussed the layout, with Thomas noting that FOLIO typically uses a one-third two-third split pattern rather than a 50-50 split.
Thomas suggested the possibility of a collapsible portion to manage screen space better.
The group agreed to update the ticket with the proposed changes and seek further UX feedback.
✅ For the next meeting:
Members of the group who added new features to the Google sheet will create draft tickets and we will review them at the meeting.
Each member of the group will present an existing ticket that they picked from the list and suggest the edits if any needed.