File Specification Number and Name
None
What Happened?
During the code cleanup we did in a recent release to align views, functions, SPs, etc.. to the Fact Type names we renamed the Assessment views to use the singular ASSESSMENT but the removal of the old version that used the plural did not happen. That needs to be removed to avoid confusion.
Also from that cleanup, we missed renaming the Source-to-Staging script to the singular, Source-to-Staging_Assessment but it was updated in the DataMigrationTasks table creating a mismatch between what exists in the DB and what is called when the auto-migration coide is executed.
Acceptance Criteria
• Current Behavior: The Source-to-Staging SP name and what is called from DataMigrationTasks do not align. 2 versions of the assessment views exist
• Expected Behavior: Cleanup the name and removed the deprecated view
• OSC Ticket: N/A
Documentation
• Release Notes: Completed the cleanup of the stored procedure and view names to use the Fact Type name for consistency throughout the migration process
• Other GitBook Documentation: On the Fact Type page - https://center-for-the-integration-of-id.gitbook.io/generate-documentation/developer-guides/migration/fact-type-table/assessment-fact-type in section ‘2.Staging’ we need to change references to the Source-to-Staging stored procedure to drop the final 's' in Assessments. All the refernces should be
[Source].[Source-to-Staging_Assessment].
• ETL Checklist Impact: N/A
Testing
• Requires updating of Test Case(s) or Create Test Case if it doesn't exist
• Create appropriate test data in Hydrate
• Include a screenshot of the corrected file to confirm test results.
Steps to Reproduce
No response
Version
No response
Logs or Error Output
Priority
Medium
Code of Conduct
File Specification Number and Name
None
What Happened?
During the code cleanup we did in a recent release to align views, functions, SPs, etc.. to the Fact Type names we renamed the Assessment views to use the singular ASSESSMENT but the removal of the old version that used the plural did not happen. That needs to be removed to avoid confusion.
Also from that cleanup, we missed renaming the Source-to-Staging script to the singular, Source-to-Staging_Assessment but it was updated in the DataMigrationTasks table creating a mismatch between what exists in the DB and what is called when the auto-migration coide is executed.
Acceptance Criteria
• Current Behavior: The Source-to-Staging SP name and what is called from DataMigrationTasks do not align. 2 versions of the assessment views exist
• Expected Behavior: Cleanup the name and removed the deprecated view
• OSC Ticket: N/A
Documentation
• Release Notes: Completed the cleanup of the stored procedure and view names to use the Fact Type name for consistency throughout the migration process
• Other GitBook Documentation: On the Fact Type page - https://center-for-the-integration-of-id.gitbook.io/generate-documentation/developer-guides/migration/fact-type-table/assessment-fact-type in section ‘2.Staging’ we need to change references to the Source-to-Staging stored procedure to drop the final 's' in Assessments. All the refernces should be
[Source].[Source-to-Staging_Assessment].
• ETL Checklist Impact: N/A
Testing
• Requires updating of Test Case(s) or Create Test Case if it doesn't exist
• Create appropriate test data in Hydrate
• Include a screenshot of the corrected file to confirm test results.
Steps to Reproduce
No response
Version
No response
Logs or Error Output
Priority
Medium
Code of Conduct