Duplicates

In some instances users may find multiple versions of the same attendee profile have been added to their Upshot account, this should be avoided for reporting purposes. Only one version of each attendee is needed on Upshot, as this attendee can then be added to all areas of the system.

This guide explains how the built-in duplicate checker works, give some additional tips on how to prevent duplicates in the first instance and how to resolve the issue if users find duplicates on their account.


Duplicate checker

Upshot has an inbuilt duplicate checker that can flag up potential duplicates when new attendees are added or existing attendee profiles are updated.

The starting point for this is cross-referencing the First name or Nickname and Gender of an attendee. This is why these fields are required by default and cannot be changed. This minimum amount of information is needed as a starting point to allow the system to flag potential duplicates for you. 

Note that Gender does provide the option of prefer not to say and not provided

The duplicate checker also looks across the following Upshot default fields - D/O/B, Postcode, Email and Mobile number. 

These criteria will be queried if this data is provided for both attendees. For example, a potential duplicate will be highlighted if another attendee is found that:

  • Has the same first name or nickname
  • And has the same last name (if they have one)
  • And has the same Gender
  • And has the same postcode or DoB or email or mobile
  • And has the same postcode and DoB (when both used)

It is important to appreciate that the absence of some of the above data on one of the profiles or the potential for human error in terms of spelling or replicating the information off a paper registration form onto the system can cause the duplicate checker to not recognise potential duplicate profiles.

To avoid instances of this an effective starting point before adding any new attendee either via inputting the information off a paper registration form or the external attendee sign up form can be using the  search bar in the top right-hand corner of the account to see if the attendee already exists. 

Note that any custom data fields are not used in the duplicate checker process. 

Duplicate Warning

If the system recognises that this attendee may be a potential duplicate it will bring up one of the following two messages, dependent on the method of adding this attendee profile.

If the attendee is being added through People > Add new the following message will appear.

Please ensure you check the profile highlighted before clicking Continue to add this new profile to the system. 

If potential duplicates are flagged on the Attendee sign up waiting list they will be marked with a red exclamation mark.

If users click on the red exclamation mark next to the attendee's name this can allow them to see this attendee's information alongside the existing attendee's on the account, which can be helpful to determine whether or not this truly is a duplicate.


Tips to help prevent duplicates

The first step is to ensure all users at your organisation understand the importance of not having duplicates on your Upshot account and recognising what the above duplicate checker notifications mean. Having all users aware and engaged in this process can be a really effective step in stopping additional duplicates being added to the account. 

As mentioned earlier if this does seem to be an issue for your organisation an effective starting point before adding any new attendee can be using the search bar in the top right-hand corner of the account to see if the attendee already exists, this will avoid issues with any instances where the duplicate checker has been unable to recognise potential duplicates. 

Note: Within the search bar, the ordering of names is determined by: First Name, then Last Name, then Nickname, then ID. If a First Name, Last Name and Nickname all match then the most recently created attendee will appear first in the search bar.

Following on from this the most common example of why duplicate profiles exist come from a lack of data on the attendee profiles. Minimal information on attendees does not allow the system or users to recognise that two profiles are necessarily the same individual. 

This may be caused by organisations receiving partially completed registration forms or users looking to add new attendees to Upshot quickly and so only inputting minimal information about them. 

To avoid this it is recommended organisations look to make more fields on their registration form required. This can be done by a System Admin under the data display options. This can help to ensure that certain information is collected on participants, helpful for consistency in your reporting later, but also ensure that the system has more fields to check for potential duplicates and that users cannot enter very limited information when adding attendees.

This is where the external Attendee Sign-up form can be particularly helpful. Compared to a paper form where attendees may not complete much information, organisations using the electronic registration form can make certain fields required, ensuring that the attendee has to complete those fields before being able to submit the form. 

Making one or two extra fields such as Last name, or Email address required can help to make a difference here. 

In addition, using the Attendee sign-up form and moving the registration process online can help to remove errors made when trying to read/understand handwriting in terms of what has been input on a paper-based form onto Upshot.

Finally, organisations might find it helpful to use the Attendee Profile Picture feature as a way to verify existing profiles or between two profiles of the same name.


Identifying Duplicates

Whilst individual duplicates might be highlighted by users while going about tasks on the system, at other times you may want to review or identify all the potential duplicates on your account. In order to help users to carry this out, we have created a template Duplicate Checker to identify possible duplicates within your account through the use of the People Report.

You can download the Duplicate Checker template here. Before opening the download of the template, you may need to "unblock" the document first within your downloads in order to allow its functionality. Please see the video below which demonstrates how to do this, along with the rest of the steps needed to use the template. There are also step-by-step instructions within the first tab of the sheet.



Resolving Duplicates

If organisations find they have duplicate profiles the aim is to match up any information as needed and remove (delete) one of these profiles from their account.

