2023-11-13 Reporting SIG Meeting notes

Announcements/Reminders

Impacts of New Fields and Features

• Are there any new fields or features we should know about from any of the functional areas that may impact reporting?
  • New
    • We will be getting new data fields for the Open Access app - more details coming
    • Timezone format is not consistent across the tables in FOLIO, which impacts LDP and Metadb
      • Nassib confirmed that he does not change timezone settings as part of the ETL with the LDP/Metadb software, so whatever is in FOLIO is what we get in LDP/Metadb
      • RFC-3339 sitting with TC about always representing times as an ISO date format https://github.com/folio-org/rfcs/pull/13
    • Invoices will have a fiscal year assigned. You will be able to process an invoice in a past fiscal year (with Poppy) and in a future fiscal year (after Poppy)
  • From Recent Meetings
    
    • There is a proposal to deprecate the donor field in the POL and replace it with an Organization type of donor in Quesnelia.  This will also be linked to inventory in a future release as well.
    • (Jennifer Eustis) from MM: proposal for a new field for item source (New field in the item record: Source ID - Functional analysis)
    • (Stefan Dombek) feature with Orchid: in the module audit, we have logs for orders and order lines and snapshot for create, edit, and delete records (unfortunately not for fiscal year rollover, just create/edit/delete; need to know the date of your FYO and then report based on that) ( UXPROD-3215 - Getting issue details... STATUS )
    • (Jennifer Eustis) request for more helpful info when there are duplicate UUIDs during data import ( MDEXP-625 - Getting issue details... STATUS )

Upcoming meeting topics (tentative)

• Reporting Development in Preparation for Poppy Release
• Reporting Experiences from Various Institutions
• Reporting App demonstration
• Metadb Updates for January 2024

(Slightly Changed) FOLIO Analytics 1.7 Poppy Development and Review Schedule

• Oct 27 EOD: Last day to submit new Pull Requests for 1.7 Poppy release of Folio Analytics.
• Oct 30 - Nov 3: Review Board completes review of all 1.7 code.
• Nov 6 - Nov 10: Code fixed by report development teams per review board feedback.
• Nov 10 - EOD:  Feature Freeze. 
• Nov 13 - Nov 22: Testing.
• Dec 1: Folio Analytics 1.7 is released.

*Nov 20 - FOLIO Application Poppy is released

Any new members?

• Welcome/introductions

• Representative for the Documentation Working Group
• Query developers - possibly from Index Data?
• FOLIO Analytics Review Board 

Development Focus: Getting ready for the Poppy Release

• see current issues on folio-analytics
• see current pull requests on folio-analytics
• see https://github.com/folio-org/folio-analytics/wiki for Changes by Release notes
• see FOLIO Analytics Review Board for information on query reviews for the Poppy release
• status of pull requests for 1.7 Poppy Release
• wiki updates for 1.7 Poppy Release
• questions?

Reporting Product Owner Corrie Hutchinson will demonstrate the use and configuration of the Reporting App (replaces the LDP App). The Reporting App is used to query data on your LDP or Metadb reporting database. A new feature has been added for the Poppy release to allow running queries stored on GitHub repositories to be run right from the Reporting App in FOLIO. 

• allows institutions to create connections to run sql queries on their LDP or Metadb instances and export results right from within the FOLIO application Reporting App
• you can connect to a variety of repositories; repositories must be public; later feature will allow private repos
• "run reports" functionality populates with the queries in the repository
• can set default parameters for queries
• run the report and export as csv
• every sql query requires json metadata file - Mike Taylor has written instructions at https://github.com/folio-org/ui-ldp/blob/master/doc/reports.md
• JSON file describes how the report runs and includes parameters
• interest in public query repositories available
• suggest we have future topic of how insitutions manage their report github repositories

Questions

• Can we write queries in non-sql languages to be run with the Reporting App (e.g., python)?
• Will there be an Actions menu, as we have in other FOLIO app interfaces?
• Are there plans to make more github repositories of FOLIO report queries public?
• Can the Reporting App hook up to LD Lite? 
• How long will there be support for both LDP and Metadb platforms with the Reporting App?
• Stay tuned on slack as Corrie researches answers to questions (Thank you, Corrie!)

Feature Requests

• Contact Corrie Hutchinson with questions and new feature requests

The PC met last Thursday on 11/9 and the notes can be found at 2023-11-09 Product Council Agenda and Meeting Notes. The PC SIG working group updated the PC on its progress. The template for SIG reports was rolled out in October. Feedback that was received has been incorporated into the template. The next written report is for 11/16 and can be found SIG Reports 2023-11-16. Bulk Edit and List App will have the same working group. Slack channels and the group name have been renamed.

2023-09-14 Product Council Agenda and Meeting Notes

Here's the wiki page for the tri council subgroup: FOLIO Product Council Sub Group on the Re-Architecting's Impact on the Product Council (Tri-Council)

Some additional useful links:
https://folio-org.atlassian.net/wiki/display/PC/2023-11-09+Product+Council+Agenda+and+Meeting+Notes
https://folio-org.atlassian.net/wiki/display/PC/SIG+Reports+2023-11-16