2025-05-12 Resource Access Meeting Notes

🗣️ Discussion Points:

1. Introduction and Agenda Adjustment (11:02:33 - 11:03:00):

   • Overview: Susan welcomed everyone and noted a good turnout with 15 participants. She mentioned a change in the agenda, postponing the fee fine user interface discussion to next Monday to focus on more pressing matters.
   • Complications: The urgency stemmed from the need to quickly gather the top five development priorities for the product council, which had caught them off guard.

2. Prioritization Process (11:03:00 - 11:08:12):

   • Discussion: Susan and Cornelia had met earlier and realized the importance of getting their SIG's priorities on the product council's list. A couple of weeks ago, they were asked to provide their top five development priorities with a very tight turnaround, which they weren't prepared for.
   • Proposal: Jana explained that each priority needed to have a JIRA ticket attached, complete with a detailed story and description. This was part of a new prioritization process that the product council was implementing.
   • Complications: David sought clarification on whether the priorities should include projects with known external funding, such as the "building use only" request type work, which is being done outside the current developers but contributed back to the main code.

3. Development Priorities (11:08:12 - 11:12:04):

   • Discussion: David emphasized the need to distinguish between priorities that have external funding and those that don't. Susan agreed, suggesting that their top five priorities should focus on areas without allocated resources.
   • Proposal: Susan asked Jana for her perspective based on conversations she had had, and Jana clarified that the prioritization was more about community needs rather than available funds.
   • Complications: Cornelia pointed out that some priorities on the current dashboard didn't have JIRA tickets linked or were still drafts. Jana explained that these tickets needed to be fleshed out to give a clear picture of the development time required.

4. Specific Development Needs (11:12:04 - 11:19:05):

   • Discussion: Various participants discussed specific development needs, such as request anonymization and loan anonymization. Susan suggested that they should allocate their top five priorities to areas without allocated resources.
   • Proposal: Susan proposed using a spreadsheet to rank priorities asynchronously, allowing everyone to contribute their input.
   • Complications: The challenge was to define these priorities quickly and ensure they were well-documented in JIRA tickets.

5. JIRA Tickets and Features (11:19:05 - 11:27:40):

   • Discussion: Participants mentioned specific JIRA tickets and features, including UXPROD-1879, UXPROD-4470, and UXPROD-3651. Cornelia suggested adding new patron notice policy triggers to the list.
   • Proposal: Susan encouraged everyone to add relevant JIRA tickets to the spreadsheet and flesh them out as much as possible.
   • Complications: The need to quickly develop detailed JIRA tickets was emphasized, as this would be crucial for the prioritization process.

6. Remote Storage and Implementers Group (11:27:40 - 11:35:07):

   • Discussion: David highlighted the importance of remote storage work for UChicago, noting that it was a high priority for them. Thomas suggested adding remote storage as a separate line item in the prioritization list.
   • Proposal: Thomas proposed discussing with the product council to add remote storage as its own SIG, given its importance.
   • Complications: The overlap between different SIGs was discussed, with implementers and public libraries often having overlapping priorities.

7. Additional Priorities and Points Allocation (11:35:07 - 11:47:02):

   • Discussion: Participants discussed additional priorities, including automatic renewals and batch renewals. Susan suggested that they should allocate points to rank these priorities.
   • Proposal: Susan proposed a system where each institution could allocate a certain number of points to the priorities they deemed most important.
   • Complications: The tight timeline for prioritization was acknowledged, and the need for a clear process was emphasized.

8. Timeline and Next Steps (11:47:02 - 11:53:09):

   • Discussion: The timeline for adding items to the spreadsheet and allocating points was discussed. Jana offered to ask for an extension from the product council to give them more time.
   • Proposal: Susan suggested aiming for a week to complete the prioritization process, with institutions adding their items by Wednesday and allocating points by the following Monday.
   • Complications: The need for a clear process and deadlines was emphasized to ensure they could meet the product council's requirements.

✅ Decisions Made:

• Postponement: The discussion on the fee fine user interface was postponed to next Monday to focus on more urgent matters.
• Prioritization Process: They decided to use a spreadsheet to rank development priorities asynchronously, allowing everyone to contribute their input.
• Points Allocation: Institutions would allocate points to rank priorities, aiming for completion by next week.
• Extension Request: Jana would request an extension from the product council to give them more time to complete the prioritization process.

📌 Action Items:

• Spreadsheet Creation: Susan would create and share the spreadsheet for ranking priorities.
• JIRA Ticket Addition: Participants would add relevant JIRA tickets to the spreadsheet and flesh them out as much as possible.
• Extension Request: Jana would request an extension from the product council to give them more time to complete the prioritization process.
• Points Allocation: Institutions would allocate points to rank priorities by the 19th.

📊 Data & Insights:

• Prioritization Needs: The need for detailed JIRA tickets and clear prioritization was emphasized throughout the meeting.
• Development Work: Various development needs were discussed, highlighting the importance of specific features and the urgency of getting them prioritized.

🔄 Follow-Up:

• Next Meeting: A follow-up meeting was scheduled for next Monday to continue the discussion and finalize the prioritization process.
• Spreadsheet Updates: Participants were encouraged to update the spreadsheet with their priorities by Wednesday.

🐝 JIRAs:

• JIRA:UXPROD-1879: Feature related to fee/fines.
• JIRA:UXPROD-4470: Feature unspecified.
• JIRA:UXPROD-3651: Feature related to automatic renewals.
• JIRA:UXPROD-2112: New triggers for notices.
• JIRA:UXPROD-2285: Filtering requests by item effective location.
• JIRA:UXPROD-1835: Reading room only checkouts.
• JIRA:UXPROD-3266: Splitting refund and credit transactions.
• JIRA:UXPROD-4000: New patron notice policy trigger for automated lost fees.
• JIRA:UXPROD-4001: New patron notice policy trigger for paying automated overdue fines.