113, 119, 125, 127, 218, 219, 220, 221 Modify the Staging-to-RDS migration for the dimension table changes

[lizbrunet]

In https://aemcorp.atlassian.net/browse/CIID-7861 we modified the N or D dimesnion table, DimNorDStatuses. We need to update Staging.Staging-to-FactK122StudentCounts_NeglectedOrDelinquent and any related views to incorporate those changes. Some of these file specifications are processed through the Assessment fact type but we need to ensure that they are updated to the new dimension model as well.

Acceptance Criteria

Setup: N/A

QA: Run the N or D migrations and verify that data is making it through for each of the file specs (if the dev for them is completed)

Testing proof: add a screenshot of the page that passed testing to the ticket as the work is completed.

Migration Steps:

Ex.) RDS - App.Wrapper_Migrate_NeglectedOrDelinquent_to_RDS

Ex.) Reports - 119, 127, 218, 219, 220, 221 (the single screen should take care of this but 119 and 127 still use Get_CountSQL while the 200’s use the new report migration process.

Test Cases: does this require an update to the test case(s)? Y/N: No

Documentation - does this require an update to documentation (GitBook edits)? Yes/No

Release Notes? (Add language for Release Notes) We updated the DimNorDStatuses dimension table to CEDS 13 and also to make it more efficient. We updated the migrations for N or D to incorporate those changes involving that dimension table.

OSC Impact - does any part of this task require an OSC ticket?

If yes, once the OSC ticket is created, add the OSC ticket # to the JIRA ticket.

ETL Checklist Impact - does any part of this task require an update to the ETL Checklist (i.e., were changes made to the database tables or columns)?