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.
...
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.
...
Decline to State → blank
X → Indeterminate/Intersex/Unspecified was the original assumption about how to map this, but we are going the wrong way, percentage-wise---I think this should be non-binary, and then let people change to intersex if they want to. DIscuss with Helen on Wednesday!
text fields (”other” description) may be brought into Slate, but cannot go to SIS
...