- Elizabeth Storrs after Vet cycle is done, migrate CAS/Liaison gender field to standard Gender Identity field; migrate CAS/Liaison sex field to gender marker
- create new marker and identity fields in TUH
- discuss next move with Dmitri
Resources
https://data.ucop.edu/files/documents/amcas-gender-identity-mapping-for-gad.pdf
| Expand | ||
|---|---|---|
| ||
In the current process in which we load to the staging area of SIS, regardless of any other data, if the SSN is found on a pre-existing record in SIS, the record will go to suspend status, and only when a user makes the determination that the new record is the same person as the pre-existing one will a match be made. So it wouldn’t matter if the student had a new gender, as long as the admissions user is able to figure out that it is indeed the same person. Open question: (asked, but unanswered) Under what circumstances does gender get overwritten in SIS or a new row created? Is a new gender row ever created? |
random note: in Slate, the delivered sex field is going to have a great deal of data in it, since we have been using it from the beginning . Merging newer records into older records may generate phantom values in this field, and we need to be very careful not to be using those values when they have not been maintained.
The required ‘legal sex’ v. optional ‘preferred gender’ in the CAS systems is a decent entry point to thinking about sex/gender as a core data point within the Tufts data ecosystem.
...
Summary sheet of all incoming admissions data: https://tufts.box.com/s/y1e60u11oob8gv2blbmoeljkzmo78y0b
Slate to SIS
This is mapped from the delivered, person-scoped Sex field in Slate.
To get data into that field,
at some point
Mapping from Slate Identity/Marker to Slate Sex for consumption by SIS:
Coalesce: Identity first, then Marker.
Male/M → Male
Female/F → Female
Transmasculine/Transman → Transgender
Transfeminine/Transwoman → Transgender
Prefer to Specify → Other
Non-binary → Nonbinary
Decline to State → blank
X → non-binary
text fields (”other” description) may be brought into Slate, but cannot go to SIS
...
Automated update of “sex” field within Slate
Create Scheduled Query SFTP Process
Using the work Helen did in TUSMGP as a model, there is now an automated query in Vet and in TUH that will update the delivered ‘sex’ value with a concatenated Identity/Marker value; the Assign Sex field for SIS interface queries are set to run between 2-4 pm to get the updates before data is pulled for SIS. If gender does not match withinThese run to the Trigger: Person - Sex source format.
When copying over the query, the ‘extended’ export value Helen had set in the concatenated sex export gets reset to “default”. The mapping existed for M and F, but NB value was not mapped anywhere. 12/2 Updated both the mapping, so NB flows correctly, but also updated the export values.
TUH Assign Sex field for SIS interface query was started on 11/27/2024.
12/2 reviewed imports and updated anyone with an NB value by hand on their application record, since it had not been mapped
In the applications we control, should we be asking for “other”, even if we cannot send that to SIS? Is it just performative? Elizabeth Storrs ask Hope!
SIS
Everything ultimately has to flow into SIS.
...
There are also user-defined options to capture pronouns and gender identity--these are updated manually.
...
Is not sent to Powerfaids or for Students to or from HR.