2020-09-21 Reporting SIG Meeting notes

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
XSarah 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
XStefan DombekLeipzig UniversityXAxel DoerrerUniversity Mainz

Natalya PikulikCornell UniversityXOwen StephensK-Int
XEliana LimaFenway Library Organization
Marcia BorensztajnEBSCO

Harry KaplanianEBSCOXMolly 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
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!
  • discussing next steps for Reporting SIG after Derived Tables are Created:
    1. Systematic group review of derived tables in future Reporting SIG meeting
    2. Modify queries to use the derived tables
  • At their own institutions or hosting provider, LDP admins can automate derived table updates through a simple script


FOLIO Reporting development

  • The database folio_snapshot is now being updated once per hour (at 0 minutes after the hour) from the folio-snapshot reference environment. This allows making changes via the FOLIO UI at https://folio-snapshot.dev.folio.org/ and working with the updated data in the LDP database within an hour.

    The database folio_snapshot is now also being updated once per hour (at 30 minutes after the hour) with the derived tables from https://github.com/folio-org/folio-analytics/tree/master/sql/derived_tables which create tables in the local schema.

    If we could prefix our local tables with our names, in the form local.firstlast_... (for example, local.nassibnassar_items_ext), that would help with keeping the local schema workspace organized.

    Thanks for your help!


Reporting Data Privacy Working Group:

  • update on request to Product Council to have FOLIO create centralized documentation for fields containing personal data 
    • FOLIO Product Owners will maintain central list of data privacy fields
    • NN will follow up on this; he will create a Google Doc with the tables and fields based on the list from the Data Privacy workgroup
    • Cate Borema will work with Product Owners to keep this document up to date; Nassib will follow up with Cate


Derived Tables Discussion

  • How do we keep aliasing consistent across derived tables?
  • Discussion to continue in next Reporting SIG meeting


RA/UM Working Group

  • RA/UM derived table demo
  • rows 25, 28, 29
  • useful to bring in the id field of the table, then a useful name field right after in the query, such as patron_group_id and patron_group_name

MM Working Group

  • Jennifer Eustis is new liaison to MM Reports Subgroup!
  • MM derived table demo
  • row 2 
  • useful to bring in id and hrid when available
  • long aliases are helpful to describe the data more clearly

ERM Working Group

RM Working Group

External Statistics Working Group


ID tables

Question about ID tables

  • in folio_snapshot, organization id, vendor id, and contact id are all the same id data; id numbers are same, but elements associated with id numbers is different
  • would it be better rename id to organization_id in organization_contacts?
  • foreign key analysis only works with real data and does not work with test data
  • what about renaming the columns for clarity? 
    • better to retain the tables in their original form
  • one way to work with the id table issue is to alias the tables
Reporting Survey ReminderAll

Remember to have your institution's Reporting Representative complete the Reporting Survey


Fine/Fees questionHolly

For the question about reporting on options for lost item replacement actual cost, Option B for developing a separate Fine/Fee type was chosen over using the Transaction Information field.

Option B:

  • Reporters would find SET COST charges by looking for a Fee/Fine Type of ‘Lost item fee’.
  • Reporters would find ACTUAL COST charges by looking for a Fee/Fine Type of ‘Lost item fee’ (actual cost)’.


Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


Action items