2025-11-04 FOLIO Implementers Meeting Notes

Nov 4, 2025

• Housekeeping (5-min.)

• RFID integration

• What is RFID generally? See https://en.wikipedia.org/wiki/Radio-frequency_identification

• What are RFID tags used for in libraries?

  • Circulation, both mediated and unmediated

  • Inventory/Shelf-Reading

  • Automated materials handling (AMH)

  • Security/Exit Gates

• What other technologies/vendors are involved in RFID functionality in the FOLIO community?

Link to recording: https://recordings.openlibraryfoundation.org/folio/implementation-group/2025-11-04T11:00/

@Tara Barnett @Darsi Rueda @Thomas Trutt Felix Wichmann, Johannes Gutling, Charlotte Whitt, Susan Kimball, Kate Deibel, Stephanie Kaceli, Roy Viado, Magnus Andersson, Joseph Molloy, Lisa Perchermeier, Olga, Martina Tumulla, Kajsa Backius, Valerie Sain, Cody N, Bjorn Muschall, Qi, Maura Byrne, Martin Scholz, Anja Kakau

• Overview: Thomas opened with reminders about the upcoming PC update on November 6 and shared the Topic Calendar & Idea Bank link for planning remaining 2025 meetings and brainstorming 2026 topics.

• Proposal: Invitation for volunteers to serve as co-convener for Implementers SIG. Emphasized minimal workload and collaborative nature of the role.

• Complication: Lack of new ideas for 2026; call for contributions.

• Background:

  • Bavarian libraries migrated to FOLIO ~1.5 years ago; RFID support became essential for advanced colleges.

  • Legacy system (CSIS) had RFID integration; goal was to replicate and improve workflows in FOLIO.

• Workflows Identified:

  • Tag Initialization & Editing: Writing barcodes and metadata to RFID tags.

  • Circulation: Check-in/out at service desks; batch processing for multiple items simultaneously.

  • Security Gates: Mentioned for completeness but not core focus.

• Technical Approach:

  • Developed RFID Connect Stripes app integrated into FOLIO UI.

  • Challenge: Browser-based Stripes lacks direct hardware access → solution was a local web server acting as a proxy between RFID hardware and browser.

  • Connector uses JSON-based interface (preferred over XML for simplicity).

• Demonstration Highlights:

  • Circulation tab mimics FOLIO check-in/out UI with batch processing capability.

  • Displays item security status, completeness of multi-part items, and links to inventory records.

  • Supports check-in/out operations with real-time RFID tag updates.

  • Tag editing modes: Full Automatic, Semi-Automatic, and Manual for flexibility.

  • Permissions model implemented for granular control (e.g., restricting “Delete Tag” to avoid accidental data loss).

• Security Concerns:

  • Running a local web server raised institutional IT policy issues.

  • Suggested mitigations: limiting exposed endpoints, Docker containerization, or browser extensions.

• Interlibrary Loan (ILL) Workflow:

  • Developed mechanism for temporary adoption of foreign RFID tags during ILL transactions.

• Future Vision:

  • Introduce a Stripes hook for RFID connectivity, enabling multiple apps to leverage RFID services.

  • Align with ALMA-like standards for interoperability.

• Thomas praised UI design and suggested exploring overrides for blocked items.

• Maura raised concerns about permissions for tag deletion to prevent errors; confirmed granular permissions exist.

• darsi asked about Keycloak/Eureka compatibility; Felix noted future adjustments needed.

• Charlotte proposed presenting demo to PC and TC councils for feedback and alignment with FOLIO development standards.

• Additional Ideas:

  • Add RFID indicator property in item records.

  • Support multiple barcodes per item for complex collections and ILL scenarios.

• Resources Shared: GitLab links for RFID Connect app and connector; English README available.

• Technical Notes: Connector uses .NET/ASP for Windows; other vendor tools (e.g., Bibliotheca Staff Connect) also exist.

• Consensus: Strong interest in formalizing RFID support in FOLIO; demo considered a solid starting point for community adoption.

• Agreement to share demo resources and presentation via Slack for broader review.

• Consensus to pursue PC/TC engagement for feedback and potential roadmap inclusion.

• Permissions model for RFID Connect confirmed as necessary for production environments.

• RFID adoption varies across institutions; some use single tags per item, others multiple tags for multi-part items.

• Batch processing significantly improves circulation efficiency compared to single-item workflows.

• Permissions granularity is critical for mitigating operational risks (e.g., accidental tag deletion).

• Next Implementers SIG meeting will revisit RFID topic and review feedback from PC/TC demo.

• Felix to provide updated app documentation and explore Keycloak/Eureka compatibility.

• No specific JIRA numbers mentioned during meeting.

• RFID Connect (Stripes app)

• RFID FOLIO Connector (local web server)

• Bibliotheca Staff Connect (vendor solution)