Skip to end of banner
Go to start of banner

2024-11-25 Reporting SIG Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Date

How to Join the Meeting

Meetings are held on Zoom on the first 4 Mondays of each month at 11:00 am Eastern U.S. time (see this time in your time zone). The first and third Mondays focus on Reporting Development topics, and the second and fourth Mondays focus on Reporting Business topics.

Here are the Zoom details:

Join from PC, Mac, Linux, iOS or Android: https://openlibraryfoundation.zoom.us/j/601231377?pwd=ZVFtQWxUaTFLb1J3b1JPdlZqZU1lQT09

Or iPhone one-tap (US Toll):  +13017158592,,601231377# or +13126266799,,601231377#

Or Telephone:

    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)

    Meeting ID: 601 231 377

   Find your local number: https://openlibraryfoundation.zoom.us/u/ketrxUP4uW

Attendees

Present?

Name

Organization

Arthur Aguilera

University of Colorado, Boulder

Erin Block

University of Colorado, Boulder

Shannon Burke

Texas A&M University

Suzette Caneda

Stanford University

Mark Canney

Lehigh University

Dung-Lan Chen

Skidmore College

Lloyd Chittenden

Marmot

Ann Crowley

Cornell University

Tim Dannay

Mount Holyoke College

Danielle Dempsey

Villanova University

Axel Doerrer

University Mainz

Shelley Doljack

Stanford University

Stefan Dombek

Leipzig University

Jennifer Eustis

U. Massachusetts Amherst / Five College

Lynne Fors

Wellesley College

Vanessa French

Lehigh University

Lisa Furubotten

Texas A&M University

Mike Gorrell

Index Data

Alissa Hafele

Stanford University

Lucy Harrison

GALILEO

Kara Hart

Wellesley College

Andrew Henryson

Texas A&M University

Corrie Hutchinson

Index Data

Jamie Jesanis

MCPHS

Jeanette Kalchik

Stanford University

Harry Kaplanian

EBSCO

Sarah Kasten

University of Chicago

Tim Kiser

Michigan State University

Kevin Kishimoto

Stanford University

Ingolf Kuss

HBZ

Alexander Lao

Stanford University

Joanne Leary

Cornell University

Eliana Lima

Fenway Library Organization

Eric Luhrs

Lehigh University

Sharon Markus

Cornell University

Kathy McCarthy

EBSCO

Lisa McColl

Lehigh University

Linda Miller

Cornell University

Joseph Molloy

Spokane Public Library

Kathleen Moore

EBSCO

Nassib Nassar

Index Data

Elena O'Malley

Emerson

Tod Olson

University of Chicago

Jean Pajerek

Cornell University

Kimberly Pamplin

Texas A&M University 

Scott Perry

University of Chicago

Natalya Pikulik

Cornell University

Emily Sanford

Michigan State University

Bob Scheier

Holy Cross

Vandana Shah

Cornell University

Linnea Shieh

Stanford University

Rebekah Silverstein

Oklahoma State University

Susie Skowronek

Oakland University

Ken Smith

Valdosta State University

Kimberly Smith

Middle Tennessee State University

Clare Spitzer

Stanford University

Amelia Sutton

U. Massachusetts

Simona Tabacaru

Texas A&M University

Huey-Ning Tan

Stanford University

Vitus Tang

Stanford University

Christie Thomas

University of Chicago

Irina Trapido

Stanford University

Catherine Tuohy

Emmanuel College

Patrick Waite

U. Mass Amherst

Visitors:

Discussion Items

Item

Who

Notes

Attendance

Attendance & Notes

  • Today's attendance-taker: Linda (or substitute)

Announcements and Reminders

Scott

Announcements:

  • About the Reporting SIG meeting schedule

    • Meetings are held on the first 4 Mondays of each month at 11:00 am Eastern U.S. time (see this time in your time zone). The first and third Mondays focus on Reporting Development topics, and the second and fourth Mondays focus on Reporting Business topics. 

    • "business" means topics like presentations on reporting functionality and new features, new reporting applications, surveys and studies on reporting, etc.

    • "development" means working on derived tables and report queries for the folio-analytics GitHub repository

    • "workshopping" queries could be scheduled during any of these meetings, and it would be great to have topics and/or questions in advance so we can prepare to walk through the answers/approaches, such as "how to I fix this inventory query to get rid of the duplicates?" or "what is the best way to calculate totals in this finance query?" 

  • November 25 and December 23 meetings are canceled

Ongoing Topics:

  • Workshopping your queries

    • part of each Reporting SIG business meeting will be devoted to time to work through any query questions you may have

    • please reach out to Christie Thomas if you have a question you would like to "workshop" during an upcoming Reporting SIG meeting

  • Impacts of New Fields and Features (Sharon)

  • Upcoming Reporting SIG meeting topics (tentative)

    • Derived Tables

    • Reporting App use at various institutions

    • More Metadb training

  • Any new members?

    • Welcome/introductions

SIG Recruitment:

