2025-02-06 Reserves Meeting notes

Feb 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: Resource Access SIG (FOLIO) | FOLIO Meeting Recordings (pw: folio-lsp)

Join our Cloud HD Video Meeting (pw: folio-lsp)

• Olga Kalachinskaya

• Wendy Jones

• Clay Oldham

• Kim Shaw

• Ann Kuo

• Shannon Cunningham

• Erin Weller

• Thomas Trutt

• Jamie Jesanis

• Robert Heaton

• Catherine Descanzo

• Anja Kakau

• Cornelia Awenius

1. Introduction and Overview (11:00:54 - 11:03:01)

   • Olga welcomed attendees and provided a brief overview of the meeting's purpose.

2. Review of Existing Tickets (11:03:01 - 11:09:34)

   • Olga initiated the discussion by reminding everyone about the existing tickets and their importance for the libraries. She asked if there were any questions or concerns regarding these tickets.

   • Erin raised two specific tickets that had question marks, indicating uncertainty about their meaning and relevance:

     • Ticket Line 77: "Enable optimistic locking for courses app."

       • Thomas explained that this ticket likely originated from the developers. He described optimistic locking as a mechanism used in inventory to prevent multiple users from editing the same record simultaneously. This feature ensures that once a user opens a record, no one else can edit it until the first user is done. He speculated that the ticket was part of a broader effort to implement optimistic locking across various areas of the app.

       • Robert added that optimistic locking allows multiple users to access the same record but applies their edits in the order they were made. This can create issues if changes overlap, as there is no clear intermediate version of the record. He suggested that this feature might cause problems but acknowledged that it could be beneficial in certain contexts.

       • Olga mentioned that she had initially ranked this ticket low due to her lack of understanding but considered revising her ranking based on the new information.

     • Ticket Line 80: "Add reserve count field to course reserve courses response."

       • Olga explained that this ticket aimed to optimize API calls by reducing them from two to one when checking course reserves. This would improve efficiency by only displaying relevant information if there were items in the course reserve.

       • Erin noted that her institution uses both EDS and Viewfind, but the ticket seemed more relevant to EDS. She decided to keep her ranking low as it did not significantly impact their system.

   • Catherine pointed out that there were items (lines 82 to 85) without actual ticket numbers and asked if this was the appropriate place to add new features.

     • Olga confirmed that these items were from a gap list discussed in a previous meeting. She suggested that libraries proposing new features should create the corresponding tickets to ensure clarity and proper documentation.

   • Cornelia (UB Mainz) added that she had contributed one of the items without a ticket number and supported the idea of adding more features to the list.

   • Olga proposed that the group should continue adding new features to the list and create tickets for them. She emphasized the importance of having the proposing library create the ticket to provide detailed explanations if needed.

3. Ranking and Prioritization of Tickets (11:09:34 - 11:17:13)

   • Olga reviewed the rankings of the existing tickets and highlighted the most popular features:

     • Sorting and Refresh Button: High ranking for issues related to sorting and the need for a refresh button to sync changes between inventory and courses.

     • Multiple Terms for a Single Course: Popular feature request to allow multiple terms to be added to a single course, addressing issues with extending course terms across semesters.

     • Electronic Records in Course Reserves: High demand for including electronic records in course reserves.

     • Item Search and Export Results: Requests to allow users to add items to courses via item search and to export course results.

     • Bulk Edit and Reserve Count: Features for bulk editing courses and adding reserve count to course search results.

   • Erin and Thomas provided input on the ranking process and the importance of refining tickets. They discussed the need to focus on high-priority tickets and ensure they are well-documented for easier pickup by developers.

4. Adding New Features and Refining Tickets (11:17:13 - 11:31:07)

   • Olga suggested adding new features to the list and refining the top-ranked tickets. She emphasized the importance of having a comprehensive list to present to the product council.

   • Thomas highlighted the importance of refining tickets for easier pickup by developers. He explained that well-documented tickets are more likely to be addressed by development teams, even if there is no immediate commitment.

   • Robert suggested focusing on high-priority tickets and considering the concept of "low hanging fruit" – features that are high priority but require less development effort. He inquired about the process for estimating the size and effort required for each ticket.

     • Thomas explained that size estimates are typically done by the development team. He suggested that the group could ask developers to provide rough estimates for the top-ranked tickets to help prioritize them.

   • Olga proposed that the group should add all necessary features to the list and rank them. She assigned homework to attendees to add missing functionalities and rank them before the next meeting. She also suggested that the group could refine the top-ranked tickets together in future meetings, with guidance from Thomas.

5. Next Steps and Homework (11:31:07 - 11:33:40)

   • Olga assigned homework to attendees to add missing functionalities and rank them before the next meeting.

   • Thomas offered to assist with refining tickets in future meetings.

✅ Decisions Made:

• Attendees agreed to add new features to the list and refine the top-ranked tickets.

• It was decided to present the comprehensive list to the product council for further action.

📌 Action Items:

• All Attendees: Add missing functionalities to the list and rank them before the next meeting.

• Olga: Organize the list and prepare it for presentation to the product council.

• Thomas: Assist with refining tickets in future meetings.

📊 Data & Insights:

• Insights on the importance of optimistic locking and its implications for the courses app.

• Discussion on the need for a mechanism to reduce API calls for course reserves.

🔄 Follow-Up:

• Next meeting scheduled for February 20th to review the updated list and discuss further steps.

Feel free to let me know if you need any additional details or modifications!