Why is "Possible Matches Found" lying to me?

LegacyUser

Juli said:

If it's not entered as a birth, why is it labeled "birth"?

LegacyUser

Jordi Kloosterboer said: I know other sites and programs use the christening info if birth is not listed, but they usually say it is christening. I think it should say Christening too as that is what it is (according to the record).

LegacyUser

Paul said: Sometimes it's the source that shows the christening as a birth (or even as a baptism, but better not go into that), but elsewhere I find it has been the user's choice in adding the data to the birth fields, when clearly it refers to a christening.

LegacyUser

Juli said: There's no source involved here; I was entering a spouse using the "add spouse" button. And my whole point is that it WASN'T entered as a birth. It was incorrectly _labeled_ as a birth in the "possible matches" popup.

LegacyUser

Adrian Bruce said: Yes, I can get the same thing as well...

Here I'm trying to Add A Spouse named Martha Spode, born 1737. Here's what Possible Matches shows me...


It is clearly offering 936F-ZV6 with a Birth of 29 May 1737.

If I go to the profile in question, it shows nothing for the birth but a "Christening" of 29 May 1737, viz:


Basically, it's offering the best it can (which is fine) but describing it incorrectly. Not just incorrectly but in a misleading manner. The reason that I chose Martha Spode is that I know my Martha was not baptised until a few years after her birth (not the Martha of the profile shown by the way - another one).

It seems to me that the system is (yet again) attempting to second guess what we want to know and simplify it because we can't be expected to understand that a birth and baptism might be different...

LegacyUser

Erika Campbell said: Remember that this is an international Tree and if it says baptism or christening, just added in the appropriate spot and it will help others also.
Erika

LegacyUser

Adrian Bruce said: Agreed - but the point is that in the "Possible Matches Found" for "Add a Spouse" (and goodness knows what else...), the details of the possible matches found are misrepresented and incorrect and could, therefore, result in the user rejecting that possible match when it's actually a good match.

Yes, the correct information is on the profile but no-one's going to dig down to find it if an earlier screen has displayed incorrect data that leads to the user rejecting it.

LegacyUser

Juli said: I'm confused about what possible relationship Erika's comment has with my question. (Yes, "christening" and "baptism" are EXACTLY THE SAME THING, but that's not what this question is about, at all.)