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.
Update on documentation of derived tables
Stefan, Axel
Axel and Stefan have met to talk about automating documentation of derived tables
Stefan created a script to extract comments and tables from the derived table scripts
Would like to automate diagrams for these tables, but it could be tricky. Have to parse the SQL to extract the tables and the joining fields.
In Monday SIG, we decided diagrams would really be helpful if possible
RA/UM: willing to try to build out some more diagrams for how Inventory tables connect, especially Instance/Holdings/Items (have actually already covered materials hierarchy and locations). Didn't really start this work yet, though.
Included this request in our recent update to PC, and MM Convener actually made an announcement for us. Expect to do a series of visits to SIG in the new year to try to make a stronger case.
Also did get some confirmation that reaching out to Community Council would be a good idea; they are talking about FOLIO-wide onboarding, and we might be able to suggest that reporting be added as a good place to have a representative
Updates and Query Demonstrations from Various Reporting Related Groups and Efforts
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.
RA/UM Working Group
Meetings have become more of a lab session, working through specific problems
Contact Angela if you would like to join these meetings; second Tuesdays at 1pm Eastern
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 will be fixing the LDP derived table instance_ext.sql which has a duplicate field (record_source and instance_source). The column record_source will be removed and comments will be added to the derived table.
If you are able to test ldpmarc 1.6 new release, please do so.
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 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
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