| Attendance & Notes | Angela | Attendance & Notes - Today's attendance-taker: Linda Miller
- Today's note-takers: Team Leads for project updates
|
Announcements /
Reminders | Angela | Recruiting New Query Developers - The Reporting SIG is always on the look-out for new query developers. Please let us know if you are interested in doing query development or if there are others at your institution who might be a good fit.
Test Data FOLIO Reporting developers and Reporting SIG members are encouraged to use this new page to share test data cases they have entered into FOLIO reference environments to keep us all aware of what data to expect when we test our queries.
Cluster Ranking New Report Clusters are added on a regular basis, so it is important to make sure your institution is reviewing these clusters and ranking them to establish report development priorities. If you rank reports for your institution, please follow the instructions below. If someone else ranks, please pass this information along to that person so your institution's vote can be included. - Action =>> Please review Reporting SIG-All Report Clusters (57 issues) in JIRA and RANK each report cluster for your institution (R1-R5)
- For reporting, institutions only need to rank the UXPROD Report Cluster JIRA issues. All reporting requirements, which are captured in REP-XXX issues, roll up to the UXPROD Report Clusters. Report clusters cover one or more report (REP-XXX issue) requirements.
Changing Meeting Time (forward one hour)? - Seems okay, will stay in touch
- won't do next week because of speaker, but maybe by August 2
|
| Discussion: inclusion of LDP app in FOLIO release | All | Update: LDP app will not be included in FOLIO Juniper release. Discussion: does the reporting community want the LDP app to be included in FOLIO releases? - when you put an app in the release, you are committing FOLIO project resources. FOLIO the project thus takes on responsibility for the maintenance of the app. a barrier to entry for that kind of commitment makes sense. we have some modules where the original implementation team has departed, and we have to be careful about orphaned code. There is a reason to be cautious. It would be nice to have it all included, but it is a commitment on the part of the project, and the code itself doesn't necessarily come with resources.
- the process needs to be clearly documented so that organizations that want to include something, they know what hoops they'll need to jump through. we should push that up through the new governance system. if there are barriers being put up, we need to see clear documentation.
- should there be a cost-benefit analysis of how useful this is going to be?
- in-app reports from different FOLIO modules? those are developed by the app developers
- for FOLIO app, might want to state the dependencies; eHoldings app works exclusively with EBSCO, so LDP app is similar in that it requires the LDP
- costs to including LDP app in release:
- FOLIO has costs of maintaining and kind of certifying the code
- LDP app developers have to cost to conform to process
- hosting provider could refuse to support LDP app
- costs to not including LDP app in release:
- miss out on some of the testing in bugfest, etc.
- FOLIO ships without any kind of central reporting solution (though, of course, dependent on having an LDP)
- local admins have to go through the process of installing the app separately from FOLIO
- integration of the apps gets transferred to the hosting provider or local admins (but same is true for the LDP - maybe the strongest argument for not bundling in FOLIO release?)
- the hosting provider could refuse to support LDP app, or could price institutions out of LDP hosting
- benefits of including in LDP app?
- helps reinforce the idea that many reporting solutions can co-exist in FOLIO ecosystem
- may pave the way for other external apps to be brought into the fold (there may be other similar integrations, like Caiasoft)
- might be nice to have a reporting portal app that points to various FOLIO reporting options, including LDP app and in-app reports, and that might be easier if LDP app is in release
- LDP app is tied to LDP as requirement, but perhaps the app could eventually have a wider scope to include other sources (maybe query builder could query FOLIO APIs directly)
- API querying still doesn't allow joins/cross-app querying
- having the app included is perhaps good advertising for the LDP
- having the app included could be seen as a vote of confidence/community support and allow for arguing for continued/increased developer resources
- reporting has been under-supported, and this app is going to directly assist reporting
- this app is filling a huge gap for non-SQL reporting for libraries
- if this is true, this would be big, because upcoming features in LDP app make it much more likely that people will feel comfortable using the LDP app for reporting because they won't have to learn SQL
- already have institutions that are disappointed that it won't be included in Juniper
- would benefit from bugfest testing
- benefits of not including app in FOLIO release
- not beholden a release workflow that is poorly documented
- if we go through with it, we have to argue for transparency and work this through the governance structure, will likely be a lot of time and effort
- being decoupled from release cycle means we can release whenever we want
- wouldn't have to use the FOLIO infrastructure (e.g., JIRA)
- perhaps more consistent with LDP as independent from FOLIO
- difficulty trying to conform to both FOLIO and ReShare requirements
- right now, FOLIO is still under development; if something changes in schemas from FOLIO database, the LDP app could have errors when trying to run a report
- but maybe it's a bit better if we can stay in tune with FOLIO app release cycle, at least in report development and maybe also LDP platform development
- just because we don't include now doesn't mean we couldn't add it later; maybe a bit harder to include now and remove later
- What would we ultimately like to accomplish?
- make the LDP and LDP app available in a way that is easy to be included
- testing the LDP as an integration with FOLIO
- increased visibility and support for LDP development
- In favor of inclusion: almost everyone, maybe around 10-11, maybe more, a few abstentions/on the fence
|
| Update LDP implementers grid | All | FOLIO LDP1-based Reporting First Implementers Grid |
| Updates and Query Demonstrations from Various Reporting Related Groups and Efforts | Community & Coordination, Reporting Subgroup Leads | Project updates Reporting development is using small subgroups to address priorities and complete work on report queries. Each week, these groups will share reports/queries with the Reporting SIG. Reporting development team leads are encouraged to enter a summary of their work group activities below. RA/UM Working Group - A lot of review last week, gave some feedback on various questions and made some plans for query updates
- Will hold off on additional queries to finish up query updates and documentation
- May have another SME joining the team meetings (Eliana!)
- Context
MM Working Group - The group is still on pause. Our meetings will reconvene Aug. 3, from 12-1pm ET via zoom.
- We are still waiting for the duplicate orders and OCLC synchronization reports. When we reconvene, we will look at our derived reports and discuss the implications of recent changes such as the new data model from the bound-with part 2 work that was released with Juniper.
ERM Working Group
RM Working Group - a fund distributed invoice line even when paid does not show every fund distribution row in the transactions table (in the Finance application); this may be a local setup issue...
- several queries for RM completed, but still need documentation, testing, and review
- working on queries for the 1.2 FOLIO Analytics release
- for latest updates, see RM Prototype and Query Development Status
- Friday the RM SIG proposed a new organization; ERM would be raised to level of SIG, and RM would join Acquisitions group to form an Acquisitions SIG, also elevate Open Access group to a SIG
Reporting SIG Documentation Subgroup - No changes
- Additional Context
External Statistics Working Group - no updates currently
- ACRL query set included in FOLIO-Analytics 1.1 release
- 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 clusters
For all recent work on FOLIO Reporting SQL development:
|
| Topics for Future Meetings | All | - Alternate FOLIO reporting systems
Google Sheets add-on (June 14)- ByWater system (July 26)
- Follow-up on MARC status, Quickmarc/Data Import conflicts
- How to strengthen connections to SIGs and their developers to be kept in the loop about changes to the data model
- Show and tell
- how are institutions using the LDP
- examples of using the local schema
- Cornell's report ticketing system
- Rollout plans from institutions
- Ask someone on the sysadmin side to talk about LDP administration (Jason Root?)
- Training topics
- adding test data in FOLIO snapshot
- How to do ad hoc querying with the derived tables
- How to use the LDP app
- using KNIME to build reports
- use of local schema for custom tables
- more on MARC
- using different applications (other than DBeaver)
- Postman for API queries, also Insomnia
- Upcoming:
- 16 August: presentation from ERM group on metadb/ERM
Review and update Topics for Future Reporting SIG Meetings
|
|
|
|