2021-06-28 Reporting SIG Meeting notes

• Now have people interested from Pacific time
• Any flexibility to move later in the day?

Announcements /
Reminders

No meeting next week (July 5)

Fundamentals of the FOLIO Community (June 30 at 11am Eastern U.S. time)

• This webinar is the first in a new series of onboarding videos for community members. It will cover topics such as FOLIO’s governance structure and the relationship between libraries, vendors, and developers, user-experience design, and the FOLIO Code of Conduct.
• Register for the Forum by following this link to Zoom.
• A recording of this Forum will be included above and on the Open Library Foundation YouTube channel (https://www.youtube.com/c/OpenLibraryFoundation).

Reminder: Request for feedback

From MODUSERS-119:

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

• https://s3.amazonaws.com/foliodocs/api/mod-users/users.html#users_post
• https://s3.amazonaws.com/foliodocs/api/mod-users/groups.html#groups_post

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.

• Test Data Updates to FOLIO Snapshot Environments

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.

RM Working Group

• working on queries for the 1.2 FOLIO Analytics release
  • reviewed RM-Standing Orders query and ERM-Orders Status query, which are similar but will be posted separately due to minor differences in design
  • reviewed Open Order query
• 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
  • 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
• 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:

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

• Plan time for lots of testing LDP/queries
• With LDP, want to have a base system against which to compare
• End up using "require columns" system because queries won't work out of the box without certain columns that may not show up in local LDP
• would be good to have LDP access well before go-live
• If you're transitioning when you normally run statistics, make sure the queries are working
• Keep reminding staff to request queries as early as possible; they will come in at the last minutes

• 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

• Alternate FOLIO reporting systems
  • Google Sheets add-on (June 14)
  • ByWater system (June 28)
• 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