2025-03-06 Reserves Meeting notes

Mar 6, 2025

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: https://recordings.openlibraryfoundation.org/folio/resource-access-sig/ (pw: folio-lsp)

https://zoom.us/j/337279319 (pw: folio-lsp)

Ann Kuo

Migena Rrapushaj

Christine Tobias

Jamie Jesanis

Erin Weller

Thomas Trutt

Robert Heaton

Anja Kakau

Shannon Cunningham

Olga Kalachinskaya

Cornelia Awenius

Amelia Sutton

1. Review of Previous Meeting Suggestions (11:03 - 11:06)

   • Olga shared the table of suggestions and noted no new suggestions were added after the last meeting.

   • Anja pointed out a duplicate suggestion (Line 96) and proposed combining it with another similar suggestion. This was agreed upon to avoid confusion and ensure clarity in voting.

2. Top Suggestions and Their Rankings (11:06 - 11:10)

   • Olga reviewed the top-ranked suggestions based on scores:

     • Move "Add by Barcode" and "Fast Add" to the top of the page: This suggestion received the highest ranking due to its potential to improve workflow efficiency.

     • Link electronic records in ETS: This was the second-highest ranked suggestion, emphasizing the need for better integration of electronic records.

     • Allow addition of electronic items to a course without creating a fake barcode (Ticket #102): This suggestion aims to streamline the process of adding electronic items to courses.

     • Refresh courses after an item is associated with the course: This suggestion focuses on improving the synchronization between courses and inventory records.

3. Detailed Discussion on Top Suggestions (11:10 - 11:19)

   • Thomas explained the need for detailed descriptions and use cases for the "Add by Barcode" and "Fast Add" suggestion. He emphasized the importance of specifying the expected improvements and providing a mock-up for the front-end developers.

     • Discussion Points:

       • The current placement of the "Add by Barcode" and "Fast Add" features causes the page to scroll to the top, which is inconvenient for users.

       • Moving these features to the top of the page would enhance usability and reduce the need for excessive scrolling.

   • Linking electronic items to courses: This suggestion requires more detailed planning, including considerations for inventory and course management systems.

     • Discussion Points:

       • Determine whether to link holding records or item records.

       • Consider the creation of dummy records for electronic items.

       • Ensure the functionality aligns with existing systems and user needs.

4. Review of Existing Tickets and New Suggestions (11:19 - 11:24)

   • Olga and Thomas discussed the process of reviewing and creating new tickets. They emphasized the importance of detailed descriptions and the need to group tickets by areas for better organization.

   • Anja suggested grouping tickets by areas such as interface changes, additional fields, and sorting functionalities. This would help streamline the review process and ensure that related tickets are addressed together.

5. Action Plan and Homework (11:24 - 11:30)

   • Olga outlined the next steps:

     • Group existing tickets in JIRA for better organization.

     • Participants who added new features will write detailed summaries for them.

     • Review the list of tickets before the next meeting to identify low-hanging fruits and prioritize them for discussion.

   • Discussion Points:

     • The importance of efficient time management during meetings.

     • The need to focus on easily implementable suggestions first to make quick progress.

6. Miscellaneous (11:30 - 11:31)

   • Erin mentioned a specific issue (Ticket #92) that might be resolved by EBSCO. She suggested removing it from the list if resolved, as it may be a settings issue specific to Michigan State University.

     • Discussion Points:

       • The importance of verifying whether issues are institution-specific before adding them to the general list.

       • The need for follow-up with EBSCO to confirm the resolution of the issue.

• Combine duplicate suggestions to avoid confusion.

• Group existing tickets in JIRA for better organization.

• Participants who added new features will write detailed summaries for them.

• Olga: Group existing tickets in JIRA and add linked issues for each group.

• Participants: Write summaries for new suggestions and review the list before the next meeting.

• Erin: Follow up on the issue with EBSCO and remove it from the list if resolved.

• The highest-ranked suggestions were identified based on scores.

• Detailed planning and descriptions are crucial for implementing suggestions effectively.

• Next meeting scheduled in two weeks to review grouped tickets and new summaries.

• Participants to complete their assigned tasks before the next meeting.