Today's note-takers: Team Leads for project updates
Product Council
Jennifer
Announcements/Reminders
Scott
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
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.
(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
)
FOLIO Analytics Update
Poppy and FOLIO Analytics 1.7 were both released in December.
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)
We will need to be recruiting for a variety of roles in the coming months. Please consider whether you would be interested. Reach out to Scott Perry or Sharon Markus with any questions.
Representative for the Documentation Working Group
Query developers - possibly from Index Data?
FOLIO Analytics Review Board
Reporting Documentation Update for Poppy
Eliana
Review of Known Data Field Changes
Sharon
Recurring Items (Updated weekly, but not always discussed in meeting)
Updates and Query Demonstrations from Various Reporting Related Groups and Efforts Projects (Recurring)
Community & 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.
MM/RA/UM Working Group
Leadership transitioning to Christie Thomas
Meetings to be held on the 2nd Wednesday of the month at 12:00 PM ET
see the folio-mm-ra-um channel on the Metadb slack for more information
The Reporting SIG has representation on the Documentation Working Group, which is building end-user documentation for https://docs.folio.org/docs/ (mostly linking to existing documentation over on GitHub)
D-A-CH Working Group (D-Reporting)
Ongoing topics
Onboarding training
DBS statistics
JIRA-Issues, Rpt-Clusters
Gap analysis to statistic codes, user counts etc.
Identifying functions that we need for statistics in Germany but are not yet implemented in FOLIO
Meetings
Next meeting will be at 20th, Nov
Contact Stefan Dombek if you would like to get a calendar invitation