Page Comparison

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
  • From Recent Meetings
    
    • 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)
    • 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) (

      Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-3215

      )
    • (Jennifer Eustis) request for more helpful info when there are duplicate UUIDs during data import (

      Jira Legacy
      server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MDEXP-625

      )

Upcoming meeting topics (tentative)

• Reporting Development in Preparation for Poppy Release (ongoing)
• Reporting Experiences from Various Institutions (Stanford December 7)
• Metadb Updates for version 1.2 release (February 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.

*December 18 - 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 

ACQ + ERM are reunited.

Discussion on structuring an overview of reporting options:

• How we can structure the overview so that it can be used to select software?
• Look at multiple layers for each reporting option
  
  • Datasource, e.g. FOLIO
  • How are the data collected? E.g. with Metadb
  • Database, e.g. POSTGRES
  • Data presentation, e.g. 3rd party solution
• Each layer should described with:
  
  • Where is it hosted?,
  • Who is the vendor?,
  • Is there support?
  • etc.
• This is a good approach for a matrix
• After the matrix there is a critical overview in text form for each option

(Note from Tod: What sort of additional software is needed to interact with the data and make reports. i.e., is an external tool needed to run SQL (DBeaver, MS Access, Python scripts) or is there some sort of built-in functionality for building and running?