Attendees can only be deleted if they have not been saved or submitted on a register, have timeline events added to their profile or been sent/completed a survey. If one of the profiles has none of the above they can be deleted by going to their profile and under Tools on the right-hand side clicking Delete.

If an attendee has one of the above associations, these must all be removed before the profile can be deleted. This two-step deletion is in place to ensure that data is not deleted too quickly or by accident. 

In addition, it is likely that the correct version of the attendee that you wish to keep needs all the associations then added to their profile as well.

Note, while it can seem like a quick solution to archive/pseudonymise the duplicate attendee, so that there are no longer two versions of the attendee on your account, this is not a solution we would recommend. Archiving/pseudonymising means that this duplicate profile will still appear in your reports, meaning that the number of unique attendees you have worked with overall, or that are of a specific Gender/Ethnicity etc will be incorrect. For more information on Archiving or Pseudonymising please see their respective guides.

Before starting the manual processes listed below, it can be a good idea to add to the duplicate profiles Last name or Nickname something such as DO NOT USE to ensure that other team members can differentiate between the two profiles on the system and do not continue to add information to the incorrect profile.

Transferring Timeline Events between the two profiles can be sped up by copy and pasting any notes attached to a particular event.

Any outstanding or completed Surveys attached to the duplicate profile will be seen on the right-hand side of their profile. This will allow users to find the relevant survey to remove submissions or the attendee from specific survey deployments. 

Users will also be presented with any 'Closed Surveys' that the attendee has previously been sent/attached, which they did not complete, and that have subsequently gone past the 'closing date' for submissions. The attendee must be removed from the deployments of these closed surveys to enable deletion of the profile. The quickest way to do this is to click on any closed survey presented, extend the closing date and then delete the participant from the deployment. The deployment can be closed again following this if desired.

Media files can only be edited by the team member who has added them to the system, so users may need to ask other users to assist them in this aspect.

Finally, the full details of Sessions attended by the duplicate profile can be found on their individual Session Report.

Go to the registers of these sessions (by clicking on the 'Date') and remove the duplicate profile and if necessary add the correct profile you wish to keep.

Note that the Session Report will only highlight submitted or counted sessions that the attendee is on the register for. If everything appears to have been removed from the duplicate attendee profile and there is still not the option to 'delete' it is worth checking to see whether the attendee is on any 'draft' registers or registers for 'sessions submitted, but not counted.' 

The quickest way to double check this is to run an Attendance Report , and choosing all options under the 'Session Status' filter. 


Key Terms

Archiving:

The archiving feature will allow you to store attendees that are no longer actively engaging in your projects and activities. Their data remains but they are no longer directly accessible for day-to-day use. For more information on this please refer to the Archiving guide.
Attendee sign-up form:
This is an external registration form, which can be shared via a public form URL or by embedding on your own website. This allows attendees to register themselves onto your database. The attendees get no access to the Upshot account. 
For more information on this please refer to the External Attendee sign-up form guide or view the short video here.
Deployment (Folder of survey responses)
This is a folder of attendees’ survey responses. This is where you can group together certain responses to the same survey, for example for an Evaluation survey those responses related to a specific group or activity. 
Also, the system can run a comparison of different deployments of the same survey. For instance, in surveys to do with Mental Health and Wellbeing it is often important to see individual responses change over time. Different deployments would allow you to measure and then compare this. I.e. Baseline results compared to Follow Up.
Media:
Media files can provide examples of qualitative evidence of the work you have been delivering. These files are not limited to pictures and videos but can also include word and excel documents as well as PDF files. These files will all sit in your media library. For more information on this please refer to the Media guide.
Pseudonymisation:
Pseudonymisation is a function that replaces or removes information that identifies an individual. This allows you to delete personal information you no longer want or need to keep, without erasing the attendee’s participation data. Once attendees are pseudonymised they are instantly archived.  This means they are no longer included in active searches.
In addition, personal identifiers are deleted or scrambled and only historical participation data is retained.
N.B.: It is not possible to reverse pseudonymisation of an attendee. Once the system has removed the personal identifiers of an attendee, they cannot be recovered. For more information on this please refer to the Pseudonymisation guide.
Registration Form:
This is the form completed when adding a new participant to the system. This contains fields around basic demographic details, permissions and consents as well as any custom fields. Organisations can add new participants using the internal registration form, People > Add new, where they enter the information often from a physical copy onto Upshot and/or use the external Attendee sign up form which provides a link for individuals to complete the registration form themselves.
For more information on the Registration form please view the short video here.
Timeline Event:
Each attendee on the system has a timeline and you can track points of interest on their journey as "timeline events". These record what has happened or changed with a participant outside of regular session data and can often be viewed as individual outcomes from participating in the project.
For more information please refer to the short video here.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us