/
2025-02-13 Resource Access Meeting Notes

2025-02-13 Resource Access Meeting Notes

Owned by Susan Kimball
Last updated: Mar 03, 2025 by Thomas Trutt


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


Zoom

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

Attendees

Jana Freytag

David Bottorff

Rachael Smith

Marie Widigson

Thomas Trutt

Vanessa French

Olga Kalachinskaya

Mark Canney

Christine Tobias

Laurence Mini

Martina Tumulla

Jamie Jesanis

Susan Kimball

Cornelia Awenius

Discussion Items:

Time

Item

Who

Description

Goals/Info/notes

5Min

Administrivia

Cornelia Awenius

Susan Kimball

WOLFCon call for proposals likely coming end of February. Located in Westin Downtown Kansas City.

Note Taker: AI? (Thomas Trutt)


50MinOld Jira ticket review

Continue reviewing Vega tickets older than 4 years.








Meeting Notes

Eureka early adopters, Jana and Thomas - So far, permissions are the most complicated issue on the user end. Eureka permissions are very different than in Okapi. Libraries transitioning to Eureka will need documentation to help with setting up permissions. RA/UM/Implementers could assign a small group to look at this. Implementers in two weeks will be looking at Eureka.  Eureka will be the new platform in Sunflower. EBSCO is working on Dev Ops documentation and will start bringing it over to the project wiki.

Backing up a bit, Eureka is a new platform that has been approved for release as the official platform in Sunflower. It replaces two components that are in the current version of FOLIO. Okapi and the authentication and authorization process. These two modules are replaced with open source modules from outside the FOLIO community. One is called Kong and the other is KeyCloak. Kong is a load balancer, so it allows for the communication between all the different modules and adds a lot of higher level functionality. The one that's causing issues with permissions is KeyCloak, which adds a ton of authentication and authorization features to FOLIO.

Continued reviewing Vega tickets older than 4 years, starting with those labeled "loans". Spreadsheet to track what we have reviewed.

🗣️ Discussion Points

  1. Product Council Meeting Overview (11:00 - 11:05)

    • Quarterly Reports: Introduction of SIG conveners to the product council.
    • Prioritization and SIG Participation: Main topics discussed.
    • Eureka Permissions: Issues with user permissions in Eureka.

  2. Eureka Platform (11:05 - 11:10)

    • Permissions Construct: Changes in permission constructs with Eureka.
    • Task Group Formation: Suggestion to form a task group for user management and resource access.

  3. Wolfcon Announcement (11:10 - 11:12)

    • Location and Call for Proposals: Wolfcon to be held in Kansas City, call for proposals at the end of the month.

  4. Vega Tickets Review (11:12 - 11:20)

    • Spreadsheet Overview: Susan introduced a spreadsheet created from the original 93 UXPROD tickets that were older than four years. These tickets were filtered by Steph and labeled accordingly.

    • Labeling and Filtering: Susan added subgroup labels to the tickets, ensuring that all labels listed in the spreadsheet are now also in JIRA. The link to the JIRA filter with just the loans was shared in the meeting notes section of the agenda.

    • Ticket Review Process: The group reviewed specific tickets, discussing their relevance and whether they should be kept, refined, or closed. Here are the details of the tickets discussed:

      1. UXPROD-1118: Export User Loans List to Excel or CSV

        • Discussion: The current functionality was reviewed, and it was noted that additional fields are needed for exports.
        • Decision: The ticket needs further refinement to include additional fields.

      2. UXPROD-1120: One-Time Escalation of User's Permission

        • Discussion: Temporary override functionality was discussed, with examples from previous systems like Aleph.
        • Decision: It is a low priority but useful feature. The ticket will be kept for further refinement.

      3. UXPROD-1122: Offline Checkouts

        • Discussion: The feasibility of offline checkouts was debated, with alternatives like pen and paper being suggested.
        • Decision: The ticket will be closed due to feasibility issues.

      4. UXPROD-1124: Alert Staff to Special Location at Check-In

        • Discussion: The need for pop-up alerts for special locations was highlighted, with examples from various institutions.
        • Decision: The ticket will be kept as it is a desired functionality.

      5. UXPROD-1126: Renewal Failures and Overrides

        • Discussion: Issues with overrides for renewal failures were discussed, including known failures that don't have overrides.
        • Decision: The ticket will be kept and further refined.

      6. UXPROD-1128: Loan Truncated Due to Recall in Queue

        • Discussion: The need for pop-up alerts for truncated loans was discussed, with suggestions to expand the scope to include all reasons for truncated loans.
        • Decision: The ticket will be kept and potentially merged with other related tickets.

      7. UXPROD-1130: Sort by Normalized Call Number

        • Discussion: Sorting items by call number in various interfaces was discussed, with a focus on the need for proper sorting by call number.
        • Decision: The ticket will be kept and further refined.

      8. UXPROD-1132: Automatic Renewals

        • Discussion: The desire for automatic renewal functionality was discussed, with examples of current scripts used by some libraries.
        • Decision: The ticket will be kept as it is a highly desired functionality.

      9. UXPROD-1134: Add Renewed Date to Loans

        • Discussion: Adding the most recent renewal date to loan records was discussed, with a focus on the use cases for this feature.
        • Decision: The ticket will be kept and further refined to understand the use cases better.

✅ Decisions Made

  • Export User Loans List: Confirmed that additional fields are needed for exports.
  • One-Time Escalation of User's Permission: Agreed that it is a low priority but useful.
  • Offline Checkouts: Decided to close the ticket due to feasibility issues.
  • Alert Staff to Special Location: Agreed on the need for this functionality.
  • Renewal Failures and Overrides: Confirmed the need for better handling of overrides.
  • Loan Truncated Due to Recall: Agreed to expand the scope to include all reasons for truncated loans.
  • Sort by Normalized Call Number: Confirmed the need for proper sorting by call number.
  • Automatic Renewals: Strong interest in having this functionality.
  • Add Renewed Date to Loans: Need to refine the use case for adding renewal dates.

📌 Action Items

  • Susan: Update the spreadsheet with today's discussions and decisions.
  • David: Look into the automatic renewals ticket and provide more details.
  • Thomas: Follow up on the bulk edit functionality for offline checkouts.
  • Marie: Provide feedback on the special location alert functionality.

📊 Data & Insights

  • Eureka Permissions: Significant changes in permission constructs, requiring task group formation.
  • Wolfcon: Announcement of location and call for proposals.
  • Vega Tickets: Detailed review and labeling process for older tickets.

🔄 Follow-Up

  • Next Meeting: Continue the review of remaining Vega tickets and move on to loan policies and rules.
  • Reserve Subgroup Meeting: Scheduled for March 20th.

Related content