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 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 reviewed the consistency of our LDP and metaDB derived tables which is looking good.
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
Product Council
For all recent work on FOLIO Reporting SQL development:
If you're okay using APIs might want to try LDLite
Why don't all institutions get LDP?
EBSCO has internal analytics platform called Panorama, but it's not quite everything people need
Cornell has been through a learning curve with EBSCO on LDP, and things are getting better (more frequent updates, better performance)
have to negotiate it with them, but if they are willing to host, they should be able to now
it's really important that they stay on the recommended platform when they implement (LDP1 → AWS/Postgres)
Index Data develops the software and has offered support for other hosting providers, but that's easier if it's being hosted on the recommended platforms
Upcoming training
Cornell going to share some of their local training
Duke may be able to share some local recordings as well