Notes:

📄 Meeting Minutes:

🗣️ Discussion Points:

🧭 Support Channels Overview (00:00–00:01)

• Overview: Thomas outlined the available support channels for Folio users, including Slack channels, the folio support email, and the TDX portal. A TinyURL was shared for easier access to the TDX portal.
• Proposal: Encouraged users to post issues in any of the support channels for visibility and quicker resolution.

🏛️ WolfCon 2025 Announcement (00:01–00:01:14)

• Event Details: Scheduled for September 23–25 in Kansas City, with both in-person and virtual options.
• Call for Submissions: Open for presentation proposals.
• Workshops: Pre-conference workshops will return, including AI-focused sessions.

🚦 Release Status Updates (00:01:14–00:03:17)

• Ramsense: Released for general use but not yet adopted due to a blocker bug affecting automated patron blocks. Vega team is addressing the issue.
• Sunflower: Entering Bugfest next week. Uses the new Eureka platform. Expected release: mid-May to early June.
• Trillium: In pre-development. May be released late 2025 or early 2026.

🔧 🌐 Eureka Platform & Keycloak Integration (00:03:17–00:07:45)

• Eureka: Replaces Okapi with Kong for better stability and security. Groups microservices into larger containers.
• Keycloak: Replaces Folio’s current login and permissions system. Offers enhanced security and granular access control.
• Permissions Overhaul: All permissions will need to be reconfigured for Sunflower. New features include time-based access and creator-only edit rights.

🔍 New Features & Enhancements (00:07:45–00:10:09)

• Reading Room Access: Developed for Library of Congress; allows access control for physical spaces.
• In-House Use Requests: Persistent item requests during patron use.
• Mediated Requests: Staff-mediated request processing, similar to Aeon.
• List App: Enables item list creation and metadata updates.
• Reports App: Allows small-scale reporting within Folio.
• Bulk Edit & Query Engine: Expanded capabilities and UI enhancements.
• Platform Stabilization: Focus for Trillium and Umbrella Leaf releases.

🧪 Reporting & Schema Change Communication (00:12:07–00:21:04)

• Discussion: Vandana and Sharon raised concerns about unannounced schema changes disrupting reporting workflows.
• Proposal: Include schema changes in release notes.
• Complications: Schema changes often undocumented or buried in JIRA tickets.
• Decision: Thomas will discuss with Product Owners (POs) and advocate for a dedicated schema change section in release notes.

📅 Release Timeline Clarification (00:21:04–00:21:44)

• Ramsons: Expected in 3–4 weeks.
• Sunflower: Mid-May to early June.
• Trillium: Likely early 2026.

🧩 Feature Adoption Strategy (00:21:44–00:25:11)

• Discussion: New features like mediated requests depend on departmental interest and external system compatibility.
• Reporting App: Under testing with MetaDB. Caution advised due to potential impact on production.

🐞 Circ Log Errors & PubSub Issues (00:25:11–00:31:02)

• Issue: Stephanie reported incorrect attribution in circ logs.
• Cause: Possibly due to PubSub, a deprecated messaging system.
• Resolution: Thomas will escalate to Vega and investigate replacement with Kafka events in Trillium.

🧠 Feature Requests & Ideas (00:31:02–00:43:00)

• Call Number Sorting: Joanne requested long-standing fix for holdings-level call number sorting.
• Circulation Count in Item Records: Suggested for selectors and general usage tracking.
• UI Customization: Requests for background color options and app icon reordering.
• Discussion: Feature requests should be submitted via TDX or Slack with “idea” tags. Community support increases implementation likelihood.

📚 Folio Friday Format Suggestions (00:43:00–00:44:08)

• Suggestions:
  • Review new release features collectively.
  • Share departmental use cases.
  • Continue open Q&A format.

✅ Decisions Made:

• Thomas will:
  • Advocate for schema change documentation in release notes.
  • Investigate circ log attribution errors with Vega.
  • Track and support feature requests through TDX and Slack.
• Reporting team will continue testing the reporting app under MetaDB cautiously.

📌 Action Items:

📊 Data & Insights:

• Release Delays: Historical delays of 1–4 weeks for major releases.
• Security Enhancements: Keycloak introduces time-based access and creator-only edit rights.
• Reporting Impact: Schema changes significantly disrupt reporting workflows, necessitating better communication.
• PubSub Issues: Identified as a root cause for multiple circulation-related bugs; replacement planned.

🔄 Follow-Up:

• Next Folio Friday to include:
  • Review of new release features.
  • Departmental use case sharing.
  • Continued Q&A and feedback collection.

💻 Related Projects:

• MetaDB – Reporting database integration.
• List App – Metadata management.
• Reporting App – In-app reporting tool.
• Bulk Edit – Enhanced editing capabilities.
• Eureka Platform – New backend architecture.
• Keycloak – New authentication and permissions system.
• PubSub – Deprecated messaging system.
• Kafka Events – Planned replacement for PubSub.