Log in
Sign up
View all  |  Close all
#
Subject
Posted by
Actions
1
Smart Match?? Plain Stupid Match it should be...
Dag Torkild Antonsen
- Close

Smart Match is not so smart, it should be changed to Plain Stupid Match.

Why?

One example:

Serine Maria Hansdatter Rasch b. 1864 d. 1901

has the smart match:

Marta Marie Hansdatter b. 1822 d. 1851

Why should I need to deny this is not correct person. The smart match says that a person dead before my person is even born is a good suggestion. Wrong parents, wrong husband, wrong children.. u name it. I have 25.589 "smart" matches awaiting to confirm. I do NOT want those stupid suggestions.. And even have to pay for them.

Dag Torkild Antonsen
Norway
- Reply
2
RE: Smart Match?? Plain Stupid Match it should be...
John and Eileen O'Connor
- Close

I agree "Smart Matches " are not so smart.   Example: Mary O'Connor nee Lynch matched with Mary Lynch nee Conroy.  Obviously to anyone with a functioning brain that Mary Lynch and Mary Conroy have nothing in common except that their forename is Mary.   Oh wow , there's another Mary in the world !!   One born in Ireland in 1926 and another born 10,000 miles away in Australia in .........1880 , I believe.   How is this a match?  And nothing else in common.

 I get hundreds of so called "Matches" which take forever to delete/reject.

It also seems to me that I have requested the system to ignore matches from specific trees, but I keep getting them next month.  Does anyone else find this happens to them? 

John and Eileen O'Connor
Ireland
- Reply
3
RE: Smart Match?? Plain Stupid Match it should be... [2]
Lior Shaked
- Close

Hi Eileen,

Thanks for writing to us.

The reason that you see wrong natches as well as correct ones is that we show you all matches, to reach mazimum research potential, like Shani explained.

I will forward your request to improve the quality of matches to our developers.

Can you please give me an example of a tree you chose to ignore, and got again?

Best Regards,

Lior

MyHeritage team 

 

Lior Shaked
Israel
- Reply
4
RE: Smart Match?? Plain Stupid Match it should be...
shani treves
- Close

Hi Dag,  

In our Enhanced Smart Matches, we now show you ALL of your matches, the high quality matches and the lower quality ones.

The list is sorted by quality, so you’ll see the best Matches first, but we also show you the other matches below, so that no information will be hidden, and all your research potential will be met.

If you find that a match is wrong (sometimes siblings are matched with each other for example), just mark it as rejected. The Correct match will most often appear at the top of the list.

Marking the match as rejected will help you manage your matches, and will also help us understand that this should not be regarded as a Match in the future.

You can also choose to ignore all your Smart Matches for a family tree that you are matched with, so that you won't receive any results from this tree in the future.

Please see the following FAQ for more information: 

How do I ignore all online Smart Matches™ for a tree that I am being matched with ?

 

Best regards,

Shani

MyHeritage team 

shani treves
Israel
- Reply
5
RE: Smart Match?? Plain Stupid Match it should be... [2]
Dag Torkild Antonsen
- Close

I have now 43.000 matches. Do you think it is a good way to sit and click "reject" on all those?

The sollution you mention is like having problem with a wheel on your car, and the sollution is "condemn your car".

It would be better if the Smart Match used exact match to even be listed as a match.

Today I even got a match on persons with different sex. 

The sollutions mentioned later in this thread is only a cure for a sickness. It is better to remove the cause of sickness.

A match should be in 3 levels based on importance: 1. Name and date of birth of selected person. 2. Names of parents / Names of children. 3. Additional info like place of birth, place of death and so on

A name is a match if 2 letters per 3 letters of name is correct. Then you are safe in case of name Olav or Olaf.

Different sex = automaticly rejected.

And so on..

It's so easy to make the perfect formula..

Dag Torkild Antonsen
Norway
- Reply
6
RE: Smart Match?? Plain Stupid Match it should be...
Risto August Virtanen
- Close

Yes, many matches are not so smart. I got one where they lived 300 years apart!Foot in mouth

Confirmations/rejections should be allowed to non-Premium members, too.Wink

Maybe it would help even matches become smarter.

Better genealogy is our goal after all — or at least it should be.Cool 

Risto August Virtanen
Suomi
- Reply
7
RE: Smart Match?? Plain Stupid Match it should be...
Ronny Tertnes
- Close
I would like at least the opportunity to filter the smart matches, for example when I (soon) enable smartmatch for the bigger tree I have of 88.000 names, I would love to be able to (initially at least) filter that I do not want to see smart matches below 70% for example...
Ronny Tertnes
Norway
- Reply
8
RE: Smart Match?? Plain Stupid Match it should be... [2]
philip james wood
- Close

