First presentation of LDP road map | Nassib | - Considerations:
- Many reports have been ranked by institutions for "go live (MVP)".
- LDP critical dependencies on FOLIO core development which have been requested and flagged as critical beginning in late 2018 will likely not be addressed until mid-2020 or beyond, based on discussions with the FOLIO capacity planning and project management groups.
- FOLIO is requesting that "go live (MVP)" features be ready by January 2020, to be released in Summer 2020.
- Future developer resources appear to continue to be roughly around 1 FTE on average, consisting of several part-time developers.
- LDP road map is based on these considerations, and aims to release features according to FOLIO's projected time lines for addressing critical dependencies as well as available developer resources.
- For "go live (MVP)":
- LDP will support ad hoc, cross-domain queries for all, or a very large proportion, of FOLIO data. We would ask this working group to help us determine, in the near future, the definition of "all FOLIO data" required for inclusion in the LDP.
- The LDP developers and this working group will aim to implement all reports requested for "go live (MVP)" if possible.
- Historical data will be retained in the LDP but not transformed into a single schema.
- Report queries at "go live (MVP)":
- Queries can be written using relational attributes when using the most common attributes (e.g.
loans.loanDate ), but will require JSON paths to access nested attributes (e.g. json_extract_path_text(loans.data, 'status', 'name') which refers to the "name" subfield located within the "status" field). - In other words, a set of "common" attributes will be available as relational attributes, while other attributes will have to be retrieved from JSON data (in the same table) using the
json_extract_path_text() function. - The usage takes the form
json_extract_path_text(A, F1, F2, ...) where A is the attribute containing the JSON data, and F1, F2, ... is a list of up to five nested JSON fields which specifies a path into the JSON data. - The JSON data include the complete set of data provided by FOLIO, while the relational attributes are created as a convenience to make writing queries easier.
- Historical queries within a single schema, ETL, and star schema are features planned for later releases of the LDP but are dependent on the identified critical dependencies and availability of developer resources.
|
Next Reporting Data Models to Deliver | All | Shall we build these reporting data models next? - Circ Item Detail at https://wiki.folio.org/display/RPT/Circulation+Item+Detail+Report+Prototype
- Services Usage at https://wiki.folio.org/display/RPT/Services+Usage+Report+Prototype
- Shelf List Location at https://wiki.folio.org/display/RPT/Shelf+List+Location+Report+Prototype
Questions: - What do RPWG members think of these (above) as our current highest priorities?
- Would the prototype developers like to develop the SQL queries for each of these?
| Using GitHub for developing SQL report queries | Nassib | Demonstration of how to contribute a new SQL report query--or a modification of an existing query--using the shared community space in GitHub that has been set up for this purpose. Refer to Contributing report queries to ldp-analytics for written instructions. |