Page Comparison

...

XXXX

Preset?	Name	Organization	Present?	Name	Organization
X	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
	Elizabeth Edwards	University of Chicago	X	Tod Olson	University of Chicago
	Claudius Herkt-Januschek	SUB Hamburg	X	Scott Perry	University of Chicago
X	Doreen Herold	Lehigh University		Stefan Stadtherr	MPIL Heidelberg
X	Anne L. Highsmith	Texas A&M	X	Simona Tabacaru	Texas A&M
	Harry Kaplanian	EBSCO	X	Kevin Walker	The University of Alabama
X	Ingolf Kuss	hbz		Charlotte Whitt	Index Data
	Lina Lakhia	SOAS		Michael Winkler	OLE
X	Joanne Leary	Cornell University		Uschi Klute	GBV
X	Michael Patrick	The University of Alabama			Holly Mistlebauer	Cornell University
	Nassib Nassar	Index Data	X	Angela Zoss	Duke University
	Veit Köppen	University Magdeburg	X	Lisa DeCarolis	Smith College/Five Colleges
X	Linda Miller	Cornell University			Philip Robinson	Cornell University
	Filip Jakobsen (guest)	Samhaeng		Jackie Gottlieb
X	Jackie GottliebElena OMalley

Discussion Items

Item	Who	Notes
Assign Notetaker, Take Attendance, Review agenda	Sharon	Today's notetaker: Scott Perry Last week's notetaker:

Tod Olson and Ingolf KussIn App ReportingFilip Jakobsen, Holly Mistlebauer

Filip joins this week's Reporting SIG meeting to provide an overview of his vision for in-app reporting in FOLIO

introductions
Filip's vision for in app reporting
Reporting SIG members: questions, comments, discussion

NOTES

-form filler functionality discussed with ERM is similar to Filip's vision for in app reporting

-we have search and filter functionality in FOLIO today; could save templates as form

-many reports we are doing today could be delivered as in app reports

-logic of having a checkbox, search, and filter with csv download

-if we build search/filter/checkbox functionality into the applications (see UI prototype design below), we could deliver many in app reports

-add "associated records" to application window to allow user to select data elements from different apps

-(Tod) fits well with moving away from Stripes toward GraphQL

-(Nassib) workflow engine could orchestrate representation

-(Tod) if we make templates, need to make sure they could be called from an API and a workflow

Related issues we have discussed and we will discuss further at future meeting

distinction between in-app reports and LDP datawarehouse reports: real-time data vs day-old data
review JIRA tickets for in-app reports
details on the interface to pull data out of different applications
timeframe, project planning for in app report (features) development
2 basic types of in-app reports: Excel exports and other more detailed reports
discuss possible candidate for a pilot area to implement in-app reporting functionality; discuss timing, scope, etc.; best to look for an area where ad hoc reporting is needed (user management?)

A number of reports have been taken on as in-app, these have been what you might call "static reports", like patrons that owe over N amount of fines, which everyone will want.

Have also been talking about exports to CSV, which are similar data to static reports but can be sent to a spreadsheet

Looking for feedback from Reporting SIG members: Are we going in the right direction?


Update and Demos from the LDP Report Working Group	Angela, 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 NOTES: 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. GitHub 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	All	Review and update Topics for Future Reporting SIG Meetings
Other Topics?	All	Any 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

Versions Compared

Old Version 2

New Version Current

Key

Discussion Items

Action items