Today's note-takers: Team Leads for project updates
Announcements / Reminders
Angela
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.
Test Data
FOLIO Reporting developers and Reporting SIG members are encouraged to use this new page to share test data cases they have entered into FOLIO reference environments to keep us all aware of what data to expect when we test our queries.
New Report Clusters are added on a regular basis, so it is important to make sure your institution is reviewing these clusters and ranking them to establish report development priorities. If you rank reports for your institution, please follow the instructions below. If someone else ranks, please pass this information along to that person so your institution's vote can be included.
Action =>> Please review Reporting SIG-All Report Clusters (57 issues) in JIRA and RANK each report cluster for your institution (R1-R5)
For reporting, institutions only need to rank the UXPROD Report Cluster JIRA issues. All reporting requirements, which are captured in REP-XXX issues, roll up to the UXPROD Report Clusters. Report clusters cover one or more report (REP-XXX issue) requirements.
Need to compile a list of volunteers to help with Bug Fest for LDP app (don't need to have a Test Rail account)
Presentation of KNIME, Postman
Angela
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
On hiatus for a few weeks
Will meet with RA SIG and try to identify an RA member willing to connect regularly with Reporting SIG
Will hold off on additional queries to finish up query updates and documentation
Friday the RM SIG proposed a new organization; ERM would be raised to level of SIG, and RM would join Acquisitions group to form an Acquisitions SIG, also elevate Open Access group to a SIG
Reporting SIG Documentation Subgroup
No changes
Additional Context
Over the next few months, Reporting SIG Documentation Subgroup will be helping to build end-user documentation for https://docs.folio.org/docs/ (much will be linking to existing documentation over on GitHub)
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
For all recent work on FOLIO Reporting SQL development: