Page Comparison

Announcements/Reminders

Ongoing Topics

Announcements:

• Wolfcon 2024 coming up in September
  • Here is a summary of information about WOLFCon 2024 from Jesse Koennecke:
    • Location and Dates: Senate House, University of London, September 24-26, 2024
    • 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.

• Metadb User Group meetings
  • The Metadb Users Group meetings have ended and the topics will now merged into Reporting SIG meetings

Ongoing Topics:

• Workshopping your queries
  • part of each Reporting SIG meeting will be devoted to time to work through any query questions you may have
  • please reach out to Christie Thomas if you have a question you would like to "workshop" during an upcoming Reporting SIG meeting

• 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 Reporting SIG meeting topics (tentative)

• Reporting SIG and Reporting Development meeting structure
  • focus on derived table development, support, maintenance
  • LDP to Metadb Training Part 2 (June 24)
  • Writing reports for the Reporting App (July 8)

• 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

Workshopping Queries 

*This is a standing Reporting SIG meeting topic. We don't expect to have time for this topic during the 5/13/24 meeting, so we'll pick it up again at future meetings

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. New Proposal for Reporting SIG Meeting Topics, Schedule, and Structure

We have a new proposal for the structure, topics, and schedule for Reporting SIG meetings starting July 2024. We would like to discuss this with you and see what you think! Here is the general idea:

• Reporting SIG meetings return a weekly schedule, still held at 11am ET on Mondays
• meeting topics alternate between "business" and "development" each week
• "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?" 

-meetings devoted to workshopping are good

-sounds like a plan

-will add to slack messages to ask about this

-add labels to alternatings meeting, e.g. "Reporting SIG - Business," "Reporting SIG - Development" 

Metadb Software Development, Upgrades, and Testing

Our Product Owner Corrie Hutchinson would like to cover some important topics with regard to Metadb software development, testing, and upgrades.

• Testing Metadb upgrades
• Bugfest testing workflows and processes

-ID still working on leadership transition

-metadb release cycle and testing procedures in discussion

-metadb testing needs to be done outside BugFest

-how would testing be different from testing done by individual institutions? 

-need to test metadb alone and as part of a flower release

-how do we make sure we don't break something with each new release? how can this be done in a more automated/discoverable way?

-how do we give feedback to the FOLIO community that things need to be changed upstream?

-FOLIO Snapshot is beyond what most FOLIO dbs are... it may not be the best testing environment

-Should we continue to try to point metadb to a BugFest environment?

-Reporting App needs to be tested as well

-Is bugfest stable for long enough that the initial metadb load has time to complete?

-I feel like metadb is more reactionary than other folio dev. so, when considering flower releases, maybe it would make sense to test metadb against bugfest immediately AFTER flower release. then the new folio data fields can be tested, but most institutions won't jump to new flower release right away

-might be better for Devops SIG to test Metadb and Reporting SIG to focus on derived table testing

-should we plan to align metadb releases with Flower releases or rolling releases

-should we plan sprint reviews in the Reporting SIG?

Stefan Dombek will lead a discussion on workflows for the folio-analytics github repository

• see https://github.com/folio-org/folio-analytics
• urgent need for faster reviews and merges for Pull Requests submitted to this repository

-new workflow is needed to go along with new structure for developing and reviewing PRs

-folio-analytics is behind 

-would be helpful to have sprints, deadlines, etc.

-rolling releases challenging in that there is less pressure to get the next query developed

Derived Table Pull Request Prioritization 

To support the review and merge process for current pull requests submitted to the folio-analytics GitHub repository, we'll take a look at the current list of Pull Requests and add the new "High Priority" label to them.

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