|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||Tod Olson||University of Chicago|
|x||Claudius Herkt-Januschek||SUB Hamburg||x||Scott Perry||University of Chicago|
|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|
|Munich Technical University Library|
|Joanne Leary||Cornell University||Uschi Klute||GBV|
|x||Michael Patrick||The University of Alabama||x||Vandana Shah||Cornell University|
|x||Nassib Nassar||Index Data||x||Angela Zoss|
|x||Veit Köppen||University Magdeburg||Lisa DeCarolis||Smith College/Five Colleges|
|x||Linda Miller||Cornell University||x||Elena O'Malley|
|Matt Harrington||Duke University||Holly Mistlebauer||Cornell University|
Today's Attendance Taker: Linda Miller
Today's notetaker: Vandana Shah
Last week's notetaker: Sharon Beltaine
|Updates from Various Reporting Related Groups and Efforts||Various|
The Reporting SIG is using small work 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:
|Request for More Data Analysts on the RPWG||Sharon|
The Report Prototype Working Group is hard at work building report prototypes and queries to support FOLIO participants reporting requirements. We need more data analysts to join this group to get our reports done on time for upcoming Go Lives. Let's discuss possibilities in more detail.
This is an opportunity for people to develop skills (SQL), as these skills will be needed in the future too. Are there additional resources (people from other institutions who can join us) for query writing? A lot of institutions are represented here, we are in a work crunch, and need more resources from other institutions. Linda would like to see report clusters to get a better idea of what's needed in report prototyping and query writing.
Nassib noted that the test database was set up a while ago, would the analysts like to start working with that? Do people recognize how they will interact with the reporting system, can we experiment with that?
Sharon: At Cornell, a small group will take the query templates and edit them for Cornell's needs, will learn core SQL needed, and will learn to write queries from scratch, so that when we go live, we can report out as needed. How are others structuring this? Angela: Duke is looking for others interested in SQL development, hope to have something by go-live that's an easier interface. Kevin: his institution is working on this, to see which tools will work best for their reporting purposes.
Nassib: Microsoft Access is currently not too compatible with PostgreSQL, it needs more testing with the newest version of Access. Also, the newer version of PostgreSQL (upcoming) may also be compatible with Access. Nassib has requested Index Data dev ops people to test a public version of the LDP, and they may be able to address the issue of Access incompatibility. More deeply nested attributes in the JSON data will be not be available through Access's visual query builder. For now, this is the best we can do, and if lots of queries are using the nested data, the columns can be generated by individual institutions from the FOLIO data table.
Kevin: Can everyone from this group commit to writing at least one query? That's very important right now.
|SQL Training Resources for LDP Query Development||Nassib, Angela, Kevin, Sharon|
A number of training tools and resources have been identified to jump start data analysts who can join the RPWG report prototype and query building efforts. We'll review these during our meeting. Nassib shared some resources from Stanford which are an excellent source for a conceptual background. Vandana suggested a resource for hands-on SQL training.Please add to the training resources page, if you have any resources in mind.
|Review of Non-Clustered RA Reports||Angela|
Angela will walk us through a review of Resource Access reports that did not fit into a cluster category.
See the list at
RA clusters have been uploaded to the Google drive. Next step was to create UXPROD issues in JIRA to represent each cluster. Each issue shows the reports included in each cluster, sorted by cluster labels. The po-mvp labels indicate that at least one inquisition needs this at go-live. Good news is that only half of the clusters in RA are needed at go-live. This will help with prioritization. Originally 100 reports had been added to the RA master sheet. Only 50 reports were clustered, as the remaining did not fit into any RA clusters. For example, reports on batch jobs - these could be moved elsewhere. Also some need to be pushed back into in-app.
|Topics for Future Meetings||All|
Review and update Topics for Future Reporting SIG Meetings
- Reporting Data Privacy to follow up with Jesse, Tod, and Cate, and Chair-Elect to determine approach to audit trails in LDP