2020-09-28 Reporting SIG Meeting notes

Date

28 Sep 2020

Attendees

Name	Organization	Name	Organization
Sharon Beltaine	Cornell University	Sara Colglazier	Mount Holyoke College/Five Colleges
Elizabeth Berney	Duke University	Erin Nettifee	Duke University
Joyce Chapman	Duke University	Karen Newbery	Duke University
Jean Pajerek	Cornell University	Tod Olson	University of Chicago
Claudius Herkt-Januschek	SUB Hamburg	Scott Perry	University of Chicago
Doreen Herold	Lehigh University	Stefan Stadtherr	MPIL Heidelberg
Sarah Park	Duke University	Simona Tabacaru	Texas A&M
Clint Bellanger	Auburn University	Kevin Walker	The University of Alabama
Ingolf Kuss	hbz	Christie Thomas	University of Chicago
Joshua Lambert	Missouri State	Andi Bihler	Munich Technical University Library
Joanne Leary	Cornell University	Cheryl Malmborg	University of Chicago
Michael Patrick	The University of Alabama	Vandana Shah	Cornell University
Nassib Nassar	Index Data	Angela Zoss	Duke University
Veit Köppen	University Magdeburg	Lisa DeCarolis	Smith College/Five Colleges
Linda Miller	Cornell University	Elena O'Malley	Emerson
Matt Harrington	Duke University	Holly Mistlebauer	Cornell University
Cathy Tuohy	Emmanuel College (FLO)	Nancy Bolduc	Cornell University
Shirley Moentnish	Missouri State	Eric Pennington	Texas A&M
Stefan Dombek	Leipzig University	Axel Doerrer	University Mainz
Natalya Pikulik	Cornell University	Owen Stephens	K-Int
Eliana Lima	Fenway Library Organization	Marcia Borensztajn	EBSCO
Harry Kaplanian	EBSCO	Molly Driscoll	EBSCO
Amelia Sutton	U. Massachusetts	Heather Loehr	Hanover College
Mary Morgan	Grand Valley State University	Jennifer Eustice	U. Massachusetts Amherst / Five College

Discussion Items

Item	Who	Notes
Attendance & Notes	Sharon	Attendance & Notes Today's attendance-taker: Linda Miller Today's note-takers: Team Leads for project updates
Review Results of Reporting Clusters JIRA Issue Ranking Conversion	Sharon	Please note that JIRA rankings for UXPROD and REP issues were converted by Holly to the new ranking system R1 (urgent) to R5 (not needed). As of 2020, the Reporting SIG is only ranking reporting cluster issues, such as "UXPROD-2029 RA-Requests Cluster." You can find report clusters by using the label "report-cluster" in your JIRA search. Individual report requirements are captured in JIRA issues that start with "REP," such as "REP-275 Curbside Pickup Report."
Updates from Various Reporting Related Groups and Efforts	Community & Coordination, Reporting Subgroup Leads	Project updates The Reporting SIG is using small working groups to address priorities and complete our work. Each week, we will provide updates to the Reporting SIG from these various reporting-related groups and efforts. Please include updates on specific JIRA issues for prototype or query development workflow. Additional JIRA tickets for Angela to create for prototypes or queries ? Community & Coordination: reporting survey is out! As of 9/24/20, there were 14 out of 16 respondents to the reporting survey - Yay! Aliasing for reports FOLIO Reporting development Derived table spreadsheet: https://docs.google.com/spreadsheets/d/1GL5XssOJaBMuKOrM0H_0lhht0G4ApDNr72SVLGV0JT0/edit?usp=sharing This week: query development groups take another look at what additional tables may be needed to support ad hoc querying Draft starter list of proposed column names important to keep using the "JSON_EXTRACT_PATH_TEXT" latest model queries for using JSON arrays https://github.com/folio-org/folio-analytics/tree/master/sql/derived_tables JSON array examples: https://github.com/library-data-platform/ldp/blob/master/doc/User_Guide.md#7-json-arrays RA/UM Working Group RA/UM derived table demo rows 25, 28, 29 shown so far MM Working Group MM derived table demo row 2 shown so far; updated to remove former WITH statement ERM Working Group identifying derived tables in agreements and knowledge base Khalilah Gambrel will attend the next ERM meeting to find out how eHoldungs data can be loaded in LDP verifying the latest reports ranking to match with the current development roadmap for latest updates, see ERM Prototype and Query Development Status RM Working Group for latest updates, see RM Prototype and Query Development Status RM Derived Table demos rows 11, 21 shown so far External Statistics Working Group Recategorize External Statistics REP Issues
Writing Aliases in Derived Tables	Angela Zoss	Guidelines for Writing Aliases How do we keep aliasing consistent across derived tables? Argument is that appropriate aliasing makes sure the reports make sense to end users and that consistent aliasing across queries ensures consistent readability Don't want to add a lot of overhead, but do want groups to be thoughtful about how derived tables will get pulled into other queries General rules always alias the ID field by adding (simple) table name if joining in a name from a secondary table (and keeping the id field), both id and name should have similar alias if a field name occurs in multiple tables (e.g., permanent_location_id, statistical_code_id), always add the table name ideas for a "registry" we could keep track of "approved" aliases in some kind of spreadsheet, like this example groups could use it to verify aliases in a new query, store new aliases as created could be a bit too much work, but might be nice to have a good starting set of example aliases
Topics for Future Meetings	All	Review and update Topics for Future Reporting SIG Meetings

2020-09-28 Reporting SIG Meeting notes

Date

Attendees

Discussion Items

Action items