Vet Residency Data in PowerFaids Incorrectly

Box folder link https://tufts.box.com/s/d0ckxtskspuifnazuoflrfore1s9mjl9 contains email threads, SIS summary of recent Vet student residencies, and comparison of answers to residency questions in TUV.

Issue Description

From Elaine Collins, Re: New Question Samantha Fox “We are researching a student (1511570) who had two applications in Slate (they are in a joint DVM/MD-MPH program).  They should have been a PA resident but when I look at self reported residency data in SIS, I only see MA as the state of residency…..I only ever see MA being the value we sent from SIS to PF for this student. 

Open

VMCAS

Open

SIS

 

Permanent address was updated by student in SIS 7/3 to Pennsylvania, which updated the address in PF, but not the residency (which is acting like it should).

Troubleshooting/Research

As shown above, Pennsylvania is state of Legal Residence in VMCAS, and both Mailing and Permanent Addresses are in Massachusetts.

In VMCAS there are also the program questions used to confirm residency:

Open

in the application itself

All three of these fields are matched to individual Slate fields, but there is no built-in logic or double-checking, so we end up with data like this, where the three relevant fields do not match or are missing information.

Open

https://vet.admissions.tufts.edu/manage/query/query?id=e64534da-9ed5-4bdd-b1bb-14e2e7a96206

In SIS there are 4 separate groups of fields as part of Residency, but only two of them are used.

 

Open

data added through Z_RESIDENCY batch process, which runs weekly

 

 

Open

Kiran not finding how the Slate data gets in--Dmitri says coming from Slate, legal state then perm state, then mailing state

 

In PF the data looks like this:

Open

Just a single value, overwritten if it changes, but there is now an audit log.

2 aid years are sent at a time, 2023 and 2024 sent evening 9:30 and 10:30pm-ish into PF staging tables, which load into PF the following morning. It is possible to run the job ad hoc for a particular student to the staging table in PF, which is what we were doing for testing.

• the VT feed to SIS from Slate is currently using permanent address to populate the residency field

•  students cannot adjust the residency field

• Self-reported State Residency flows to VT State of Origin in PF

• changes made to the state of residency in SIS do not affect the State of Origin field in PF if the student is no longer in Admissions

Resolution Steps

Work with Dmitri to adjust what data he is pulling from the VMCAS application to be the application-scoped legal state of residence (legal_state).

Vet should review legal state of residency in comparison to the programmatic questions via https://vet.admissions.tufts.edu/manage/query/query?id=e64534da-9ed5-4bdd-b1bb-14e2e7a96206, and adjust the VMCAS legal state field as necessary. If any changes are made, Financial Aid must be informed in order to update PowerFaids. [Set this up as a deliver message, if I can…

9/30/2024

These 9 students in the 2025 Vet cycle have a disconnect:

Open

The only valid test cases are those where the permanent address state and the legal state are different--we are expecting/hoping for the legal state value.

Dakin, Lin, Naley, Fether-Hashimosto, and Rascona are the testing pool;

and it fails:

Open

Dakin should be Massachusetts, not Florida.

Outcome

Per Dmitri 12/11/2024, both Residency Offical1 and Self-reported legal state for Vet will match each other, and be based on the legal_state field in Vet. (rolls to Perm State and Mailing State if no Legal_state).