2020-01-13 Reporting SIG Meeting notes

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

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:

• Fix Version Updates
• Out of scope issues

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

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.

• UXPROD-2051 MM - Shelflist Report Cluster - done
• UXPROD-2052 MM - Quality Control Cluster - done
• UXPROD-2049 MM - Collections Analysis Cluster- done
• UXPROD-2216 Cataloging Status Cluster - done
  • Christie is working on this
  • There is a prototype - Uncatalogued materials report prototype
  • close to being done with finding all of the data points
• UXPROD-2029 RA-Requests Cluster - done
• UXPROD-2028 RA-Print vs. Eprint Cluster 
• UXPROD-2027 RA-Missing Items Cluster
• UXPROD-2026 RA-ILL DocDel Cluster
• UXPROD-2025 RA-ILL Cluster
• UXPROD-2024 RA-Holds Cluster
• UXPROD-2017 RA-Collections Recalls Cluster
• UXPROD-2023 RA-Fine/fee Cluster
• UXPROD-2022 RA-DocDel Cluster
• UXPROD-2021 RA-Delivery Services Cluster
• UXPROD-2020 RA-Collections UM Cluster
• UXPROD-2019 RA-Collections Reserves Cluster
• UXPROD-2018 RA-Collections Renewals Cluster
• UXPROD-2215 LDP-MARC-table
• UXPROD-2030 RA-Reserves Atlas Cluster
• UXPROD-2031 RA-Serials Use Cluster
• UXPROD-2032 RA-Slips Notices Cluster
• UXPROD-1915 RA-Collections Use Cluster

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

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

• Report Prototype and Query Development Project List

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

Review and update Topics for Future Reporting SIG Meetings