2022-03-14 Reporting SIG Meeting notes









xArthur AguileraUniversity of Colorado, BoulderxLinda MillerCornell University
xSharon BeltaineCornell University
Nassib NassarIndex Data

Erin BlockUniversity of Colorado, BoulderxElena O'MalleyEmerson

Nancy BolducCornell UniversityxTod OlsonUniversity of Chicago

Lloyd ChittendenMarmotxJean PajerekCornell University
xAxel DoerrerUniversity Mainz
Michael PatrickThe University of Alabama

Shelley DoljackStanford UniversityxEric PenningtonTexas A&M


Stefan DombekLeipzig UniversityxScott PerryUniversity of Chicago
xJennifer EustisU. Massachusetts Amherst / Five College
Natalya PikulikCornell University

Alissa HafeleStanford University
Vandana ShahCornell University
xIngolf KusshbzxAmelia SuttonU. Massachusetts

Kim LaineCornell University
Simona TabacaruTexas A&M

Joanne LearyCornell University
Kevin WalkerThe University of Alabama
xEliana LimaFenway Library OrganizationxAngela ZossDuke University
xEric LuhrsLehigh University


Discussion Items




Attendance & NotesAngela

Attendance & Notes

  • Today's attendance-taker: Linda Miller
  • Today's note-takers:  Team Leads for project updates

Announcements /


FOLIO Analytics repository pre-release!

  • https://github.com/folio-org/folio-analytics/releases/tag/v1.3.0-beta5
  • Commits over the last year: https://github.com/folio-org/folio-analytics/graphs/commit-activity
  • What went well?
    • worked well; a lot of people tried to review, and it was nice to see new people stepping up. (probably still need more people to review!)
    • important to say that everyone can create queries; you don't need to be a SIG member. maybe we can publicize this more - let others know they can contribute?
    • documentation was helpful - how to port, how to review
      • Question: should derived table conversion steps be added to CONTRIB.MD?
      • Or PORTING.MD?
    • good to have deadlines
    • ++
    • in addition to the documentation, the checklist has also lowered the barrier on being a reviewer, made people less fearful
    • response time for getting answers to questions, fast responses have been helping
  • What should we do moving forward
    • FOLIO LDP query apps - were a bit late getting testing set up, may need to do that a bit earlier next time
      • there is new functionality, but there haven't been any new tests created 
      • need to use snapshot for bugfest instead of bugfest environment
      • has anyone been asked to write new tests? not that we know of
      • maybe testers should reach out to Charlotte?
      • for next time, starting a little earlier
      • Jennifer could write a new test for save
      • who should be initiating?
      • normally, the week before claiming test (and the week of), POs or others will write tests
      • for the next release, Jennifer can post in Slack channel, ask Nassib if we need tests
      • not too late, we can still write a test and test it
      • Jean, Sharon, and Jennifer are all available to help
      • bugfest is 2 weeks long, so there is still time
      • maybe we can check in with Charlotte and/or Nassib about correct procedure for learning about and writing tests for new features
    • LDLite - our derived queries for LDP and Metadb won't work for LDLite, do we need to do something for LDLite?
  • Question: what is the next step?
    • Are we porting report queries?
    • Do we start writing queries for metadb?

Recruiting New Query Developers

  • The Reporting SIG is always on the look-out for new query developers. Please let us know if you are interested in doing query development or if there are others at your institution who might be a good fit.

Updates and Query Demonstrations from Various Reporting Related Groups and EffortsCommunity & 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.

RA/UM Working Group

MM Working Group

  • Meetings are 1st Tuesday of the month, 12-1pm ET via zoom using the usual FOLIO password. Our lab sessions are open to everyone. Please bring your questions, examples, and comments about reporting and metadata.
  • We have submitted our slate of derived tables for Metadb for Lotus R1 2022. We completed 16 derived tables for metadb!
  • We are turning our attention to finish porting over derived tables to metadb. We have a sign up sheet. We are looking for reviewers.
  • In next our lab session, we will use the LDP instance identifiers and go through the process of porting this over to metadb, how to contribute a pull request with the changes and update the runlist.txt, and go through a review.

ERM Working Group

  • Fixed data types for foreign keys: #554, #551, #550
  • Will now refocus on documentation and new derived table developement
  • ERM Prototype and Query Development Status
  • Meetings are bi-weekly on tuesdays 11am ET alternating with RM Working Group
    • Next meeting will be at 15th, March
    • Contact Axel Dörrer if you would like to get a calendar invitation.
  • Mermaid diagrams can now display directly in GitHub markdown! Example

RM Working Group

Reporting SIG Documentation Subgroup

  • Honeysuckle documentation is live on https://docs.folio.org/docs/
  • Iris documentation is in progress, due December 15
  • 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)

External Statistics Working Group

  • no updates currently
  • new organizational/tracking scheme for JIRA, with pointers to queries in folio-analytics repository
  • New organizational structure for External Statistics reports
    • external statistics reports (e.g., ACRL) typically require running queries from different functional reporting areas
    • these reports will be captured in JIRA under one UXPROD-XXXX report cluster issue, then the descriptions will point to each of the queries required to run them on the folio-analytics repository
    • institutions will need to rank each of these 8 new UXPROD-XXXX report cluster issues
    • each reporting development team will take responsibility for the queries in their area for the external statistics clusters

Product Council

For all recent work on FOLIO Reporting SQL development:

Demonstration of GitHub DesktopAngela
Topics for Future MeetingsAll
  • Next: Reviewing a pull request 
  • How to deal with External Stats reports?
    • maybe subteam leads check in about that
    • probably wait until after Metadb conversion is more complete
  • Definitely do GitHub Desktop demonstration at a SIG meeting in future, probably about 15 minutes

Review and update Topics for Future Reporting SIG Meetings 

  • A test Action Item (Ingolf)