Versions Compared

Old Version 2

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version 3

changes.mady.by.user Sharon Markus

Saved on

Key

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

...

Item

Who

Notes

Attendance & NotesSharon

Attendance & Notes

  • Today's attendance-taker: Linda Miller
  • Today's note-takers:  Team Leads for project updates
Reporting Survey PresentationKevin Walker

Kevin will present a summary of the results of the Reporting SIG survey, which was sent to one reporting representative per FOLIO-participating institution. 


Updates from Various Reporting Related Groups and EffortsCommunity & Coordination, Reporting Subgroup Leads

Project updates

The Reporting SIG is using small working groups to address priorities and complete our work.  Each week, we will provide updates to the Reporting SIG from these various reporting-related groups and efforts. Reporting Development Team leads are encouraged to enter a summary of their work group activities below.

Community & Coordination: 

  • no meeting last week

FOLIO Reporting development

RA/UM Working Group

(same as last week) Moving on to refactoring, have 4 queries scheduled for R1 2021

  • Have a proposed fix for recalls from Cate
    • problem: want to be able to report on people who receive recalls. when a recall is requested, the request doesn't have a link to the active loan, so we don't currently know the correct borrower receiving that recall.
    • instead of creating the link, Cate suggested using the "dueDateChangebyRecall" flag on loan to find borrowers who'd had a recall. we'll also need the date, but they could just add that to the loan record.
    • any concerns with this? any other reasons we might need a direct link between a recall and a loan that this wouldn't resolve?
  • Continued work on refactoring - one done, one discussed. Planning to have 4 done fore R1 2021.
  • Meeting notes: https://docs.google.com/document/d/1UnzG64tl917LOH2FtWhCEPlSOsnJWKL-0eu88Ouo1DU/edit
  • Current status of RA/UM clustersissues: https://drive.googlegithub.com/file/d/1yQkPb7ORop5dzrdtSnU68c8YXu-jFSMN/view?usp=sharingfolio-org/folio-analytics/issues?q=is%3Aissue+is%3Aopen+RA%2FUM

MM Working Group

  • We worked on and closed issue 143.
  • For naming, po is used for purchase orders and pol purchase order lines.
  • Working group uses this spreadsheet to track JIRA issues, priority, and reports needed.

ERM Working Group

ERM Agreements Clusters will split up into eHoldings and local KB/GoKB related issues

  • eHoldings data within LDP:
    • Test data from Cornell has arrived
    • Consideration to develope a functional prototype by the subgroup
    • Development Resources are needed for a productional implementation (Frontend-Developer and Backend-Developer)have been loaded and verified
    • Starting on prototype development


Community & Coordination: 

  • no meeting last week

FOLIO Reporting development

RM Working Group

External Statistics Working Group

  • Recategorize External Statistics REP Issues
  • new organizational/tracking scheme for JIRA, with pointers to queries in folio-analytics repository
  • New organizational structure for External Statistics reports
    • external statistics reports (e.g., ACRL) typically require running queries from different functional reporting areas
    • these reports will be captured in JIRA under one UXPROD-XXXX report cluster issue, then the descriptions will point to each of the queries required to run them on the folio-analytics repository
    • institutions will need to rank each of these 8 new UXPROD-XXXX report cluster issues
    • each reporting development team will take responsibility for the queries in their area for the external statistics clustersEXAMPLE


Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


...