Today's note-takers: Team Leads for project updates
Announcements / Reminders
Angela
Possible raining topic: Git/Github?
should we cover that in a SIG meeting? how many interested?
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.
Prove the design of using external data sources(outside FOLIO data) in the Library Reporting Database
User acceptance testing: are we meeting the requirements that we hoped we would?
Develop support for using MARC data in FOLIO reporting
Develop a FOLIO Reporting Vision and Strategy
Develop support structure for those using queries
Understand our needs for normalizing, denormalizing, summarizing, aggregating, anonymizing data
Expand outreach by sharing experiences of report development groups more broadly and getting feedback from other groups in the FOLIO community
Maintain, support, and distribute robust repository of shared queries
Write shared documentation on the queries, connecting reporting tools to Library Reporting Database
Write shared documentation on the Library Reporting Database implementation, maintenance and schema (e.g., data dictionary)
Reach out to FOLIO implementers and respond to their reporting problems and needs
Extend collaborative model of report development groups to a larger scale, focusing on those who will actually be using the queries
What else did we accomplish?
Priorities for 2022:
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
Angela has been attending RA SIG meetings to open the lines of communication, now once a month
Contact Angela if you would like to join these meetings; first Wednesdays at 10am 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.
Our goals this year:
Work on converting our LDP derived tables and queries to metadb
Work on learning GitHub, git, and more sql
ERM Working Group
Discussed ERM Goals 2022
Complete documentation on existing derived tables
Migrate ERM LDP queries for Metadb use
How to get more ERM SIG more involved for...
(real life) reporting requirements
checking results of report on real data
How can development for the integration of eHoldings data be funded
Housekeeing: Github issues left overs, how long to keep meeting recordings etc.
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
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: