Today's note-takers: Team Leads for project updates
Announcements / Reminders
Fundamentals of the FOLIO Community (June 30 at 11am Eastern U.S. time)
This webinar is the first in a new series of onboarding videos for community members. It will cover topics such as FOLIO’s governance structure and the relationship between libraries, vendors, and developers, user-experience design, and the FOLIO Code of Conduct.
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.
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.
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.
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.
Request for feedback: Documentation of mod-users data attributes
Maybe consider GitHub actions to run scripts nightly, send alerts?
Bring up in a dev meeting to explore possibilities
Noticing any problems with the data integrity?
example problem with communication between FOLIO apps - if you delete a PO line, the agreements don't get updated
App Interaction SIG has a channel on Slack, so can share information with them (#appinteraction)
Orders talks to Inventory, but Inventory doesn't talk back to Orders, so changes in Inventory don't get reflected back in the orders
Updates and Query Demonstrations from Various Reporting Related Groups and Efforts
Community & Coordination, Reporting Subgroup Leads
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
Progress on Patron List, maybe ready for review this week
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
Reviewed all of the feedback, planned out changes, and will incorporate this week
Over the next few months, Reporting SIG Documentation Subgroup will be helping to build end-user documentation for https://docs.folio.org/docs/ (much will be linking to existing documentation over on GitHub)