SIG Reports 2025-12-18

SIG Reports 2025-12-18

Reports should include:

  • Discussion of specific development areas. Including Jira issues for both features and bugs is helpful.

  • Work related to the FOLIO Roadmap or work that occurred that is not well-represented on the FOLIO roadmap.

  • Information about demos, user discussions, or future functionality for FOLIO.

  • Spins-ups or wind-downs of specific subgroups or working groups in a particular area.

  • Ideas or issues that came up feel outside the scope of the SIG but need commenting.

When you click on Submit Request, this will create a new wiki page that will need to be published. To submit a request,





SIG NAME

SIG Convenor(s)

PC Liaison

Report and Include any relevant JIRA issues

SIG NAME

SIG Convenor(s)

PC Liaison

Report and Include any relevant JIRA issues

Acquisitions SIG

@Heather McMillan

@Autumn Faulkner  

1. Fiscal Year Management

The group has been examining questions related to paying invoices in future fiscal years and exploring how institutions manage multiple concurrent fiscal years. Members are seeking clarity on recommended workflows and whether specific practices are supported or expected within FOLIO.

2. Fund Balancing Discrepancies (Implementers Topic 188)

A recurring issue has been identified when comparing fund reports with information displayed in the FOLIO fund screens. When a fund has a credit balance, the Unavailable field currently shows a value of $0.00, rather than reflecting the actual credit amount. The group recommends that FOLIO display the true credit balance on fund screens, with any filtered or adjusted representations handled through dashboards rather than altering core fund data.

3. Need for POL Duplication Functionality (Implementers Topic 189)

While users can currently duplicate entire purchase orders, there is strong interest in the ability to duplicate purchase order lines (POLs). This functionality would be especially valuable for orders containing numerous POLs, some of which are identical. Templates do not meet this need, as confirmed by the Bavaria team. The group proposes options such as a “Duplicate POL” entry in the actions menu or a “Save & duplicate” option during POL creation.

4. UIREC-350: Editing Piece Receiving Locations

The group also reviewed UIREC-350, which concerns the behavior when editing a piece’s receiving location. Members support presenting a “Delete or Keep Holdings” modal when the receiving location is changed, to ensure holdings are managed consistently and transparently.

5. New convener for 2026. @Susanne Gill

App Interaction SIG

@Tara Barnett

@Martin Scholz



Consortia SIG

@Lucy Harrison & @Former user (Deleted)

@Lucy Harrison



Data Import SIG

@Christie Thomas , @Jennifer Eustis

@Jennifer Eustis

 

Discovery SIG

@Nicole Trujillo

 

  • Number 1 community priority updated with new Jira work tbd, UXPROD 4805.

  • Discovery Jiras identified and placed in dashboard via labels. Ongoing assessment of new Jiras created that may have discovery platform implications.

  • Discussions on linked data, ways of going between discovery environments and FOLIO, or viewing FOLIO information in discovery.

Documentation Working Group

@Ludwig Liebl

@Martina Tumulla 



ERM SIG

@Martina Schildt 

@Charlotte Whitt



Implementers SIG

@Thomas Trutt 

@Charlotte Whitt



Linked Open Data

@Laura E Daniels & @Chris Long

@Charlotte Whitt & @Lisa McColl



Metadata Management

@Felix Hemme  & @Raegan Wiechert 

@Jennifer Eustis

  • There was a working meeting at WolfCon to begin the discussion of the UI in Inventory and making it better able to adapt to different users and differing needs.

  • Discussed the need for an acquisition date that can be filled in manually (i.e. something not only tied to Orders data)

  • Discussed enhancements to bound-withs to make it more clear what is part of a bound-with and also to more clearly mark which record is the “parent” record; also the possibility of being able to change the sort order of bound-withs.

  • Presentation by Stanford on an authorities workflow process

Open Access SIG

@Martin Bauschmann

@Alexis Manheim



Privacy SIG

@Schwill, Carsten  & @Adam Chandler 

@Thomas Trutt



Public Library SIG

@Joseph A Molloy

@Lisa McColl



Reporting SIG

@Sharon Markus  & @Scott Perry 

@Jennifer Eustis 

Reporting SIG working on:

  • Development priorities are on the Community Priorities Dashboard in the Reporting SIG section

  • Metadb Data Privacy Subgroup of Reporting SIG working on requirements for data privacy and data anonymization features for Metadb software development

  • Reporting App permissions requirements and UI development

  • Documenting and escalating bugs and issues impacting reporting software

  • Offering information sessions on reporting tools such as Lists App, Reporting App, LDLite, and Metadb

Resource Access

@Susan Kimball & @Cornelia Awenius 

@Jana Freytag 



SIG Conveners

@Martina Schildt 

 

Meetings are held twice a year. Next meeting will take place in March 2024.

System Operations and Management SIG

@Ingolf Kuss 

@Ingolf Kuss 



Support SIG

@Anya & @Debra Howell 

@Autumn Faulkner





User Management

@Maura Byrne 

@Maura Byrne 



Workflow SIG

 

 

@Lisa McColl







Dormant SIG

Dormant Since

Dormant SIG

Dormant Since

Accessibility

Sep 24, 2022 

Privacy SIG

Oct 19, 2023