Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.





Attendance & NotesAngela

Attendance & Notes

  • Today's attendance-taker: Linda (or substitute)
  • Today's note-takers:  Team Leads for project updates
Product Council SIG check-inJesse & Owen
  1. Can you share the purpose of your SIG: functional area/cross cutting/affinity group, etc?
  2. What areas does your SIG have responsibility for?
  3. What do you feel like your SIGs purpose is currently? Has it changed over time?
  4. Do you have product owners who regularly work with the SIG? Do you feel that your requirements are being successfully developed into FOLIO?
  5. How do you feel about the resources allocated in the development areas that are focused on?
  6. What are some of the challenges facing your SIG/subgroup? Are there ways in which you feel the SIG has been unable to accomplish its mission?
  7. If you work on areas of development, do you feel like there are areas of development not resourced at all or significantly under-resourced?
  8. What has been successful with the SIG? What things contributed to that success?
  9. What could the Product Council do to help the SIG?
  10. Do you feel like the Roadmap accurately represents the work of your SIG (both desired and already accounted for)?
  11. How can we improve our communications with the SIG? Does the current monthly reporting work? Would have a dedicated PC meeting for your SIG be helpful?
  12. Is the SIG comfortable communicating with the PC and have a sense of when a PC conversation would be helpful?
  13. What functions should the PC be accomplishing and how would the SIGs like to have those need met?

Announcements /


Any new members?

  • Welcome/introductions
  • Would anyone like a buddy? Like to be a buddy?

How to find our latest recordings

(Always) 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.

Review of In-Progress Projects
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. MM notes
  • We reviewed the consistency of our LDP and metaDB derived tables which is looking good.

ERM Working Group

  • FOLIO Data Model Training (in progress)
  • ERM Query Development Status
  • Open Access
    • Report requests are being collected in the OA SIG Link (in progress)
    • The test environment from the SIG Reporting will get the app OA (in progress)
    • Test data will imported
  • Meetings are bi-weekly on tuesdays 11am ET alternating with RM Working Group
    • Next meeting will be at 6th, Dec
    • Contact Stefan Dombek if you would like to get a calendar invitation

RM Working Group

Reporting SIG Documentation Subgroup

  • Morning Glory documentation is live on
  • Nolana documentation is in review
  • Orchid documentation will be in progress soon, and plans are underway to include beta-level documentation for Metadb
  • Additional Context
    • The Reporting SIG has representation on the Documentation Working Group, which is building end-user documentation for (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:

Topics for Future MeetingsAll
  • How to deal with External Stats reports?
    • maybe subteam leads check in about that
    • probably wait until after Metadb conversion is more complete
  • Exploring new recruitment/onboarding strategies (e.g., buddy system)
  • More work on asynchronous collaboration, how to engage in discussions and question answering more broadly
    • consider connecting with a Slack channel, to make sure any forum topics get highlighted on Slack as well?
  • Open question: should we update FOLIO LDP-based Reporting First Implementers Grid
  • Cleaning up our wiki pages

Review and update Topics for Future Reporting SIG Meetings