2026-04-13 Resource Access Meeting Notes

2026-04-13 Resource Access Meeting Notes

Date: Apr 13, 2026 

 

Recordings

NOTE: RESOURCE ACCESS SIG USES EITHER ZOOM’S AI NOTES FUNCTIONALITY OR GOOGLE GEMINI 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)

 

Zoom

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

Attendees

@Susan Kimball

@Katie Rahman

@Scott Peterson

@David Bottorff

@Thomas Trutt

@Olga Kalachinskaya

@Anja Kakau

@Amelia Sutton

@Robert Heaton

@Cornelia Awenius

@Jamie Jesanis

@Steve Strohl

@Jacob Dudley

@Heather

Discussion Items:

Time

Item

Who

Description

Goals/Info/notes

Time

Item

Who

Description

Goals/Info/notes

5Min

Administrivia

@Susan Kimball

@Katie Rahman

Upcoming meetings:

  • Thursday, April 16th - Fee Fine Subgroup

  • Meeting possible on Monday, April 20th. Susan on vacation next week. Watch Slack for agenda or cancellation by Friday.

  • Calendar Calming - No meetings week of April 27th (April 27th and April 30th)

Announcements:

SMS messaging sub-group met with @Stephanie Buck (Deactivated) on April 1st

Zoom AI or Gemini institutional acct.

35Min

Prioritization Planning

 

Brainstorm prioritization process for RA

 

15Min

RA SIG Description

 

Finalize draft description based on 2026-02-09 and 2026-03-23 discussions

 

Meeting Notes

AI-Generated minutes (pardon any errors)

Based on the combined audio and chat transcripts from April 13, 2026, here is the summary and analysis of the Resource Access SIG meeting.

📄 Meeting Minutes

The meeting served as a collaborative brainstorming session to adapt the ERM SIG's methodical prioritization strategy to the Resource Access SIG context. The members discussed various technical and organizational methods to group granular JIRA tickets into manageable "feature sets" to facilitate community voting and development. Additionally, the group reviewed calendar adjustments for late April, updates on SMS messaging integration, and the final call for WolfCon proposals.

📄 Discussion Points

  • Administrative and Subgroup Announcements (00:08:05 – 00:12:10):

    • Upcoming Meetings: A FeeFine subgroup meeting is scheduled for this coming Thursday. Susan Kimball announced she will be on vacation next week, with Katie Rahman managing the SIG's activities in her absence. A decision regarding the meeting on Monday, April 20th, will be made by Friday based on the evolving agenda.

    • JIRA Ticket Review: The meeting on Thursday, April 23rd, is dedicated to a JIRA ticket review, continuing the progress made during the previous week's session.

    • Calendar Calming: In alignment with FOLIO community practices, no meetings will be held during the last week of April (April 27th and April 30th) to provide members with a "calendar calming" period.

    • SMS Messaging Subgroup: The subgroup met with Steph Buck on April 1st to discuss high-level needs for SMS notifications. They explored whether messaging should be part of the standard notice policy or handled via APIs for external application integration. This conceptual work will eventually be translated into formal JIRA tickets.

    • WolfCon Proposals: Members were reminded that the deadline for session proposals for WolfCon is April 15th.

  • JIRA Prioritization Strategy and Challenges (00:12:10 – 00:47:17):

    • ERM SIG Model Adaptation: Susan Kimball introduced the ERM SIG's strategy, which involves a methodical process of introducing topics, discussing them, and using "thumbs up" voting in JIRA to establish priority. However, the RA SIG faces the challenge of having a significantly larger volume of existing, highly granular tickets (e.g., one feature might span 5-10 tickets), making the ERM model difficult to apply directly.

    • Ticket Grouping Proposals: Robert Heaton suggested rolling granular tickets into broader "feature sets". This would allow the community to vote on a cohesive functionality rather than individual technical components.

    • Technical Implementation Debates:

      • Epics and UXPRODs: Anja Kakau and David Bottorff discussed using Epics or UXPRODs for grouping. Anja pointed out the technical limitation that JIRA does not allow nesting Epics, and many existing RA tickets are already linked to large, multi-year Epics like "Notices".

      • The DIP Process: Thomas Trutt mentioned the Development Improvement Process (DIP), a new high-level tracking method being explored by the Product Council (PC). This process is intended to summarize work at a high level for resource allocation by the PC and Technical Council (TC) while keeping UXPRODs as the actual work items for developers.

      • Separate RA JIRA Space: Thomas Trutt also proposed the possibility of requesting a dedicated JIRA space for the RA SIG. This would allow the group to use custom templates, groupings, and filtering without being constrained by the broader FOLIO project's JIRA structure.

      • Blanket JIRAs and Labels: Anja Kakau suggested creating "blanket" JIRA tickets or using specific RA labels to group related issues without disrupting existing Epic links.

      • Offline Management: Cornelia Awenius suggested using external tools like spreadsheets for the initial grouping work to avoid overcomplicating the JIRA environment prematurely.

    • Utilizing the Gap List: Susan Kimball highlighted that the existing "Gap list" should serve as a primary source for identifying missing features and functionalities that need prioritization. The group was encouraged to add any high-priority items not yet captured on that list.

📄 Action Items and Follow-up

  • Cornelia Awenius: Remove the April 27th and April 30th meetings from the group calendar.

  • Susan Kimball and Katie Rahman: Determine the status of the Monday, April 20th meeting by this Friday and communicate the decision via Slack.

  • Susan Kimball: Update the top-level SIG page with the new group description discussed during the meeting.

  • All Members: Review and submit any final WolfCon session proposals by the April 15th deadline.

  • All Members: Review the Gap list and add any missing high-priority items for use in the upcoming prioritization process.