Where is Soocial's merging or de-duping?
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Soocial does have a de-duping or merging feature. Unlike other sync solutions we aim to have our merging work behind the scenes. That means that when you sync we start a similarity look up for possible merging candidates, then merge them if they reach a certain score.
All this merging goes on behind the scenes - and happens with every new contact that makes its way into Soocial. This way your address book always remains sane. You don't have to think about de-duping, it just happens.
I’m happy with our approach
The company and 1 other person say
this answers the question
-
Inappropriate?Soocial does have a de-duping or merging feature. Unlike other sync solutions we aim to have our merging work behind the scenes. That means that when you sync we start a similarity look up for possible merging candidates, then merge them if they reach a certain score.
All this merging goes on behind the scenes - and happens with every new contact that makes its way into Soocial. This way your address book always remains sane. You don't have to think about de-duping, it just happens.
I’m happy with our approach
The company and 1 other person say
this answers the question
-
Inappropriate?I'd definitely like more details on this, because this is the biggest problem in any syncing solution.
Whats the "score", when is it reached, and what happens when its reached? Just a total merge of all data?
Is there a manual merge once I realize there are two dupes in my contacts?
I’m wanting to know more
-
Inappropriate?I keep hitting the dedupe button but nothing happens. It says it's going to run in the background, but I still have the same total # of contacts and soocial still says I have dupes. What am I doing wrong?
I’m frustrated.
-
Jason, the deduper will only take care of two contacts that are pretty much identical including labels etc. If you have other duplicate entries, you can manually merge them in the webapp. -
Inappropriate?Ah, got it. By the way, I noticed that shift+click to select ranges of contacts now works - thanks!
I’m thankful
-
Cool, we will still improve all this stuff as we go. -
Inappropriate?How are notes fields merged? How are field-level conflicts handled? It's kind of scary not knowing how this works.
-
Inappropriate?Yeah, the merging process is super scary, so there needs to be some nice "hand holding" done by the UI to step everyone through which changes are being made.
-
Inappropriate?It is pretty simple guys, the merge will combine all details for both contacts.Only if some contact details are exactly similar they will be made one.
Example:
Mobile: 034567890
Mobile: 034567890
Will be made one mobile number for the new contact.
Home: (034) 23546798
Home: 034-23546798
Will be kept as two separate contact details. So nothing scary about that. Could be more annoying since your might end up with lots of duplicate info. But rather duplicate info than info lost as far as we are concerned.
We'd love for all of you to give us suggestions to how we can make this stuff better! -
I understand the concept of this, and agree with the principle. it would however, be good, to enable a normalisation contact details, especially phone numbers.
It would great if they could be normalised according to formatting standards per country/region, as phone numbers tend to be written in different ways in different parts of the world.
I have numerous "duplicate" phone number entries in contacts, due to syncing with other services, applications and phones in the past. For phone numbers, in principle only the digits matter, right? (yes, I know of a couple of others, like '+', '#' and '*' signs and potentially some pause characters, but in principle...) -
Hey KMK,
We might implement that in the future. It would require user specific setting. We haven't implemented that yet. -
Inappropriate?I'm still not understanding the heuristics for field level conflict resolution. What if two fields are different? Which one wins? Are notes fields concatenated?
-
Inappropriate?Well as said, we take over all the contact details for both contacts in to the new merged contact. So there will be 2 notes fields in the Vcard. That probably means one of the notes will not be visible.
-
Probably? Visible versus Invisible? Still no description of how field level conflicts are handled. OK then, I'll test it to find out. -
Inappropriate?I was saying probably because I don't know if that is true for all connections. It might be that there are devices that are able to display multiple notes for one contact.
You asked: "What if two fields are different? Which one wins?"
Answer: We keep them both.
You asked: "Are notes fields concatenated?"
Answer: No they don't, we keep both of them too. But maybe we should combine them.
Only if we have exactly identical details for both contacts we will delete one.
I guess they are not really heuristics even involved. We just compare contact details for duplicates, all the other stuff will be kept in the new contact. -
Inappropriate?I'm wayting for my dedupe to end.
If it does not find all duplicates. Guess I'll fix them by hand ;-)
Still, nice job you're doing here.
I’m confident
-
Great h3lder. Did it finish? Please let us know if there is anything we can do for you.
Loading Profile...



EMPLOYEE


EMPLOYEE