Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
AVE-16 Contact Types
- Approve Cleanup
Contact Type and Secondary Contact Type
The Contact Type and Secondary Contact Type fields are TAP’s way to identify a Contact’s relationship or relationships with the Uni. There is a hierarchy of the Contact Type and Secondary Contact Type fields to enable reporting efficiency.
The Contact Type field is mandatory because for someone to be in Jarvis, they will have some sort of relationship with the University. The values for this field have been refined as part of the Avengers release, which has been delayed due to the WB release. The new values have been documented on this Confluence page and still includes values like Alumni, Donor, Staff, and Student. It’s worth noting that there are some values that conflict eg Staff and Former Staff or Student and Graduand, there is future work required to confirm whether conflicting values can exist on the same contact at the same time (ticket to be created).
The Secondary Contact Type will only be populated if someone already has a value populated in the Contact Type field. The Secondary Contact Type isn’t a mandatory field because some Contacts will only have one relationship with the Uni eg they are an Alumni but not a Student, or a Donor as well.
Contact Type and Secondary Contact Type Hierarchy
There is a hierarchy to the Contact Type and Secondary Contact Type to enable consistency from a data quality and consistency perspective. This hierarchy is documented on this Confluence page. See the Agreed Contact Types table which lists the Contact Type under the Primary column and the associated Secondary Contact Type values in the Secondary column. This hierarchy was developed as part of the Avengers project which focused on creating consistent data.
NB: there are no flows or automation that automatically maintains the hierarchy. The hierarchy is manually cleaned and updated by TAP data stewards. There are future plans by TAP to look at what system tools can handle this (ticket to be created).
Changes History
Date | Change | Comments |
---|---|---|
Sep 16, 2022 | Remove “Patient” as a Primary Contact Type | Remove and replace with specific primary contract type based on individual circumstances. If not any of the above then friend - also added to grateful patient category - ** Automatic tag: “Do not contact” |
Sep 16, 2022 | Remove “Parent of Student - Alumni” as a Primary Contact Type | Make a secondary contact type of all Primary contact types |
Sep 19, 2022 | Leave “Alumni Affiliate” | To be reviewed at a later date - for now please leave Alumni Affiliate as a primary contact type. |
Sep 23, 2022 | “Alumni Affiliate” added as Secondary Contact Type | To Donor, Staff or Former Staff, Organisation Contact |
Sep 28, 2022 | Split of Staff or Former Staff and Student or Graduand |
|
Agreed Contact Types
| Primary | Secondary (None or any of the types) | Comments |
|
---|---|---|---|---|
| Alumni | Donor Staff Former Staff Graduand Student Organisation Contact Parent of Student - Alumni | (Student- for SINGL we might be tracking Alumni who is again studying) |
|
| Donor | Staff Former Staff Graduand Student Organisation Contact Parent of Student - Alumni Alumni Affiliate | Alumni Affiliate studied at various institutions that Sydney Uni acquired over the years. |
|
| Staff | Graduand Student Organisation Contact Parent of Student - Alumni Alumni Affiliate |
|
|
| Former Staff | Graduand Student Organisation Contact Parent of Student - Alumni Alumni Affiliate |
|
|
| Student | Graduand Organisation Contact Parent of Student - Alumni |
|
|
| Graduand | Organisation Contact Parent of Student - Alumni |
|
|
| Organisation Contact | Parent of Student - Alumni Alumni Affiliate |
|
|
| Friend | Parent of Student - Alumni |
|
|
| Alumni Affiliate | Parent of Student - Alumni |
|
|
|
|
|
|
|
Gift Driver flow might need updating based on changed in Contact Types. Attached herewith is a diagram that Sakshi has done: