Content Comparison

Attendance

Attendance & Notes

• Today's attendance-taker: Linda (or substitute)

• See attendance list at bottom of page
  

Announcements and Reminders

Scott

Announcements:

• About the Reporting SIG meeting schedule

  • Meetings are held on the first 4 Mondays of each month at 11:00 am Eastern U.S. time (see this time in your time zone). The first and third Mondays focus on Reporting Development topics, and the second and fourth Mondays focus on Reporting Business topics. 

  • "business" means topics like presentations on reporting functionality and new features, new reporting applications, surveys and studies on reporting, etc.

  • "development" means working on derived tables and report queries for the folio-analytics GitHub repository

  • "workshopping" queries could be scheduled during any of these meetings, and it would be great to have topics and/or questions in advance so we can prepare to walk through the answers/approaches, such as "how to I fix this inventory query to get rid of the duplicates?" or "what is the best way to calculate totals in this finance query?" 

• Important Upcoming Changes to LDP software support:

  • end of support is end of May 2025

  • see Mike Gorrell at Index Data for questions

  • institutions running LDP on a reporting database are encouraged to move to running Metadb software
    

Ongoing Topics:

• 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 

• Upcoming Reporting SIG meeting topics (tentative)
  

  • D-Reporting group updates

  • Linked Data group updates

  • Annual Statistics demo and discussion

  • Lists App updates

• Any new members?

  • Welcome/introductions

• How to find our latest recordings

  • Recording details available on our Reporting SIG Meetings and Notes page and Reporting SIG Subteam Meetings page

SIG Recruitment:

We will need to be recruiting for a variety of roles in the coming months. Please consider whether you would be interested. Please reach out to Scott Perry or Sharon Markus with any questions.

• Representative for the Documentation Working Group 

  • urgently needed

  • work with reporting documentation team to  update Reporting section of FOLIO documentation for each FOLIO software release 

  • see https://docs.folio.org/docs/reporting/

• Query developers

  • ongoing need

  • work on derived tables and report queries for the FOLIO Analytics repository and to support Metadb

  • see https://github.com/folio-org/folio-analytics

Product Council Liaison Updates

• WOLFcon 2025 will take place Sept. 23 -25, 2025 in Kansas City, MO. Monday Sept. 22, 2025 will be the preconference day like last year. The Call for Submissions will be sent out in the next week or two. Please think of submitting a session or 2 for reporting.

• Eureka on track for Sunflower Release

  • Permissions changing to role-based (see FOLIO User SIG and PC notes for more info)

  • still working on prioritization

• Need to look at Jira issues for Reporting App managed by Index Data

• Need Metadb environment to test against current and future releases (BugFest)

• Important to fit products into Roadmap

LDLite Continued Support

• Katherine Bargar will maintain LDLite, Patrick Waite will be PO

• Katherine made a pull request to make LDLite compatible with RTR (Request Token Rotation)

• work planned to be able to run it under Eureka

Latest Updates on Metadb version 1.4 software development and the LDP Project from Index Data

Mike Gorrell

LDP: Last week LDP was accepted as a full fledged project under OLF More about this in the coming weeks.

Metadb 1.4:

• We have automated the creation of the Mapping commands. This means this group will not have to do the initial mapping of JSON objects to be extracted.

• This month we’ll be testing the impact on performance (normal operation and resync)

• Will need to determine which mappings are done automatically going forward. There are some derived tables that are not used. We don’t want to waste cycles.

• Let’s look at this spreadsheet showing usage from Colorado, Chicago, Stanford and Cornell

Automatic Mappings

• institutions should be ready to talk about which derived tables are priorities for them

• pg_stats gathers statistics on the number of times tables are used, but disappears each day, so needs to be captured by another job

• Metadb Log captures information on table creation duration (See https://metadb.dev/doc/ )