Page Comparison

Announcements /
Reminders

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.

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 LDP implementers grid

• FOLIO LDP-based Reporting First Implementers Grid (now with metadb column)

New FOLIO Query Writing Knowledge Base

• See "Writing Queries" section in the sidebar of the wiki

RM Working Group

• dividing fund_expenditures_by_po_line into 2 queries: one that uses invoice payments as date range and another that uses fiscal year
• reviewed HathiTrust serial holdings report, revised for use at Cornell
• exploring ways to make it easier to find options for reporting parameters in your LDP (e.g., a list of locations, item statuses, etc.)
• several queries for RM completed, but still need documentation, testing, and review
• for latest updates, see RM Prototype and Query Development Status

Reporting SIG Documentation Subgroup

• No changes
• Additional Context
  • Over the next few months, Reporting SIG Documentation Subgroup will be helping to build end-user documentation for https://docs.folio.org/docs/ (much will be linking to existing documentation over on GitHub)
  • see Reporting SIG Documentation Subgroup and Guide to Reporting Documentation pages in this wiki

External Statistics Working Group

• no updates currently
• 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

Product Council

For all recent work on FOLIO Reporting SQL development:

• https://github.com/folio-org/folio-analytics/commits/main

• 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?)
  • What is done in JIRA? (JIRA clean up)
• 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 (LDP edition)
  • use of local schema for custom tables
  • more on MARC (ask Jennifer)
  • using different applications (other than DBeaver)
  • Insomnia for API queries?
  • SQL
  • LDP to metadb
  • non-Roman script querying (Stefan)
  • Metadb implications
    • if schema changes, will that be relatively seamless? old fields still in history, but new fields in current?
    • if fields are deprecated and removed, what happens if they come back again?
    • how will deleted records show up?
• Discussion:
  • how to rank clusters with institutional rankings going away?
  • consortia SIG is talking about a central office app of some kind; that app might need to deal with consortia-wide reporting
  • how to train:
    • wiki pages with examples? form a small project team? (e.g., how to pull from marc, how to use local schema)
    • each dev team create training about the data structures in that area?
  • Query style (ask Nassib)
• Upcoming:Oct 25:
  walk through of LDP and metadb
  • Nov 1: DBeaver tips (Sharon)
  • Nov 8: optimization?? (Axel??)

Review and update Topics for Future Reporting SIG Meetings