Versions Compared

Old Version 9

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version 10

changes.mady.by.user Sharon Markus

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 demoupdating all derived tables using the "arrow" approach
  • 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

  • RM Derived Table demos
    • rows 11, 21 shown so far

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
    • 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 MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


...