2024-04-22 Reporting SIG Meeting notes

Stanford University

Announcements/Reminders

Changes in Reporting SIG Meetings

• "Workshopping your queries" - part of each Reporting SIG meeting will be devoted to time to work through any query questions you may have

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 

Summary of Metadb Development Meetings (Corrie and others)

• Issue 826 & 827 (in GitHub) were discussed and volunteers solicited.
• Nassib encouraged using functions.  Necessary for reports that will be run using the 'Run reports' functionality in the Reporting app.
  • Questions : why use functions instead of a saved query?  Do they impact performance? 
• Nassib raised the issue of future plans for derived tables, but no roadmap was given or discussed.
  • Questions: what are the plans for derived tables in Metadb?  Advice on how to port needs from LDP to Metadb (when derived tables were employed in LDP reports)?
• Action steps : 
  • Corrie to take questions to Nassib 
  • Possibly having Nassib come to train on using functions?

Upcoming meeting topics (tentative)

• Bibcontrol presentation by Klaus Hoverrath (May 13)

Any new members?

• Welcome/introductions

• 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

ID providing multiple people to make the support more scalable–will be ;

Corrie providing role of the product owner;

Nassib is moving off to another role;

Likely to move out to a Jira environment rather than Github 

More announcements over the coming weeks

Formally applying to OLF for inclusion in FOLIO

More timelines and goals.

Nassib will be less visible, but still involved

Running through Corrie or others but likely less direct access to Nassib

Here is a summary of information about WOLFCon 2024 from Jesse Koennecke:

• Location and Dates: Senate House, University of London, September 24-26, 2024
• Call for Proposals Now Open: Got ideas about open-source to share? Talk about it at WOLFcon. Submit a presentation, panel, short talk, or pre-conference workshop. The deadline for submissions has been extended to April 30, 2024. Submit a session here.
• Early Bird Registration Now Open: Join us at Senate House, University of London. September 24-26, 2024. Register now through July 31, 2024 for an early bird discounted rate.
• Learn more about WOLFcon 2024: Want to learn more about the Open Library Foundation and WOLFcon? Be sure to visit our website where you can learn more about the foundation, members projects, communities, and the annual conference.

Reporting SIG Planning for WOLFCon 2024:

• Several sessions proposed for the WOLFCon 2024 conference! 
• See ideas we have submitted so far at  WolfCon 2024 Planning

Cornell is in the process of moving from an LDP to a Metadb reporting database system for FOLIO reporting. Natalya and Sharon will offer a presentation called "Moving from LDP to Metadb" to share key topics from what they've learned so far in helping Cornell Library staff make this transition:​

• What is Metadb?​
  • LDP versus Metadb: Overview​
  • LDP versus Metadb: Data Refresh​
  • Metadb Rollout Plans for the Cornell Library​
  • LDP and Metadb Schema Structures​​
• More about LDP and Metadb Schema Structures​
  • Writing and Revising SQL queries for Metadb​
  • Examples

This presentation is packed with information, so we may need to divide it into 2 parts. We'll see how it goes! 

Workshopping Queries

Bring your questions on queries written for the LDP or Metadb so we can "workshop" them!

Q: How can a user on the fly add ordinality to a derived table where it is not present? Example is the folio_derived.holdings_ext table which does not include ordinality. No solution was presented in the session. It was suggested that ordinality could be added to the derived holdings_ext and item_ext tables. 

• Build a directory of extracted and derived tables
  • Beta version available.
• Build Metadb query cookbook-style documentation
  • ongoing project
  • The first cookbooks are available and are being expanded. See https://github.com/folio-org/folio-analytics/wiki#cookbooks
• Build Training Program for FOLIO Data Model
  • ACQ/ERM drafts have been presented and will be updated
• Port LDP derived tables to Metadb
  • possibly done??
• Recruit from new institutions not represented
  • recommend that the development teams reach out to SIGs for an update, invite new members

• LDP release notes
• Metadb release notes (via tags)
• LDLite release notes (via tags)
• ldpmarc release notes
• LDP Reporting App release notes (mod-ldp, ui-ldp) and JIRA issues (mod-ldp, ui-ldp)
• FOLIO Analytics release notes 

Metadb FOLIO User Group

• Meetings
  • Contact Nassib Nassar if you would like to get a calendar invitation

Product Council

• (December 8 meeting) PC shared a report of the SIG check-ins
• would love for PC to check-in yearly

Reporting SIG Documentation Subgroup

• Orchid documentation is live on https://docs.folio.org/docs/
• Poppy documentation is in development
• Additional Context
  • The Reporting SIG has representation on the Documentation Working Group, which is building end-user documentation for https://docs.folio.org/docs/ (mostly linking to existing documentation over on GitHub)

For all recent work on FOLIO Reporting SQL development:

• https://github.com/folio-org/folio-analytics/commits/main