We will need to be recruiting for a variety of roles in the coming months. Please consider whether you would be interested. Please reach out to Scott Perry or Sharon Markus with any questions.

  • Representative for the Documentation Working Group 

Working Group:

Metadb version 1.4 mappings for data array extraction

Mike

This will be a working group meeting where Mike Gorrell, LDP/Metadb Project Director at Index Data, will walk us through the process of preparing mappings for data array extraction for the upcoming release of Metadb 1.4 software

  • Deployed in 2 environments (CU Boulder and Lehigh)

  • Testing to be conducted over the next few weeks:

    • Add Mappings to correspond to some of the derived tables (See example below). Run queries using those new mappings.

    • Add Mappings of more complex extractions (thank you for some test cases to use I will publish the list we have later this week). Run queries using those new mappings

    • ReSync to measure impact of CREATE MAPPING - First or second week of December

  • Working group being formed to create the mapping over the next several weeks.

  • Close to collecting daily statistics on Derived Table usage

Update on new FOLIO Reporting Environment

  • This environment will include:

    • A FOLIO environment (Ramsons and then Sunflower - roughly the same timeframe as BugFest)

      • Including the Reporting AppU

    • A Metadb synced with ^ FOLIO

  • Hoping to have it built in early December


Example of a Mapping created from a derived table creation script. From the po_lines_cost.sql script:

  • FROM:

jsonb_extract_path_text(pol.jsonb, 'cost', 'listUnitPrice')::numeric(19,4) AS po_line_list_unit_price_phys,
jsonb_extract_path_text(pol.jsonb, 'cost', 'quantityPhysical') AS po_line_quant_phys,
jsonb_extract_path_text(pol.jsonb, 'cost', 'listUnitPriceElectronic')::numeric(19,4) AS po_line_list_unit_price_elec,
jsonb_extract_path_text(pol.jsonb, 'cost', 'quantityElectronic') AS po_line_quant_elec,
jsonb_extract_path_text(pol.jsonb, 'cost', 'additionalCost')::numeric(19,4) AS po_line_additional_cost,
jsonb_extract_path_text(pol.jsonb, 'cost', 'currency') AS po_line_currency,
jsonb_extract_path_text(pol.jsonb, 'cost', 'discount')::numeric(19,4) AS po_line_discount,
jsonb_extract_path_text(pol.jsonb, 'cost', 'discountType') AS po_line_discount_type,
jsonb_extract_path_text(pol.jsonb, 'cost', 'poLineEstimatedPrice')::numeric(19,4) AS po_line_estimated_price

TO this in the Mapping file

CREATE DATA MAPPING FOR json FROM TABLE folio_orders.po_line__ COLUMN jsonb PATH '$.cost' TO 'cost';

note that there is no way to limit the fields extracted, or to rename the columns as part of this feature.


NOTE LDP Software retirement is May 1, 2025

  • Please reach out to Mike Gorrell at Index Data if you have questions

  • All institutions who have been running LDP should be completely migrated to Metadb by that date

Recurring Items (Updated weekly, but not always discussed in meeting)

Item

Who

Notes

Review of In-Progress Projects (Recurring)

Review the release notes for FOLIO Analytics, LDP, LDLite, LDP Reporting App, ldpmarc, Metadb Projects (Recurring)

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.

D-A-CH Working Group (D-Reporting)

  • A few libraries in Germany would like to start using Metadb soon. In most cases, hosting is in own data centers. The working group needs experience reports on what resources are required.

  • Ongoing topics: Workshopping, DBS statistics

    • Unification of reference data when mapping data from German union catalogs to FOLIO. Collaboration with the MM working group (D-A-CH).

    • Statistics after data anonymization according to GDPR. Collaboration with the RA/UM working group (D-A-CH).

  • Meetings: Contact Stefan Dombek if you would like to get a calendar invitation

Reporting SIG Documentation Subgroup

  • Quesnelia documentation is live on https://docs.folio.org/docs/

  • Ramsons documentation is in development

  • Additional Context

    • 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)

For all recent work on FOLIO Reporting SQL development:

FOLIO Product Council

Jennifer Eustis

2024-10-31 Product Council Meeting Notes

  • FOLIO Bugfest starts on 11/11 for 2 weeks. There is a real need for testers.

  • New Claiming App (Sunflower). With Sunflower, there will be a new App for claiming. This app will simplify the identification of late pieces and allow institutions to send claims to vendors.

2024-10-17 Product Council Agenda and Meeting Notes

PC is looking at goals for this year. One goal is working on prioritization. The PC would like to be able to understand what the priorities are for each SIG and possible gaps. Other SIGs are creating Implementers pages through the use of Jira dashboards and lists of issues. Examples are:

Acquisitions SIG: Acquisitions/Resource Management implementers

Data Import: Data Import Implementers Topic Tracker

BELA: Bulk Edit Resource Management Implementation Topics

Each SIG and working group approaches this slightly differently depending on the needs of the group. What would work here to communicate the priorities and gaps with FOLIO reporting to the PC?

  • No labels