/
Vision and Scope to Story Trace

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

Vision and Scope to Story Trace

Traced Stories

V&S#

Activity

Area

EPIC

Requirement

Jira

V&S#

Activity

Area

EPIC

Requirement

Jira

FEA01

Draft

Integration

https://sydneyuni.atlassian.net/browse/AVE-1

As ASR user, we need to understand why certain data are being overwritten by SITS integration so that we can avoid scenarios where a newer data is being reverted back to an older data

Note: 5 to 8 contact fields

Changes required on : All the integration needs to be assessed. (eg., Swift integration/connector and SITS integration)

  • somebody supplied updated email, changed it in Jarvis, SITS integration run again and wash out the supplied email. (Miranda can take a screenshot)

    This one is SITS overwriting first party data added to the system from a alumni updating their details through a ASR campaign. It's probably not students having a donor duplicate record but older alumni with donor duplicate record.

TASK:

All the integration needs to be assessed

Need discussion with each teams in TAP about Accounts and Contacts Structure (Gift admin, Plan giving (Alain, Harpreet, Demelza), Donor relations (Keri, Harriet), Events team (Miranda)

https://sydneyuni.atlassian.net/browse/AVE-99

https://sydneyuni.atlassian.net/browse/AVE-142

FEA02

Draft

Process

 

As ASR user, we need a standard procedure documentation for the following:

  • Understanding of where data is coming from and the validity of data before it is being overwritten manually or by integration

  • Clear definition of conditions of Matching records so that everyone is aligned on how to Match records.

  • Understanding of information requirement from GA team to avoid delays in processing

  • Understand and document the definition of friend so that we know if they are contactable or not

  • Validate if unsubscribe from Swift are brought back into Jarvis

  • We need standard procedure for linking a contact to an organization if the contact is an employee do we then create employment record (from Abe’s workshop). Some contacts linked to an account need to be linked as employment relationship apart from the contact to account relationship. We need set of guidelines where to put information which will give way to putting bells and whistles such as validation rules to ensure data are correctly inputted.

  • How are we recording prior names of a company (from Abe’s workshop). Similar to companies who are subsidiaries or trading as. At the moment they are creating accounts but not sure if they are necessarily linked together. If we are using Account Roles, we should locked the list so that people don’t put in rubbish values.

  • if we could have a system where we can have some flexibility on where we send our correspondence and not tied to just the primary or secondary contacts (i.e. receipt needs to go to a particular person at a particular address). Correspondence such as pledge reminders, event invitations, solicitations)

  • we need to pay a lot of attention to names that could lead to duplicate records (i.e. Jennifer as Jenny). Use preferred name and we need to define what name we use for the correspondence (check if there is flexibility on what name to use). For example Benjamin Newton

  • creating a contact and assigning them as the primary and secondary contact or two different processes, what will often find is that they are contacts on the account but they haven't actually been sent set as a primary or secondary contact.

  • activity reports in contact and account level, can we define this process more specifically. (Jess’s team use Activity rather than activity reports)

  • if a contact is updated (i.e. married) do we have a workflow that updates the account name as well? Issues arise for example when one updates contact and assumed that it updates the account as well. (applies to join, separate and decease as well)

https://sydneyuni.atlassian.net/browse/AVE-46

https://sydneyuni.atlassian.net/browse/AVE-117

https://sydneyuni.atlassian.net/browse/AVE-146

https://sydneyuni.atlassian.net/browse/AVE-149

https://sydneyuni.atlassian.net/browse/AVE-150

https://sydneyuni.atlassian.net/browse/AVE-151

https://sydneyuni.atlassian.net/browse/AVE-152

FEA03

Draft

AQ

 

  • As general user, we need understanding/clarity on the use of Account Type on account and why it is a required field but not in the account create screen

  • As general user, we need to understand the functionalities behind Primary and Secondary contacts so that we can build some workflows on it

  • As community giving user, we need just to focus on legal credit as opposed to high end donors

https://sydneyuni.atlassian.net/browse/AVE-68

FEA04

Draft

Data Integrity

 

  • As general user, we need to clean up data specially for corporations migrated from Advance where a dummy contact is attached but no primary contact is recorded so that the whole process does not fail specially on receipting.

  • As general user, we want to clean up and review data imported into Jarvis from Sensis and do the necessary so that they stay up to date.

  • As general user, we need to clean data so that there no relationship that don’t make sense such as a solicitor in a household account

  • receipting care of should be migrated into proper contacts

  • validate on accounts created for corporate contacts. Business rule on contacts that needs to be created as household accounts vis a vis their organization contact. (one of the things you could look at was any household types that maybe there's specified that contact type is a corporate contact or foundation contact or something that is not individual, education, student id if graduand)

https://sydneyuni.atlassian.net/browse/AVE-118

https://sydneyuni.atlassian.net/browse/AVE-119

https://sydneyuni.atlassian.net/browse/AVE-120

https://sydneyuni.atlassian.net/browse/AVE-87

https://sydneyuni.atlassian.net/browse/AVE-153

FEA05

Draft

Jarvis

 

  • As general user, we need to see soft credits on contacts instead of on accounts so that we can directly associate them when looking at the contact record. (@rommel.ngo need to understand Why? What is expected?) Need discussion with +Affinaquest.

  • As general user, we need efficiencies to be introduced on how to manage exclusion campaigns as they are quite challenging especially to newer staff member who are not familiar with the growing number of exclusion campaigns

  • As general user, we need to understand what each of the contact types are for and clean up the list sot that they are not ambiguous to users

  • As general user, we need more robust reports that take into consideration activities based on faculty and giving for instance so that we can better target our constituents

  • Adding secondary contact to an account does not ask for contact’s role to the account. (from Abe’s workshop)

  • we need a solution or a procedure to properly represent company hierarchy. i.e. Wespac Annex branches - National Branch, local branch, etc. (from Abe’s workshop)

  • people are forgetting to link a contact as primary or secondary contact (from Abe’s workshop)

  • we need to direct users in creating account and put validations to use the correct one for particular type of accounts being created (Account Create Utility). When adding new contact to an account, they are not necessarily aware of the legal credit and recognition credit percentages which causes issues down the track.

  • new accounts come in as leads and converted to new accounts/contact and there is an issue where they are automatically being created a s alumni

https://sydneyuni.atlassian.net/browse/AVE-18

https://sydneyuni.atlassian.net/browse/AVE-16

https://sydneyuni.atlassian.net/browse/AVE-32

https://sydneyuni.atlassian.net/browse/AVE-121

https://sydneyuni.atlassian.net/browse/AVE-122

https://sydneyuni.atlassian.net/browse/AVE-123

https://sydneyuni.atlassian.net/browse/AVE-125

https://sydneyuni.atlassian.net/browse/AVE-131

https://sydneyuni.atlassian.net/browse/AVE-147

https://sydneyuni.atlassian.net/browse/AVE-148

FEA06

Draft

Disconnected data

 

  • As ASR user, we need to understand how we can ingest data coming from faculties so that we can stay upto date

  • As ASR user, we need a way to manage updating RTS which is currently manual and tedious

https://sydneyuni.atlassian.net/browse/AVE-143

https://sydneyuni.atlassian.net/browse/AVE-144

FEA07

Draft

OGC

 

  • As ASR user, we need to laisse with OGC and establish Privacy statements so that we may reabsorb information from relevant sources.

https://sydneyuni.atlassian.net/browse/AVE-130

 

 

 

 

 

 

Related content

AVE-106 Phone Number and Email integrity
AVE-106 Phone Number and Email integrity
Read with this
AVE-37 Understand AS-IS process for Account/Contact creation
AVE-37 Understand AS-IS process for Account/Contact creation
More like this
Jarvis Data Dictionary / Business Rules
Jarvis Data Dictionary / Business Rules
Read with this
TAP Solution Slayers (TAPSS) - Team Space (to be archived)
TAP Solution Slayers (TAPSS) - Team Space (to be archived)
Read with this