This PR creates a dedicated view, crash_injury_metrics, whose purpose is to hold the authoritative crash injury metrics for all VZ reporting.
Testing
Despite what the diff says, the substantive changes here are all captured in these views.
At this point in time, I am am mostly looking for feedback on the view naming conventions. crashes_list and crash_injury_metrics. Are the names ok? Should they have the word view in the name? I guess it really isn't a big deal changes these further down the road....
URL to test: Local
Steps to test:
Follow the steps to start the data model collector branch and run the CRIS import ETL.
Start your local VZE and test the crashes list page by apply various filters and exporting data.
Ship list
[ ] Check migrations for any conflicts with latest migrations in master branch
[ ] Confirm Hasura role permissions for necessary access
Associated issues
This PR creates a dedicated view,
crash_injury_metrics, whose purpose is to hold the authoritative crash injury metrics for all VZ reporting.Testing
Despite what the diff says, the substantive changes here are all captured in these views.
At this point in time, I am am mostly looking for feedback on the view naming conventions.
crashes_listandcrash_injury_metrics. Are the names ok? Should they have the wordviewin the name? I guess it really isn't a big deal changes these further down the road....URL to test: Local
Steps to test:
Follow the steps to start the data model collector branch and run the CRIS import ETL.
Start your local VZE and test the crashes list page by apply various filters and exporting data.
Ship list