Today's note-takers: Team Leads for project updates
Announcements / Reminders
Angela
Reporting SIG Holiday Schedule
Plan to cancel December 27 and January 3
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.
New Opportunity for SIG volunteer
Documentation subgroup coordinates changes to the reporting documentation posted at docs.folio.org; represents the Reporting SIG at the monthly Documentation Working Group meetings
Gathering examples of communication breakdowns
All
Follow up on 11/29 discussion about lack of communication between developers and SMEs, lack of transparency in other areas of FOLIO
Had a good discussion in MM about documentation, change control; the most outspoken group is Data Export(?) group. It's complex; the changes show up in code commits. Recent change to SRS comes because SRS can have bib, holding, or item, so can't just label it all instance. Might have some implications, though, so have some questions that are going back to developers. Have a plan to bring this up with technical council. Maybe this should be a TC discussion at WOLFcon - how to track changes, how to write release notes. Ann Marie made a high level view of Data Import, but maybe not specific enough. Don't want to just know about changes, but how changes affect what we're doing. Need to advocate, keep bringing it up
Had a quick conversation about it on TC channel on Slack, too
TC could try to establish some norms, but to make any real change, Khalilah will probably be the point person
MM, there will be more changes; starting to work on authority, and there is also bound-with part 2; not sure about 880 - now getting mapped to alternate titles or something; 245 can't be repeated, but in graphic representations they might be repeated; might need to be changes based on how discovery systems interact
project management methodology has a solution for this called change control, has been around for decades; parties are identified and they give feedback
App Interactions is also dependent on knowing about changes to data model
would be good to have people in governance really thinking about this
another example of an issue - in inventory a field is an integer, but in SRS it's not, and that can throw people for a loop; looking at it more closely could put a spotlight on these inconsistencies
what about Support SIG? would they also be impacted? if new functionality is popping up, that would impact them as well
subteams/individuals, please consider documenting examples of data model changes that went well or poorly
Intro to SQL
Angela
Angela will lead some introductory SQL sessions for anyone wishing to participate
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
The zoom link for the meeting is https://umass-amherst.zoom.us/j/99254861410. Usual FOLIO password. Our lab sessions are open to everyone. Please bring your questions, examples, and comments about reporting and metadata.
Meetings are 1st Tuesday of the month 12-1pm ET
ERM Working Group
On going work on ERM data with LDlite
Group started on first derived table as prototype to document this areas documentation on mermaid.
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: