-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supply Data to FOM Business Team - manual extract #713
Comments
I see maybe a data model updates to capture these metrics? and something like Metabase? ie like the Optimize Team - https://iitco-metabase.apps.silver.devops.gov.bc.ca/browse/2 (or PSU, Mines, and other teams use for an easy analytics dashboard on top of postgres.. |
Preliminary query, work in progress... SELECT FROM |
Latest version of query, probably pretty close: |
To get the extract - start openshift command line, establish port fowarding e.g. Then use pg-admin to connect to database (e.g. localhost:6000), run query and save results to file. |
The FOM business team is requesting access to FOM data, including standard FOM attributes, comment count statistics, and spatial object statistics. This data is needed by late January at the latest for a short-term need, and is likely needed on a quarterly basis going forward. The primary immediate business purpose of this data is to help respond to questions about the reported lack of public comments for some FOMs.
Multiple solutions are possible. For this ticket, we're looking at doing some sort of manual data extract in CSV format to meet their immediate needs and validate that we are providing the right data. In a subsequent ticket we can look at providing a longer-term solution (*)
Data attributes/statistics required (**):
The business also asked for additional attributes (like type of tenure, something like that) that appear to be available in FSPTS, but isn't available in FOM. So for this we're just planning to provide the FSP ID of each FOM, and the business will need to join with FSPTS data to get these other fields.
(*) Longer-term solutions could include allowing business to pull a data extract via the FOM API, or to email out an extract periodically to the business, or more fancy building a BI / analytics environment that users can access.
(**) We will likely provide other attributes that are easy to provide, like FOM ID, created date, comment open/close date, etc.
The text was updated successfully, but these errors were encountered: