Does anyone else have issues with staff and students creating multiple constituent records - one for their staff or student emails and then another for their personal email address?
We have found this to be a small issue on the front line as staff/students dont always recollect the email that they booked with so might struggle to locate their own bookings.
But more of a nuisance is that our merge utility pulls them up as duplicates because their name matches on both accounts... we then find that we cant really merge them because they are in theory two separate accounts so they all sit in the "select constituent ID to be kept:" list in the merge tool? It becomes hard then to see when other potential duplicates are added to that list by the utility. I know there is a way that we can mark the accounts so that they dont get pulled into that list but that doesnt really solve our problem because we still want the system to identify in future if a real duplicate has been created on one of the two accounts.
Does anyone have any clever criteria for the dupe function that can filter out these from being pulled in the merge utility?
Thanks, Lianna
Gawain Lavers thanks for your input. Our students and staff email addresses are both @kent.ac.uk so presumably from what you have said, this could cause an issue with the same handle? whereas if they were different it would be ok? have I understood correctly?
I'm not sure I understand. Logins must be unique. EAddresses need not be. If you use TNEW it will expect Login to be identical to the Eaddress, so if two accounts both have john.smith@kent.ac.uk for Eaddress then they both can't have it for their Login, Tessitura simply won't allow it. If the two accounts each have john.smith@kent.ac.uk as an Eaddress (but not Login), then if merged then either both Eaddresses are kept, or perhaps it's smart enough to know that you only need one (since they're identical). Don't remember. It's definitely possible for a customer to have multiple Eaddresses that are the exact same email address on their account.
If one account has john.smith@kent.ac.uk for both Eaddress and Login, and the other has jsmith@kent.ac.uk for both Email and Login, and the accounts are merged, both Eaddress/Login pairs will be on the kept account, and either will allow John Smith to log in to his account. They will have different passwords.