Versions Compared

Key

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

...

Item

Who

Notes

Attendance & NotesAngela

Attendance & Notes

  • Today's attendance-taker: Linda Miller
  • Today's note-takers:  Team Leads for project updates
New time for Reporting SIG meeting?All
  • Now have people interested from Pacific time
  • Any flexibility to move later in the day?

Announcements /
Reminders

Angela

Reminder: Request for feedback

From MODUSERS-119:

Detailed documentation has been published on https://dev.folio.org/reference/api/#mod-users . This includes

Please review and give feedback whether this is sufficient and this issue can be closed, or list the information that is still missing.

If you use these modules, please review the documentation over the next week or two and send feedback to Angela.


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.
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 HathiTrust reports are being reviewed. Duplicate orders and OCLC synchronization reports are coming soon.
  • Question: have MM reports been reviewed for impact of bound-with?


ERM Working Group


RM Working Group

  • a fund distributed invoice line even when paid does not show every fund distribution row in the transactions table (in the Finance application); this may be a local setup issue...
  • credits are shown as positive in the Finance application, which impacts calculations on some queries; reporting development group agreed to have instiinstitutions modify their queries locally to make adjustments for correct calculation results
  • 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

  • Submitted for PR
  • 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:


Scheduling future topicsAll
  • Volunteers for sharing reporting rollout plans
  • Volunteers for sharing how institutions are using the LDP
  • Prioritizing training topics
    • use of local schema for custom tables
    • more on MARC
    • using different applications (other than DBeaver)
    • Postman for API queries, also Insomnia
Topics for Future MeetingsAll
  • Alternate FOLIO reporting systems
    • Google Sheets add-on (June 14)
    • ByWater system (??)
  • 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
    • 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


Review and update Topics for Future Reporting SIG Meetings 





  •  A test Action Item (Ingolf)

...