FOLIO Project Update – Week of June 22, 2020

The FOLIO Implementation Group discussed whether institutions that have already implemented FOLIO should form their own group or have their discussions within the current Implementers group. The group decided to keep everything within Implementers for another month or two to see how the volume of communication impacts Implementers communication channels.

The Metadata Management SIG reviewed proposed minor wording changes to the filters and detail view displays of suppression for records in Inventory. They also looked at proposed changes to holdings statement notes, allowing us to distinguish public from non-public. A preferred solution, with some modifications, was identified and Charlotte will share mock-ups with the group to confirm.

The Reporting SIG is preparing the FOLIO Forum presentation, “FOLIO Reporting Update on Community-Developed Reports,” which is scheduled for July 15 from 11:00am to 12:30pm ET. The FOLIO profile of the Library Data Platform now supports Course reserves. Test course reserves data are available in the FOLIO Reporting Reference Environment for query development and testing. The Reporting Data Privacy subgroup is working with the User Management SIG to analyze GDPR requirements for reports on active borrowers.

The Sys Ops & Mgt SIG  followed up on recent discussions about module upgrades with reference data. There is currently no way to flag data that should not be updated. Steve Pampell is pushing this issue forward. More detailed description is needed for reference data. They briefly addressed issues that arose during bugfest testing. Some documentation is missing for Okapi.