TUP Transition Gender Fields

Slate Instance

TUP

Requestor

 

Date

11/1/2024

Status

in progress

Summary Description

Update all TUSMGP applications to use new gender fields (Gender Marker and Gender Identity), clean up old fields, and set up process to assign ‘sex’ field value for SIS integration.

External Documentation

TechConnect Ticket

 

Box Folder

 

Desired Deliverable

Fully transition TUSMGP instance of Slate to use the new sex/gender fields in compliance with the updated University guidance:

Gender Identity (F, M, Tm, Tf, NB, Self-describe/Other, decline to state) - personal identification

Gender Marker (F, M, X, decline to state) - legal/government sex

Update person records in Slate with value in ‘sex’ field that were created >= 1/1/2019

Research

 

Testing Plan

Scheduled Query SFTP

Configuration Documentation

Test Record

Name

Existing Sex

Gender Identity

Gender Marker

New Sex Value

Outcome

Test Record

Name

Existing Sex

Gender Identity

Gender Marker

New Sex Value

Outcome

382594415

Alexander

Male

Transmasc

Male

Trans

No change, check results

046775272

Kopparapu

NULL

Non-Binary

Female

Non-Binary

SUCCESS

873285283

Usmanov

NULL

Male

Male

Male

SUCCESS

196566765

Moore

Female

NULL

Male

Male

SUCCESS

572315219

Kancharla

Intersex

NULL

Female

Female

SUCCESS

053415240

Gangaram

Female

Female

Female

N/A (should not come up in results)

SUCCESS

374485151

Cheung

Non-Binary

Non-Binary

Female

N/A (should not come up in results)

SUCCESS

 

image-20241115-164146.png
Before export/import ran
image-20241115-164213.png
After first test

Issue with Alexander not updating is because the query to generate the list is exporting a different value than expected for the gender_identity prompt. Instead of ‘Transmasculine/Transman’ it exported the short value, which is just ‘transmale.' Because of this, it was not mapped properly in the source format and did not update.

To resolve, I’m updating the query in PROD to export specifically ‘long value’ to get the expected prompts.

Outcome

 

Update the Slate-hosted applications with these new questions,
Update the CAS source formats to map to these new fields,
CASPA In Progress
CASPA Application
SOPHAS In Progress
SOPHAS Application
PTCAS In Progress
PTCAS Application
"Back-fill" the new fields with the information we have been collecting (which is mostly in the 'sex' field but I've created other custom fields to store similar info when we first got it from the CAS applications) --this is necessary for the Denodo integration to ensure we are sending sex/gender data about prior applicants.
Deprecate/remove the custom gender fields we have currently that aren't needed now that we have this policy
Set up a process to update the existing 'sex' field with SIS-compatible data for the admissions interface