As a heads up for our next meeting, please take a look at the JIRA issues below. If you do not yet have an account for the FOLIO JIRA (issues.folio.org) please use the self-signup, which is available at: https://issues.folio.org/secure/Signup!default.jspa (this sign-up gets you into both the Confluence & JIRA).
Cate Boerema gave me the following links in the FOLIO Jira, which capture what Vince Bareau (EBSCO) has entered so far to support changes to Okapi and APIs, etc. to support the technical architecture development for a Data Lake. The two links below describe features, and you need to drill down within each one to see the user stories connected with the features.
https://issues.folio.org/brows
https://issues.folio.org/brows
It is important to note that these are effectively placeholders at this point in time. They are not yet categorized for the development timeline. I will review these with you in the Reporting SIG meeting next Monday, and we will need to prioritize them for development. As we have identified that External Reporting via a Data Lake/Warehouse/Store is the highest priority (over in-app reporting and other requirements), I expect the Reporting SIG will vote to slate this development for V1. Generally speaking FYI, Cate said that features are assumed to be part of V1 unless explicitly noted for "V2" in the JIRA ticket.
All the best,
Sharon
Sharon Beltaine
Applications Systems Analyst III
Cornell University Library
FOLIO Reporting SIG Convener