Skip to content

Update Research Export demographics tab to 2026 HUD Data Standards - #6489

Draft
dtgreiner wants to merge 3 commits into
mainfrom
dg-offline-research-export-ds-updates
Draft

Update Research Export demographics tab to 2026 HUD Data Standards#6489
dtgreiner wants to merge 3 commits into
mainfrom
dg-offline-research-export-ds-updates

Conversation

@dtgreiner

@dtgreiner dtgreiner commented May 19, 2026

Copy link
Copy Markdown
Contributor

Merging this PR

  • use the squash-merge strategy for PRs targeting a release-X branch
  • use a merge-commit or rebase strategy for PRs targeting the stable branch

Description

Updates the Demographics tab of the Offline Research Export to align with 2026 HUD Data Standards: gender columns are upgraded from the retired legacy format to the current 2026 multi-select fields (Woman, Man, NonBinary, etc.), a new Sex column (HUD 4.21) is added between gender and race, race columns are upgraded to 2026 format which includes Hispanic/Latina/o and Middle Eastern or North African as first-class race fields, and the standalone Ethnicity column is removed since Hispanic/Latino identity is now captured within the race fields. The "Doesn't know, prefers not to answer, or not collected" race column now displays the specific reason rather than a Yes/No flag.

Type of change

New feature

Checklist before requesting review

  • I have performed a self-review of my code
  • I have run the code that is being changed under ideal conditions, and it doesn't fail
  • If adding a new endpoint / exposing data in a new way, I have:
    • ensured the API can't leak data from other data sources
    • ensured this does not introduce N+1s
    • ensured permissions and visibility checks are performed in the right places
  • Any major architectural changes are supported by an approved ADR (Architectural Decision Record)
  • I have updated the documentation (or not applicable)
  • I have added spec tests (or not applicable)
  • I have provided testing instructions in this PR or the related issue (or not applicable)

//: # NOTE: system tests may fail if there is no branch on the hmis-frontend that matches the Source or Target branch of this PR. This is expected

@dtgreiner
dtgreiner requested a review from eanders May 19, 2026 18:48
'Warehouse ID',
'Reporting Age', # NOTE: this is age at the latter of report start or entry
]
# TODO: DEPRECATED_FY2024 This needs to be updated in the receiving system before we update here

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a TX specific report, did we confirm the receiving system is set to handle FY2026?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed reading the rest of that part, I'll follow up with Danielle & Mary Ann.

@eanders eanders left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dtgreiner just one comment inline. I haven't been following the request, so want to make sure we've connected all the right parties or determined this isn't used in the original way, before we merge this change.

@dtgreiner
dtgreiner marked this pull request as draft May 20, 2026 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants