Versions Compared

Old Version 8

changes.mady.by.user Nassib Nassar

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

AttendanceSharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Anne Highsmith

Last week's notetaker: Sharon Beltaine

Project Tracking UpdateSharon, Nassib, Holly

Sharon, Nassib, and Holly have been working on organizing reporting JIRA issues for capacity planning.

Here is an update:

  • REP-XXX issues (data warehouse reports) must be converted to UXPROD-XXXX issues to be included in capacity planning (issue contents will stay the same)
  • Each reporting JIRA issue will:
    • be ranked
    • be estimated (later)
    • roll up to an associated Epic
    • include po-mvp label if part of MVP
  • Reporting JIRA Issues fall under these EPICs:
    • UXPROD-1128 - LDP Beta 1 - Summer 2020 (rank = go live)
    • UXPROD-1881 - LDP Beta 2 - October 2020 (rank = up to a quarter after go live)
    • UXPROD-1882 - LDP 1.0 - Summer 2021 (rank = up to a year after go live)

Nassib noted that the conversion would go quickly but that the estimating would take some time. Also, some existing FOLIO issues are blockers; need to add feature that the report requires. Sharon and Nassib talked about timing, mentioning that the labels of "Beta" etc. reflect the fact that the reporting project was so late in getting development resources, but that the work is progressing more quickly now. 

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
    • In the process of trying to secure regular access to test data.
  • LDP Report Working Group
    • Been in a holding pattern. VShah got good notes from Eric Pennington on data documentation and will remind folks that more input is needed. AZoss talked to CMalmborg at Chicago and reviewed clustering on RA reports.
  • LDP Data Privacy Working Group
    • VShah – several reports have been flagged which contain personal data. Need to be reviewed to see if they can be converted to in-app reports. Will tentatively be discussed on 7/29. IKuss mentioned that staff audit data will be a clear difference between European and US requirements with European requirements that many staff audit data cannot be retained. Example: how many items cataloged during specific period; this would never be a valid argument for retaining staff audit data. There can be a contractual agreement that certain specific staff audit data be maintained; it must then be maintained in perpetuity.
    • NNassar may be able to eliminate personal data from some reports in LDP; could delay inclusion of personal data to do software development needed to satisfy GDPR. Also feels some reports may have been mis-classified as LDP rather than in-app.
  • LDP SysOps Working Group
    • KWalker – no updates on LDP infrastructure at UA. Waiting for data to become available. SBeltaine – in the same position at Cornell.
  • Software development
    • dates on our epics assume that blocking dependencies on Folio will be worked out in the near future. 
    • we have worked around the API documentation issue to some extent, but we are still dependent on that as well as the incremental data issue both to be resolved.
  • Others?
Reporting FeaturesAll

This week, we will continue our review of the JIRA tickets for Reporting Features, gather more details and use cases, and work on prioritization. 


Stray Features

UXPROD-1100: CQL Support for Audit Module

UXPROD-358: Edge API for Acquisition Data Enhancement


LDP Open Feature Requests


First Pass START----------------------

UXPROD-1868: Allow HTTP request for results of report/query

UXPROD-1869: Ability to connect data warehouse to workflow engine for triggering reports based on logical conditions

UXPROD-1867: Build reports based on custom lists

UXPROD-1875: Build a FOLIO Data Dictionary for reporting

UXPROD-1864: Store Custom Fields from apps in LDP

UXPROD-1872: Exclude records that are suppressed in the catalog from reports

UXPROD-1863: Ability to report on data from MARC fields

UXPROD-1874: NCIP data format standards for reports

UXPROD-1870: SIP data format standards for reports

UXPROD-1865: LTI data format standards for course management systems for reports

First Pass END ----------------------


UXPROD-1866: Create a reporting dashboard with canned reports

UXPROD-1862: Use results of an LDP query to select items for batch edit in the FOLIO modules

UXPROD-1861: Document requirements and instructions for reporting applications to connect to LDP

UXPROD-1871: Ability to create local tables that translate (usually into a smaller number of catetories) values of a particular field (e.g., all of these 10 holdings locations translates to this particular library).

UXPROD-1873: Support for writing ad hoc reports


-where are issues related to eUsage prototype?

-one more....




Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 



Action items

  •  Reporting Data Privacy Group to flag reports that may have user data
  •  Reporting Data Privacy to follow up with Jesse, Tod, and Cate, and Chair-Elect to determine approach to audit trails in LDP
  •  Reporting Data Privacy to email the Reporting SIG to ask for feedback on which reports contain personal info Joyce Chapman

...