Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

For the 2024 cycle, 2 new application scoped fields were created in Slate:

image-20241001-152725.png

to capture the Legal Sex and Gender Identity fields in VMCAS Sex and Gender as a temporary holding pen.

This data was moved to the person-scoped fields on 10/1 (sex and gender 20241002-132730.xlsx), which are what are being used in the Slate hosted applications:

image-20241001-152647.png

The VMCAS mapping was updated to go directly to these fields/prompts on that same day (after the great majority of files have already come through, but there will still be a few to test on).

image-20241121-154627.png

Gender Marker Prompts: M, F, X, Decline to State

Gender Identity Prompts: Male, Female, Transmasculine/Transman, Transfeminine/Transwoman, Other, Non-binary, Decline to State

Gender Identity and Gender Marker cannot flow to Slate as they are until the fields in SIS and the feed (whether through Denodo or Kafka) includes them. Sex currently flows, so it seems least disruptive to continue to populate that field based on Marker and Identity data, then have students confirm their data upon matriculation. For more details on that project see [].

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 → Indeterminate/Intersex/Unspecified

text fields (”other” description) may be brought into Slate, but cannot go to SIS


Automated update of “sex” field within Slate

TUP Transition Gender Fields

Create Scheduled Query SFTP Process

Using the work Helen did in TUSMGP as a model, there is now an automated query in Vet that will update the delivered ‘sex’ value with a concatenated Identity/Marker value. The DVM cycle is over, but this is working on data from the Slate-hosted applications, which are asking for Marker and Identity.

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!

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.