Page Comparison

Announcements/Reminders

Impacts of New Fields and Features (Sharon)

• 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)
    • UXPROD 4345
  • (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

    )
Review and update the Impacts of New Fields and Features on Reporting grid 

FOLIO Analytics Update

• Poppy and FOLIO Analytics 1.7 were both released in December.

Metadb Update

• see important bug announcement for Metadb
• https://github.com/metadb-project/metadb/issues/58
• from Nassib: It is recommend that users not rely on transformed tables that are generated from any table containing more than one jsonb column. The most likely fix for this bug in the short term is that such transformed tables will be removed.
• (from Tod) There should be a way to interrogate the Postgresql schemata to find out which tables have more than one JSONB column
  • can use the `information_schema.columns` view
• Only one table known so far re: #58: folio_entities_links.instance_authority_linking_rule

Upcoming meeting topics (tentative)

• Reporting Documentation Update for Poppy (January) 
• Metadb version 1.2 release overview (February)

Any new members?

• Welcome/introductions

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

Reporting Documentation Update for Poppy

Review of Known Data Field Changes

Eliana will walk us through the most recent updates made for Poppy to the Reporting section of the FOLIO documentation site by the Reporting SIG Documentation subgroup (Eliana, Alex, and Sharon). 

New Metadb Section added to Folio Analytics Wiki

Stefan will walk us through his newest addition to our documentation on FOLIO Analytics: under the General section, he has added a cookbook on how to query data from Metadb using SQL.