Custom Event dated before birth date and Quality Score = Medium
https://www.familysearch.org/en/tree/person/details/GSM2-YBF
At the time I'm writing this, Sarah Stever PID: GSM2-YBF
shows a "Medium Quality" score.
She has a Birth Year of 1866.
She also has a Custom Event "Marriage Registration" with a date of 29 May 1854.
The Custom Event is 12 years before her birth.
I checked that the entered date values DO match the standard values.
The Conflict-free Data field shows Zero.
I think that an event dated prior to a person's birth should be listed as a data conflict.
I think the situation of an event dated before a person's birth should drop the Quality score to Low.
Answers
-
@Ronald P. Tilby said "The Conflict-free Data field shows Zero. I think that an event dated prior to a person's birth should be listed as a data conflict."
I would agree for standard events that have an identifiable meaning, such as death, or burial, or residence, etc. But a custom event could be anything. Since it has no identifiable meaning, the Data Quality algorithm can't make any assumptions about conflicts.
For example, suppose a person has a will that refers to all the testator's children. One of them had not been born at the time the will was written, but was born 12 years later. That child could have a custom event like "referred to in father's will" where the date is correctly 12 years before the child was born. That's not a conflict at all.
So it is understandable that dates on custom events are not used to determine conflicts as is done for standard events.
1 -
Noted: this issue has been added to the queue :)
0 -
@Ronald P. Tilby a ticket has been created for this issue. Thank you for the feedback!
0 -
- The standard "Reimsbach, Merzig, Rhineland, Prussia, Germany" (ID: 12254991) is used for 1871 to 1945. This conflicts with the birth date of 20 August 1850.
- The standard "Reimsbach, Merzig, Rhineland, Prussia, Germany" (ID: 12254991) is used for 1871 to 1945. This conflicts with the christening date of 21 August 1850.
This repeated for all places in the area, please stop 1871 as authoritarian date. It's 1815 for crying out loud!. I had to dismiss every one of them because it is giving false information.
0 -
@W D Samuelsen contact me please Your comment has been moved to a separate discussion in the FamilySearch Places group. You can find the discussion here:
0 -
I was directed to this about the quality section.
Here's to deal with
Britten, Saarholzbach, Losheim, Freudenburg, Saarburg, Mettlach, Bettingen, Saarlouis, Nalbach, Serrig, Beurig, Ulmen, Brotdorf, Hausbach, Trassem, Hilbringen, Schwemlingen, Budingen, Wehingen, Oppen, Erbringen, Luckner, Duppenweiler, etc
Every one has this crazy statement attached….
- The standard "xxx, Merzig, Rhineland, Prussia, Germany" (ID: xxx) is used for 1871 to 1945. This conflicts with the birth date of (all dates before 1871).
- The standard "xxx, Merzig, Rhineland, Prussia, Germany" (ID: xxxx) is used for 1871 to 1945. This conflicts with the christening date of (all dates before 1871.)
Every one is correct from 1815 onwards, not from 1871 onwards. This statement is sowing confusion already as it is.
0 -
The feedback for Quality Score leads to this discussion, not elsewhere.
0
