Page Comparison

Announcements/Reminders

Impacts of New Fields and Features (Sharon)

• Are there any new fields or features we should know about from any of the functional areas that may impact reporting?
• Review and update the Impacts of New Fields and Features on Reporting grid 

FOLIO Analytics Update

• Poppy and FOLIO Analytics 1.7 were both released in December.

Metadb Update

• see important bug announcement for Metadb
• https://github.com/metadb-project/metadb/issues/58
• from Nassib: It is recommend that users not rely on transformed tables that are generated from any table containing more than one jsonb column. The most likely fix for this bug in the short term is that such transformed tables will be removed.
• (from Tod) There should be a way to interrogate the Postgresql schemata to find out which tables have more than one JSONB column
  • can use the `information_schema.columns` view
• Only one table known so far re: #58: folio_entities_links.instance_authority_linking_rule

Upcoming meeting topics (tentative)

• Reporting Documentation Update for Poppy (January) 
• Metadb version 1.2 release overview (February)

Any new members?

• Welcome/introductions

• Representative for the Documentation Working Group
• Query developers - possibly from Index Data?
• FOLIO Analytics Review Board 

Meeting time and frequency discussion

Proposed Revised Structure

In the interest of reducing the current number of reporting meetings and some other consolidation efforts, we propose changing the structure for reporting meetings and work as follows:

• ACQ/ERM and RA/UM/MM report development groups merge into Metadb FOLIO User Group. Reporting SIG meetings would have regular time for lab work for workshopping query questions.
• Metadb FOLIO User Group, through Nassib’s continued leadership, will be used to work on folio-analytics development in preparation for each FOLIO (flower) software release, will cover new reporting methods and features, will replace the Query Review Board, etc. This meeting would also have regular time for lab work for workshopping query questions. This meeting could be combined with other projects at some point (e.g., Reshare). 
• Reporting SIG meetings would be consolidated to meeting twice per month at 11am ET on the second and fourth Mondays of the month. Reporting SIG meetings would continue to cover ongoing topics of interest to the reporting community. Reporting SIG meetings would also have regular time for lab work for workshopping general query questions. 
• The D-Reporting development group would continue meeting as a separate report development group. 

New Metadb Section added to Folio Analytics Wiki

A review of Stefan's newest addition to our documentation on FOLIO Analytics: under the General section, he has added a cookbook on how to query data from Metadb using SQL. 

PC Update

The Tri-Council meet on the 18th (2024-01-18 Tri-Council Meeting) to discuss 3 items: how many releases per year, what we want to get out of WOLFCon, how to make FOLIO attractive to new member organizations?

In general, most agreed that 2 releases per was the minimum. Many recognized that releases can be disruptive. Also, a lot of time is spent on testing. There was a question on how the App formalization process will affect these large flower monoreleases.

If you'd like to volunteer for the WOLFCon conference planning group, please contact Jennifer on slack. Chicago was a success. Many people value meeting in person and allowing time to build networks. There were many ideas shared from a day that focused on sharing skills for FOLIO to workshops to an unconference style day.

We didn't have time to begin this conversation.

If you have any thoughts, please share those on slack.