Yes, I agree most matches of less than 70% are rubbish, so why not suppress these so taht we can concentrate on the better ones?

I have also ignored a lot of trees but still they keep showing up!

Phil. 

philip james wood
Whittington, Lichfield, Staffordshire. England.
- Reply
9
RE: Smart Match?? Plain Stupid Match it should be... [2]
Dag Torkild Antonsen
- Close

Even a 70% match is plain stupid..

From i wrote that line i went to my smart matches, used 1 minute.. found this:

86%:  Johan Mortenssøn Blix b1666 compared to Lars Mortensen Mortenssøn Blix b1671

Everyone knows that this is not the same person. >Only 2 of 4 infos is correct. That is 50% Since they are siblings they have same parents. Thats why the 86%.

It is wrong to use parents as equal value as the name of main person.

Main person name and birth/death value should be 70%, children 20%, parents 10% of the percentage calculated..

Dag Torkild Antonsen
Norway
- Reply
10
RE: Smart Match?? Plain Stupid Match it should be... [3]
Lior Shaked
- Close

Hi Dag,

Thanks for your reply.

I took a look at the example of wrong matches.

These two people have lots of similarities, and that is why they were matched- their first names are similar and both contain Mortenssøn, they have similar birth years and similar relatives. This is the reason they were matched despite being siblings.

You are welcome to reject this match to help us understand that this should not be regarded as a Match in the future. 

Best Regards,

Lior

myHeritage.com team 

Lior Shaked
Israel
- Reply
11
RE: Smart Match?? Plain Stupid Match it should be... [4]
Dag Torkild Antonsen
- Close

I could make you a complete algorithm that removed 95% of the wrong matches. You need to use graduated points, calculated out of each of percentage simularity of each value stated of each individ.

Name - surname and dates is main criteria, secondary is parents - children - siblings, tertiary is place of birth and so on.

And why I'm sure? I'm as Sheldon Cooper from Big Bang Theory, but sadly without his eidetic memory.   I aced the Mensa-test in 13 minutes and I complained to the board why they couldn't do better...

If I had something like your company in my back, I would turn the whole system around. Making every person a customer, even those who don't want to do research. A product noone would say no to.  I would double your return.. All systems available today is like having a watch (your person in your three). Then you know the time. If you have 2 watches (a match from another three, but not same values), you cant be sure which of them is correct.. There is way too much wrong information..

Well.. I have now over 60.000 matches.  If I click once every second, I will need to click 120.000 times in next 33 hours! I won't do that.. I wait until you have a product you could call smart match. For real..

 

Dag Torkild Antonsen
Norway
- Reply
12
RE: Smart Match?? Plain Stupid Match it should be... [2]
Martin Vatshelle
- Close

I also support Ronny's Idea.

And also would suggest a faster way of rejecting/accepting maches. When I have one person with over 100 matches it takes a long time to reject all the wrong ones. Often it is siblings beeing matched, then I would like to get a list of the different first names with checkboxes and tick off all siblings, then all those matches would be rejected. Same with the other data, as if two persons have the same name, but different birth year, I would want to reject all with the wrong birth year

Martin Vatshelle
- Reply
13
RE: Smart Match?? Plain Stupid Match it should be... [3]
Lior Shaked
- Close

Hi Martin, 

Thanks for your suggestion.

I will pass this on to the appropriate department for consideration.

Please let me know if you have any other ideas as we value such input from our users. 

Best Regards,

Lior

MyHeritage.com Team 

 

Lior Shaked
Israel
- Reply
14
RE: Smart Match?? Plain Stupid Match it should be... [2]
Esther Weinberg
- Close

Hi Ronny, 

Thank you for writing to us.

This is currently not available on the family site, although its a great suggestion.

I will pass this on to the appropriate department for consideration.

Best Regards,

Esther / MyHeritage Team 

Esther Weinberg
- Reply
15
RE: Smart Match?? Plain Stupid Match it should be... [3]
Eric Dalton
- Close
That is a good idea. Count me as a supporter.
Eric Dalton
- Reply
16
RE: Smart Match?? Plain Stupid Match it should be... [4]
Dag Torkild Antonsen
- Close

Hehe..

Why? It's like taking headache-pills for noises around you that gives you headache, when removing the cause of noise that gives you the headache should be done instead.

Dag Torkild Antonsen
Norway
- Reply
17
RE: Smart Match?? Plain Stupid Match it should be... [5]
Shelly Weiner
- Close
I gave up trying to figure out StupidMatches...

If I see the same "match" appear again after Ignoring and rejecting, then I go the my person, add spaces to the name and the computer can't figure it out. 

Jacob Smith  becomes  J a c o b  S m i t h.    I can still read it with the spaces, computer can't.  Viola! No more StupidMatch.

Shelly Weiner
Henderson, NV
- Reply
 
Loading...
Loading...