Versions Compared

Old Version 5

changes.mady.by.user Sharon Beltaine

Saved on

compared with

New Version Current

changes.mady.by.user lm15@cornell.edu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Item

Who

Notes

Attendance & NotesScott

Attendance & Notes

  • Today's attendance-taker: Linda (or substitute)
  • Today's note-takers:  Team Leads for project updates


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
      • 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)
    • From Recent Meetings
      • 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
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUXPROD-3215
        )
      • (Jennifer Eustis) request for more helpful info when there are duplicate UUIDs during data import (
        Jira Legacy
        serverSystem JiraJIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyMDEXP-625
        )


Upcoming meeting topics (tentative)

  • Reporting Development in Preparation for Poppy Release
  • Reporting Experiences from Various Institutions
  • Reporting App demonstration
  • Metadb Updates for January 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.

*Nov 20 - FOLIO Application Poppy is released


Any new members?

  • Welcome/introductions


How to find our latest recordings


SIG Recruitment

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 Beltaine with any questions.

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


Reporting Rollout at University of Colorado, BoulderArthur Aguilera

Arthur will offer a presentation and discussion on the FOLIO reporting rollout at University of Colorado, Boulder.

  • went live June 2023 with FOLIO, new VueFind, and Metadb reporting database 
  • migrated from Sierra
  • contracted with Index Data for hosting
  • task force "reporting pod" for FOLIO Reporting was created and has been working on reporting for the past 2 years
  • pod learned SQL, surveyed reporting needs, and created 100+ queries; steep learning curve, but new skills beneficial to reporting staff
  • now looking to create permanent reporting group for all library data needs
  • created 3 types of reports: self-service reports, automated and scheduled reports, ad-hoc reports
  • manage issues in a github project board
  • reports stored on a github repository
  • created tracks and numbering schemas to categorize reports
  • dashboards created with Power BI (there is a free version that is easy to learn and it can be embedded into a Sharepoint site)
  • reports delivered as PowerBI dashboards or Excel files with data
  • created reports for historical data that are static
  • scripts create local tables in Metadb and report writer points to table from Power BI to create dashboard


Development Focus: Getting ready for the Poppy ReleaseScott Perry
Sharon Beltaine

Development Focus: Getting ready for the Poppy Release


Documentation Subgroup UpdatesEliana, Alex, Sharon

The FOLIO Reporting SIG Documentation Subgroup has been preparing updates to the Reporting section of the FOLIO documentation at docs.folio.org

  • see https://docs.folio.org/docs/
  • LDP1 and LDP2 references all changed to just "LDP"
  • "LDP Query Builder App" section updated to "Reporting App" 
  • Many updates to Reporting App section
  • Reminder: We could use one or two volunteers 


...

ItemWhoNotes
Review of In-Progress Projects (Recurring)
Review the release notes for FOLIO Analytics, LDP1, 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.


MM/RA/UM Working Group


ERM Working Group

  • Current topic
    • Reporting for the FOLIO App Open Access
  • Meetings are bi-weekly on tuesdays 11am ET alternating with ACQ Working Group


ACQ Working Group


Reporting SIG Documentation Subgroup

  • Orchid documentation is live on https://docs.folio.org/docs/
  • Poppy 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)


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 6th, Nov
    • Contact Stefan Dombek if you would like to get a calendar invitation


Product Council


For all recent work on FOLIO Reporting SQL development:


...