Page tree
Skip to end of metadata
Go to start of metadata









XSharon BeltaineCornell University
Sara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University

Elizabeth EdwardsUniversity of ChicagoXTod OlsonUniversity of Chicago

Claudius Herkt-JanuschekSUB HamburgXScott PerryUniversity of Chicago


Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg
XAnne L. HighsmithTexas A&MXSimona TabacaruTexas A&M

Harry KaplanianEBSCOXKevin WalkerThe University of Alabama
XIngolf Kusshbz
Charlotte WhittIndex Data

Lina LakhiaSOAS

Michael Winkler

XJoanne LearyCornell University
Uschi KluteGBV
XMichael PatrickThe University of Alabama
Holly MistlebauerCornell University

Nassib NassarIndex DataXAngela Zoss

Duke University

Veit KöppenUniversity MagdeburgXLisa DeCarolisSmith College/Five Colleges
XLinda MillerCornell University
Philip RobinsonCornell University

Filip Jakobsen (guest)Samhaeng
Jackie Gottlieb
XElena OMalley

Discussion Items




Assign Notetaker, Take Attendance, Review agendaSharon

Today's notetaker: Scott Perry

Last week's notetaker:

Update and Demos from the LDP Report Working GroupAngela, Kevin, Tod, Sharon, Eric, Scott, Michael, Claudius, Veit

The LDP Report Working Group will give an update on progress and some demos with reporting tools:

  • Database schema (Angela)
    • Schema Spy
  • Circulation detail report query (Sharon)
  • LDP-Analytics GitHub repository (Angela)
    • non-function creating version 
  • Accessing the test database (Kevin, Michael, Angela, Tod?, Sharon?)
    • Web interface
    • Client-side reporting tools
    • test data


Review of schema by Angela and SchemaSpy. Using star schema because more user friendly.

Versioning based on record_effective date for updates to records. Daily snapshot updated based on updated, new records since the previous day.

Historical data vs. current data discussion.

Schema public will be extended to include all tables needed for reporting. Not created automatically, only created as report model created.

Report Prototypes

Use API documentation. Some documentation is incomplete or missing–important for gap analysis as well.

All elements represented in SchemaSpy.


The latest versions have the star schema. The main page shows both the original legacy report, a link to Jira and the new SQL.

Able to build a library of SQL for anyone to build Folio reports. Ability to work collaboratively on reports.

User key will be link for circulation the version of the user will be retained based on when the loan is made.

Comment SQL code as a best practice to include likely issues with the report.

How will reports be organized? Not yet thought about that yet. Might be a need for user stories. How is a report used? Very detailed list of needs and use of the report.

For tools, go to Report Prototype Working Group–Tools

R and Tableau tools shown. Tableau doesn't like trailing semicolon in SQL. Will review other tools at another meeting.

Report Prototype Working Group meets Mondays at 10 EDT at https://zoom/us/j/614438335

Topics for Future Meetings


Review and update Topics for Future Reporting SIG Meetings 

Other Topics?AllAny other topics to discuss today?

Action items

  • Sharon will meet with Ann-Marie Breaux on Import-Export reports and bring notes back to Reporting SIG
  • Sharon to review ARES-related Resource Access reports with real-time data requirements with Darcy Branchini and bring notes back to Reporting SIG