Page Comparison

Attendance

Attendance & Notes

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

• See attendance list at bottom of page
  

Announcements and Reminders

Sharon

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?" 

• Important Upcoming Changes to LDP software support:

  • end of support is May 2025

  • see Mike Gorrell at Index Data for questions

  • institutions running LDP on a reporting database are encouraged to move to running Metadb software
    

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)

  • Are there any new fields or features we should know about from any of the functional areas that may impact reporting?

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

• Upcoming Reporting SIG meeting topics (tentative)
  

  • Moving from LDP to Metadb

  • Updates from the Data Array Extraction for Metadb 1.4 Workgroup

• Any new members?

  • Welcome/introductions

• How to find our latest recordings

  • Recording details available on our Reporting SIG Meetings and Notes page and Reporting SIG Subteam Meetings page

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 

  • urgently needed

  • work with reporting documentation team to  update Reporting section of FOLIO documentation for each FOLIO software release 

  • see https://docs.folio.org/docs/reporting/

• Query developers

  • ongoing need

  • work on derived tables and report queries for the FOLIO Analytics repository and to support Metadb

  • see https://github.com/folio-org/folio-analytics

Question:

How to match Course Reserve Titles to Vendor Electronic Usage reports?

Elena OMalley

Question:

If you were writing a report involving individual course reserves titles, what field would you include to help match it against vendor ebook (Clarivate/Proquest and EBSCO, mostly) usage reports? I was initially thinking eISBN, but MARC doesn't have a specific subfield for only eISBN, does it? Do ebook records have any convenient unique identifiers that would appear in both FOLIO and vendor reports?

Metadb Mapping Next Steps

Mike Gorrell

As posted on the FOLIO slack project channel, #metadb-mapping -

I have clarity around which tables the transformed data will appear in. There is an image of the data we are working with in the Metadb Documentation under section 2.5.4 Create Data Mapping:

Image Removed

And the CREATE DATA MAPPING commands:

CREATE DATA MAPPING FOR json
    FROM TABLE library.inventory__ COLUMN jsondata PATH '$'
    TO 't';
CREATE DATA MAPPING FOR json
    FROM TABLE library.inventory__ COLUMN jsondata PATH '$.metadata'
    TO 'metadata';
CREATE DATA MAPPING FOR json
    FROM TABLE library.inventory__ COLUMN jsondata PATH '$.tags'
    TO 'tags';
CREATE DATA MAPPING FOR json
    FROM TABLE library.inventory__ COLUMN jsondata PATH '$.tags.tagList'
    TO 'taglist';

Mapping a JSON object creates columns, and mapping a JSON array creates a table.  The only array in this example is tagList.  This results in an inventory__taglist table.  Everything else results in columns in the corresponding parent table, which in this case is inventory__t.The outermost object is a special case because there is no parent table.  So it results in the top-level inventory__t table.But if you imagine there is already a table inventory__t, the top-level columns and nested objects are added to it.

For more information, see the Derived Table JSON Mappings Workgroup
folder in the Reporting SIG google drive folder.Review a few Testing Notes

Next Steps:

1. Which Derived Tables to test next?

loans_items
item_ext
holdings_ext
instance_ext
instance_identifiers
locations_service_points
finance_transaction_invoices
holdings_notes
holdings_electronic_access
instance_statistical_codes
holdings_statistical_codes
locations_libraries
users_departments_unpacked
invoice_adjustments_in_addition_to
holdings_statements_indexes
holdings_statements
holdings_statements_supplements
finance_transaction_purchase_order
po_prod_ids
instance_administrative_notes
instance_contributors
item_notes

2. Clarity around how these new derived tables will be used - example queries?

Reporting SIG Goals for 2025

Sharon and Scott

If there is time, we’ll do a first cut on Reporting SIG Goals for 2025.

To start thinking about this, you can take a look at our projects here: Reporting SIG Projects

This is also a great opportunity to think about and share ideas, such as:

• What can you can bring to FOLIO Reporting to benefit the reporting community?

• What should the Reporting SIG do to support the reporting community?