Versions Compared

Old Version 6

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

Saved on

compared with

New Version Current

changes.mady.by.user Angela Zoss (Old)

Saved on

Key

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

Date

...

Item

Who

Notes

AttendanceSharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Angela Zoss

Last week's notetaker: Vandana Shah

Updates from Various Reporting Related Groups and EffortsVarious

The Reporting SIG is using small work 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:

  • Community and coordination: the group worked on planning for WOLFCON, as well as the plenary presentation.
  • LDP Data Privacy Working Group: no update
  • LDP SysOps Working Group: no update
  • Software development:  Current work focuses on preparing the LDP Beta version to be released this month.  Also beginning to work on support for MARC data and ERM data.


Guide to Attending WolfCon 2020 Reporting Sessions remotelyAll 

All Reporting SIG members are encouraged to attend the upcoming WolfCon sessions remotely. You can filter on "LDP" to see reporting topics.

The ZOOM URL will be the same for all Reporting sessions: https://cornell.zoom.us/j/5196061050

Here is the WolfCon 2020 schedule: https://wolfcon2020a.sched.com/

NOTE: SIG will *not* meet Monday, January 20 - unrelated to WOLFcon, just a US Holiday

Q4 Fix Version Reporting JIRA Ticket UpdatesSharon

As the development timeframe of Q4 2019 has closed, we were asked to review and update our JIRA tickets assigned to this quarter. Let's take a look at the updates that were made:

There are a few reports/clusters that were requested but are not possible with just FOLIO data - that is, they include data from outside FOLIO, like ILL or Atlas integrations. We would like to reflect in JIRA that these reports are out of scope and need to be worked on by individual institutions (or groups of institutions) working on those integrations.

For "fix versions" (or assigning a FOLIO release date to a JIRA issue), we only have a couple of issues that we can predict the release date. These fix versions are being applied to UXPROD issues, which is where we've been creating our cluster issues. Some of the clusters are out of scope because of a data integration (see above), others just haven't been started yet and can't get a fix version.

  • UXPROD-2049 MM - Collections Analysis Cluster
    • note: MM cluster group has already listed the fields required for this cluster, so might be able to make progress soon
  • UXPROD-2025 RA-ILL Cluster
    • the reports in this cluster are all out of scope because FOLIO does not contain ILL data. Institutions need to look at these reports themselves
    • correction: sometimes ILL data is in FOLIO, because the loan is of an institution's item to someone at another institution, and some institutions use patron group to reflect that
    • these reports may need more information, maybe we should ask RA to provide additional details/specs
    • we could discuss this at WOLFcon
  • UXPROD-2030 RA-Reserves Atlas Cluster
    • seems like reports that require Atlas won't be possible
    • but is there work on doing reserves in FOLIO that would supplant Atlas/Ares?
    • Index Data may be working on a Reserves module
    • RA SIG is just starting to see development on Reserves module
    • Will ask at WOLFcon to try to get more information about what FOLIO is doing with reserves - maybe talk with Kelly Drake from FLO
    • Reporting SIG members should ask about integrations/reserves at their institutions
Prioritizing Reporting Clusters for the MVPAll

Several new reporting clusters have been created recently in JIRA as UXPROD issues. Each reporting cluster captures one or more reports with related data elements. We will review and prioritize these new issues for the MVP. Each institution should review and rank these clusters, as that will help with work prioritization.

Please rank yourself or send along to those at your institution who rank.

  • only two FLO institutions are going live this summer, so there's a question about who should vote
  • FLO institutions will also be using separate instances
  • Think Kelly Drake will be going through
  • two going live are working with Index Data on some stuff


  • question about documentation - should we be including links to the wiki prototype pages in the JIRA cluster/report issues?
  • maybe would be better to have JIRA issues for the prototypes, so we could associate those with people and track progress more easily
  • or could track just as part of the ticket workflow - "being prototyped"
  • think we probably do want the tickets, even if we have more ticket management after that
  • would probably be LDP issue
  • would link the prototype issue to the cluster
  • another idea would be to just use the cluster ticket as the prototype ticket
  • will discuss in our community coordination group
Reporting Prototypes and QueriesAll

Let's review our Report Prototype and Query Development Project List

Meeting Notes: See notes in the list (column "status").


Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 



Action items

  •   Community and Coordination group to discuss how to maintain GDPR compliance for REP 147 and REP 148
  •   Vandana Shahto follow up on notes for changes to JIRA tickets for MM Reports and Report Clusters
  •  Angela Zoss (Old) work with Nassib Nassar to go over names list, create final proposal
  •  Angela Zoss (Old)  (?) to share proposed list with POs of SIGs to make sure changed names still make sense
  •  Angela Zoss (Old) to follow up on concerns from Christie Thomas about developing queries using json_extract_path_text; does allow for joins on individual elements in an array, doesn't work on all reporting systems

...