-
Notifications
You must be signed in to change notification settings - Fork 19
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
VHA ODS tables #13733
Labels
Eng: Data
Mark when data has been backfilled, or the issue has any data integrity concerns
Team: Delta 🔺
Milestone
Comments
pkarman
added
Eng: Data
Mark when data has been backfilled, or the issue has any data integrity concerns
Team: Delta 🔺
labels
Mar 18, 2020
va-bot
pushed a commit
that referenced
this issue
May 11, 2020
connects #13733 ### Description Adds a new ETL table `vha_decision_reviews`. The new table uses STI (single table inheritance) to coalesce Appeals, HLRs and SCs that all have a benefit type of `vha`. ### Acceptance Criteria - [x] Code compiles correctly ### Testing Plan 1. Deploy and watch ETL builder for errors. ### Code Documentation Updates - [x] Add or update code comments at the top of the class, module, and/or component. ### Database Changes *Only for Schema Changes* * [x] Timestamps (created_at, updated_at) for new tables * [x] Column comments updated * [x] Query profiling performed (eyeball Rails log, check bullet and fasterer output) * [x] Appropriate indexes added (especially for foreign keys, polymorphic columns, and unique constraints) * [x] DB schema docs updated with `make docs` * [ ] #appeals-schema notified with summary and link to this PR
in production just now:
|
For comparison:
|
va-bot
pushed a commit
that referenced
this issue
May 18, 2020
Resolves #13733 Follow-on PR to first PR #14208. ### Description Add ETL remand_reason table for VHA reporting needs. Pretty much a straight copy of original table. ### Acceptance Criteria - [x] Code compiles correctly ### Code Documentation Updates - [x] Add or update code comments at the top of the class, module, and/or component. ### Database Changes *Only for Schema Changes* * [x] Timestamps (created_at, updated_at) for new tables * [x] Column comments updated * [ ] Query profiling performed (eyeball Rails log, check bullet and fasterer output) * [x] Appropriate indexes added (especially for foreign keys, polymorphic columns, and unique constraints) * [x] DB schema docs updated with `make docs` * [x] #appeals-schema notified with summary and link to this PR
Email sent to stakeholders, scheduling time to review. |
va-bot
pushed a commit
that referenced
this issue
May 20, 2020
connects #13733 ### Description Rename table and models to drop `Vha` since the schema structure can be used for other lines of business. Adds an index on `decision_issues.benefit_type` in order to make it easier to query by line of business. ### Database Changes *Only for Schema Changes* * [ ] Timestamps (created_at, updated_at) for new tables * [x] Column comments updated * [ ] Query profiling performed (eyeball Rails log, check bullet and fasterer output) * [x] Appropriate indexes added (especially for foreign keys, polymorphic columns, and unique constraints) * [x] DB schema docs updated with `make docs` * [x] #appeals-schema notified with summary and link to this PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Eng: Data
Mark when data has been backfilled, or the issue has any data integrity concerns
Team: Delta 🔺
Description
VHA has reporting needs similar to those of VBA. These include tables:
In order to make it simple for VHA to pull the data they need, we need a new ODS table
vha_decision_reviews
that is scoped to those Decision Reviews (Appeal, HLR, SC) that have an associated benefit type corresponding to VHA.Acceptance criteria
vha_decision_reviews
ODS table with composite schema matching HLR, SC and Appeal.remand_reasons
ODS tableETL::VHADecisionReview
model and syncer added to builder jobTechnical notes
Easiest way to identify VHA-related decision reviews is via the BusinessLine to task association. See #13075 for example.
The text was updated successfully, but these errors were encountered: