Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Resolve Data Discrepancy Between MATERIALWEAKNESS and is_internal_control_material_weakness_disclosed Fields #4529

Open
sambodeme opened this issue Dec 11, 2024 · 1 comment
Open

Resolve Data Discrepancy Between MATERIALWEAKNESS and is_internal_control_material_weakness_disclosed Fields #4529

sambodeme opened this issue Dec 11, 2024 · 1 comment
Labels
curation Candidate for data curation eng

Comments

@sambodeme
Copy link
Contributor

Description

The FAC received a helpdesk ticket reporting a data discrepancy between the legacy system and the new system concerning the fields is_internal_control_material_weakness_disclosed and MATERIALWEAKNESS.

According to the published data dictionary, the MATERIALWEAKNESS field in the legacy database should map to is_internal_control_material_weakness_disclosed in the new database. However, during data migration, the algorithm used MATERIALWEAKNESS_MP instead, causing a data inconsistency.

This issue must be addressed as part of the ongoing data curation efforts to ensure accurate field mapping and data integrity.
@sambodeme sambodeme added eng curation Candidate for data curation labels Dec 11, 2024
@github-project-automation github-project-automation bot moved this to Triage in FAC Dec 11, 2024
@sambodeme
Copy link
Contributor Author

Adding related ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
curation Candidate for data curation eng
Projects
FAC
Status: Triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sambodeme