2024-06-10 Reporting SIG Meeting notes

Date

Attendees

Present?

Name

Organization

Present?

Name

Organization

xArthur AguileraUniversity of Colorado, Boulder
Eliana LimaFenway Library Organization
xSharon BeltaineCornell University
Eric LuhrsLehigh University

Erin BlockUniversity of Colorado, Boulder
Lisa McCollLehigh University

Kathleen Moore
xLinda MillerCornell University

Shannon BurkeTexas A&M
Nassib NassarIndex Data

Suzette CanedaStanford UniversityxElena O'MalleyEmerson

Dung-Lan ChenSkidmore College
Tod OlsonUniversity of Chicago

Lloyd ChittendenMarmotxJean PajerekCornell University

Tim DannayMount Holyoke College
Kimberly PamplinTexas A&M University 

Axel DoerrerUniversity MainzxScott PerryUniversity of Chicago


Shelley DoljackStanford UniversityxNatalya PikulikCornell University
xStefan DombekLeipzig University
Emily SanfordMichigan State University
xJennifer EustisU. Massachusetts Amherst / Five CollegexBob ScheierHoly Cross

Lynne ForsWellesley College
Vandana ShahCornell University

Lisa FurubottenTexas A&M
Linnea ShiehStanford University

Alissa HafeleStanford University
Susie SkowronekOakland University
xCorrie HutchinsonIndex DataxKen SmithValdosta State University

Jamie JesanisMCPHSxKimberly SmithMiddle Tennessee State University

Jeanette KalchikStanford University
Clare SpitzerStanford University

Harry KaplanianEBSCO
Amelia SuttonU. Massachusetts

Tim KiserMichigan State University
Simona TabacaruTexas A&M
xKevin KishimotoStanford University
Huey-Ning Tan

Stanford University


Ingolf KussHBZ
Vitus TangStanford University

Alexander LaoStanford University
Christie ThomasUniversity of Chicago
xJoanne LearyCornell University
Irina TrapidoStanford University

Mike GorrellIndex Data
Catherine TuohyEmmanuel College



xPatrick WaiteU. Mass Amherst




Joseph MolloySpokane Public Library

Discussion Items

Item

Who

Notes

Attendance & NotesSharon

Attendance & Notes

  • Today's attendance-taker: Linda (or substitute)
  • Today's note-takers:  Team Leads for project updates


Announcements/Reminders

Sharon

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)


  • Upcoming Reporting SIG meeting topics (tentative)
    • LDP to Metadb Training Part 2 (June 24)
    • Writing reports for the Reporting App (July 8)


  • Any new members?
    • Welcome/introductions



SIG Recruitment:

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

  • Representative for the Documentation Working Group 
  • Query developers


New Proposal for Reporting SIG Meeting Topics, Schedule, and Structure


Scott, Sharon

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


Corrie

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?


Discussion on workflows for the folio-analytics GitHub report repositoryStefan

Stefan Dombek will lead a discussion on workflows for the folio-analytics github 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 

Sharon

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.


FOLIO Product Council UpdateJennifer2024-05-30 Product Council Agenda and Meeting Notes. PC is addressing actionable items from 2023 Report on Things that could be better about FOLIO survey in this spreadsheet. The SIG/PC meeting will be on June 20, 2024, 10-11 am EST.


Recurring Items (Updated weekly, but not always discussed in meeting)

ItemWhoNotes
Review of In-Progress Projects (Recurring)
Review the release notes for FOLIO Analytics, LDP, LDLite, LDP Reporting App, ldpmarc, Metadb Projects (Recurring)
Updates and Query Demonstrations from Various Reporting Related Groups and Efforts Projects (Recurring)Community & Coordination, Reporting Subgroup Leads

Project updates

Reporting development is using small subgroups to address priorities and complete work on report queries.  Each week, these groups will share reports/queries with the Reporting SIG.  Reporting development team leads are encouraged to enter a summary of their work group activities below.

D-A-CH Working Group (D-Reporting)

  • The working group D-Reporting is planning its own repository on GitHub.
    • Special requirements require a separate repository for the German community.
    • Content of this repository
      • SQL files for DBS (FOLIO database + Metadb)
      • Files for the FOLIO App Reporting. Special reports are created here for the German community. These are usually reports that are desired as in-app reports but are not implemented in the apps.
      • SQL files for views for querying in the FOLIO database
      • Scripts for API calls, automation, Jupyter notebooks ...
      • Wiki
  • Ongoing topics
    • Workshopping
    • DBS statistics
      • JIRA-Issues, Rpt-Clusters
      • Gap analysis to statistic codes, user counts etc.
      • Identifying functions that we need for statistics in Germany but are not yet implemented in FOLIO
  • Meetings
    • Contact Stefan Dombek if you would like to get a calendar invitation


Metadb FOLIO User Group

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


Product Council


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: