Versions Compared


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





Attendance & NotesAngela

Attendance & Notes

  • Today's attendance-taker: Linda Miller Volunteer? E Pennington
  • Today's note-takers:  Team Leads for project updates

Announcements /


Recruiting New Query Developers

  • The Reporting SIG is always on the look-out for new query developers. Please let us know if you are interested in doing query development or if there are others at your institution who might be a good fit.

Test Data

FOLIO Reporting developers and Reporting SIG members are encouraged to use this new page to share test data cases they have entered into FOLIO reference environments to keep us all aware of what data to expect when we test our queries.

Cluster Ranking

New Report Clusters are added on a regular basis, so it is important to make sure your institution is reviewing these clusters and ranking them to establish report development priorities. If you rank reports for your institution, please follow the instructions below. If someone else ranks, please pass this information along to that person so your institution's vote can be included.

  • Action =>> Please review Reporting SIG-All Report Clusters (57 issues) in JIRA and RANK each report cluster for your institution (R1-R5)
  • For reporting, institutions only need to rank the UXPROD Report Cluster JIRA issues. All reporting requirements, which are captured in REP-XXX issues, roll up to the UXPROD Report Clusters. Report clusters cover one or more report (REP-XXX issue) requirements.
Update on LDP appAngela
  • Product Council has approved the LDP app for inclusion in FOLIO releases, pending satisfaction of any technical requirements decided on by Technical Council
  • Technical Council is working on those requirements and will try to turn that around quickly. One point of debate seems to be whether the LDP app code can live outside of the standards folio-org GitHub repository system.
  • Can institutions help with anything? Maybe generate test cases for bug fest?
    • LDP app is a bit different from other apps - not just a FOLIO app, also a ReShare app
    • LDP app probably will need to go through bug fest
    • Testing: user testing (bug fest) and automated testing (software engineering)
    • LDP app does have automated tests, but user testing has not been done
    • So yes, probably will need institutions to come up with user test cases for bug fest (will need to get Test Rail account, PO is responsible for making sure the test gets done, PO usually writes the test, but maybe SIG could help with that)
    • Nassib is the PO for the Reporting SIG generally, but the PO for the LDP app is actually Charlotte Whitt, but she's out this week
    • Possibly follow up with Charlotte to see what we could do while we wait
Presentation of KNIME, PostmanAngelapushing to a future week
Brainstorm queries for sprint review for LDP appAll
  • Derived tables - in-app reports right now don't really blend data from multiple apps, so this does allow for that
  • There should be local schema in there, but since it's not working we may just not mention
  • In Transit: things are going to be stuck in transit and they're going to go up to the shelves
  • Statistical Code: query search in FOLIO, when you get to large searches it just times out
  • Finances would have been nice, but snapshot doesn't have data
    • ID might be able to put data in there, or maybe someone could manually add data first thing in the morning
    • Invoices and Finance do not yet have the export to CSV.  Orders has the CSV export. We would need invoices or budget entries.
    • PO to Instance derived table would cross those areas
    • Finance probably has more than invoices
    • see if we can populate data into the finance derived tables
  • Users who will be expiring soon, or maybe already expired (inactive, or users without barcode)
    • could maybe sort by expiration date and then use some other filter
Update LDP implementers gridAllFOLIO LDPLDP1-based Reporting First Implementers Grid
Updates and Query Demonstrations from Various Reporting Related Groups and EffortsCommunity & Coordination, Reporting Subgroup Leads

Project updates

Reporting development is using small subgroups to address priorities and complete work on report queries.  Each week, these groups will share reports/queries with the Reporting SIG.  Reporting development team leads are encouraged to enter a summary of their work group activities below.

RA/UM Working Group

MM Working Group

  • The group is still on pause. Our meetings will reconvene Aug. 3, from 12-1pm ET via zoom

ERM Working Group

RM Working Group

  • no meeting last week
  • several queries for RM completed, but still need documentation, testing, and review
  • working on queries for the 1.2 FOLIO Analytics release
  • for latest updates, see RM Prototype and Query Development Status
  • Friday the RM SIG proposed a new organization; ERM would be raised to level of SIG, and RM would join Acquisitions group to form an Acquisitions SIG, also elevate Open Access group to a SIG

Reporting SIG Documentation Subgroup

  • No changes
  • Additional Context

External Statistics Working Group

  • no updates currently
  • ACRL query set included in FOLIO-Analytics 1.1 release
  • new organizational/tracking scheme for JIRA, with pointers to queries in folio-analytics repository
  • New organizational structure for External Statistics reports
    • external statistics reports (e.g., ACRL) typically require running queries from different functional reporting areas
    • these reports will be captured in JIRA under one UXPROD-XXXX report cluster issue, then the descriptions will point to each of the queries required to run them on the folio-analytics repository
    • institutions will need to rank each of these 8 new UXPROD-XXXX report cluster issues
    • each reporting development team will take responsibility for the queries in their area for the external statistics clusters

For all recent work on FOLIO Reporting SQL development:

Topics for Future MeetingsAll
  • Follow-up on MARC status, Quickmarc/Data Import conflicts
  • How to strengthen connections to SIGs and their developers to be kept in the loop about changes to the data model
  • Show and tell
    • how are institutions using the LDP
    • examples of using the local schema
    • Cornell's report ticketing system
    • Rollout plans from institutions
    • Ask someone on the sysadmin side to talk about LDP administration (Jason Root?)
  • Training topics
    • adding test data in FOLIO snapshot
    • How to do ad hoc querying with the derived tables
    • How to use the LDP app
    • using KNIME to build reports
    • use of local schema for custom tables
    • more on MARC
    • using different applications (other than DBeaver)
    • Postman for API queries, also Insomnia
  • Upcoming:
    • 16 August: presentation from ERM group on metadb/ERM
    • 9 August: Angela presents on KNIME, Postman
    • TBD: Sharon presents on Virtual DBeaver

Review and update Topics for Future Reporting SIG Meetings 

  •  A test Action Item (Ingolf)