2020-09-28 Reporting SIG Meeting notes

Owned by Sharon Beltaine
Last updated: Sep 28, 2020 by lm15@cornell.edu
3 min read

Date

Attendees

Present?

Name

Organization

Present?

Name

Organization

XSharon BeltaineCornell University
Sara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University
XJean PajerekCornell UniversityXTod OlsonUniversity of Chicago
XClaudius Herkt-JanuschekSUB HamburgXScott PerryUniversity of Chicago


Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Sarah ParkDuke UniversityXSimona TabacaruTexas A&M

Clint BellangerAuburn UniversityXKevin WalkerThe University of Alabama
XIngolf Kusshbz
Christie ThomasUniversity of Chicago
XJoshua LambertMissouri State

Andi Bihler

Munich Technical University Library

Joanne LearyCornell University
Cheryl MalmborgUniversity of Chicago
XMichael PatrickThe University of AlabamaXVandana ShahCornell University
XNassib NassarIndex DataXAngela Zoss

Duke University


Veit KöppenUniversity Magdeburg
Lisa DeCarolisSmith College/Five Colleges
XLinda MillerCornell UniversityXElena O'Malley

Emerson


Matt HarringtonDuke University     Holly MistlebauerCornell University

Cathy TuohyEmmanuel College (FLO)XNancy BolducCornell University

Shirley MoentnishMissouri StateXEric PenningtonTexas A&M

Stefan DombekLeipzig UniversityXAxel DoerrerUniversity Mainz
XNatalya PikulikCornell University
Owen StephensK-Int
XEliana LimaFenway Library Organization
Marcia BorensztajnEBSCO

Harry KaplanianEBSCO
Molly DriscollEBSCO
XAmelia SuttonU. Massachusetts
Heather LoehrHanover College

Mary MorganGrand Valley State UniversityXJennifer EusticeU. Massachusetts Amherst / Five College


Discussion Items

Item

Who

Notes

Attendance & NotesSharon

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 ConversionSharon

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 EffortsCommunity & 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


RA/UM Working Group

  • RA/UM derived table demo
  • rows 25, 28, 29 shown so far

MM Working Group

  • MM derived table demo
  • changing queries to remove the WITH and to use CROSS JOIN
  • demo of holdings_electronic_access_v2 (in progress)

ERM Working Group

  • identifying derived tables in agreements and knowledge base
  • Khalilah Gambrel will attend the next ERM meeting to find out how eHoldings data can be loaded in LDP
  • verifying the latest reports ranking (rank renaming) to match with the current development roadmap
  • for latest updates, see ERM Prototype and Query Development Status

RM Working Group

  • RM Derived Table demos
    • rows 11, 21 shown so far
    • demo of local.invoice_lines_fund_distributions, needs to be updated for the new way to extract json arrays
    • WITH allows you to create a subquery (intermediate table "funds_distr" is created); locally-scoped table that exists for 

External Statistics Working Group


Writing Aliases in Derived TablesAngela 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
    • because derived tables take data fields out of their original context (original tables), better to be more descriptive where possible
    • always alias the ID field by adding (simple) table name
      (e.g., id → user_id)
    • if joining in a name from a secondary table (and keeping the id field), both id and name should have similar alias
      (e.g., electronic_access_relationship_id, electronic_access_relationship_name) 
    • if a field name occurs in multiple tables, always add the table name
      (e.g., permanent_location_id → item_permanent_location_id, statistical_code_id → instance_statistical_code_id) 
  • 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
  • note: column name length does have restrictions, might want to agree on some abbreviations for both table and field names


Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


Action items