Date
...
| Item | Who | Notes | |||
|---|---|---|---|---|---|
| Attendance | Sharon | Today's Attendance Taker: Today's notetaker: Last week's notetaker: Anne Highsmith | |||
| Updates from Various Reporting Related Groups and Efforts | Various | 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:
| |||
| Update on Reporting Issue Blockers | Nassib | We will review reporting issues in JIRA that are blocking progress on the completion of our Epics. After reviewing the details of these issues, we will discuss the potential impact on our FOLIO deliverables. Blockers: UXPROD-1438: Process for tracking data-related API schema changes UXPROD-1431: Data attributes needed for reporting UXPROD-1414: Complete documentation of data attributes in module APIs FOLIO-1839: Enable incremental requests for all records since last request | Concerns over Limited Resources for LDP development | Ingolf | Ingolf Kuss : Need to discuss Reporting and SysOps Integrations in the SysOps SIG. SysOps SIG sees a huge gap and very limited resources for building the LDP. Questions: How to build up the data flow to the LDP ? Lead time is 6 month to build this, then testing and training must start. If it's not in the Jan 2020 release, institutions like TAMU, Lehigh and Chicago will have to change their whole timeline. Also, unit tests must catch schema changes in the underlying modules. |
| Reporting Features | All | This week, we will continue our review of the JIRA tickets for Reporting Features, gather more details and use cases, and work on prioritization. (Reporting features are different from reports in that they involve reporting functionality, not an actual report.) Reporting features now carry the ldp-platform label in JIRA. 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 UXPROD-1866: Create an LDP 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 First Pass END ---------------------- 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.... | |||
| Topics for Future Meetings | All | Review and update Topics for Future Reporting SIG Meetings |
...