Uncorrectable Suggestions

+12 votes
427 views
I've seen versions of this question, but can't find one that quite answers my question below.

Is there a way to hide uncorrectable suggestions.  I'm starting to build up a list, and new suggestions tend to be at the bottom.

For example, I know for a fact that the date on the Headstone is incorrect, so the date I have on WikiTree and the date on Find A Grave will never match.  I'm not going to ask someone to change the headstone.

Another is birthdates, again a different between multiple sources and Find A Grave.  The birth date is unconfirmable because of the different dates from different sources.  The best one can do is make an educated guess.

It'd be nice to have a expand collapse option for suggestions that have a status.
in Policy and Style by Chris Strickland G2G6 (9.3k points)
Marking the suggestions as false doesn't get rid of them?
I didn't mark them as false because they weren't false, just unresolvable.  But I may start doing that.
I call any suggestion that conflicts with the source on the profile false.  If I am uncertain what action to take I make a comment so at least I can tell I have already "been there"

2 Answers

+27 votes
 
Best answer
When appropriate you can mark a suggestion as false.

I would defer to an official document over a gravestone, and I would defer to a document closest to the event being recorded (both birth and death certificates have birth dates, if they differ go with the birth record).

I have seen baptismal records (with birth and baptisms dates) that are inconsistent with civil birth records (baptism before civil birth record). Choose one, and note that there is an unresolvable error.
by George Fulton G2G6 Pilot (731k points)
selected by Kevin Conroy
Though death certificates are authoritative for the death, for birth, they typically rely on an informant.  If the informant was the mother, she likely supplied correct information but if it was the housekeeper next door, maybe not so reliable. A birth certificate should normally trump a headstone while a death certificate might not.

In Ireland, as one example, there was a penalty if the birth was not reported within the required period and many parents would give a birth date later than the actual date but within the period that would avoid a fine so, for Ireland at least, I tend to favor the baptismal record over the civil record.

Keep in mind, even official records that are authoritative might be provably wrong.  This is certainly the case for some birth certificates where DNA clearly shows that the reported father is not the actual biological father.

Long story short: a little detective work is needed but George is correct to say that marking a suggestion false is often the way to go.
+7 votes

Clicking 'false suggestion' will hide it forever.  So that works for any suggestion that isn't correctable for whatever reason--your Aunt's middle name really is Sister, your grandfather's first name is Judge, etc. 

Specifically, for FindAGrave, you can add a bit of code to FindAGrave entries which tells the system not to check them.  It ends up being {{FindAGrave|[#memorial#]|sameas=no}}

(Edit:  whoops!  I see below that the sameas=no should only be used for completely wrong profiles, but not for inaccurate suggestions.)  

by Celia Marsh G2G6 Mach 9 (99.3k points)
edited by Celia Marsh

Hi Celia. Sorry but this advice is not correct. See

https://www.wikitree.com/wiki/Help:Find_A_Grave#Find_A_Grave_Hints_from_WikiTree.2B

which says:

Sameas=no should only be used if the Find A Grave memorial represents a different person or contains conflated information from multiple people and a majority of the information represents a different person. It should not be used if the Find A Grave memorial generally represents the same person but contains some incorrect information.

One reason for this is that if you mark the memorial sameas=no, it will suppress all suggestions about it, not just the one in question, so at some future point you may miss receiving a different suggestion which is actually correct.

As George said, the right solution is to mark the particular suggestion as false.

There are some exceptions:

[sameas=no] can also be used in case of multiple memorials for the same person on FindaGrave (CENOTAPH, MEMORIAL SITE, need merge on FG, ...) and on pre1700 profiles if the information on FG is incorrect.

I would have thought sameas=no would be more than is allowed on a Link Template 

The sameas parameter is described (briefly) at

https://www.wikitree.com/wiki/Template:FindAGrave

The page you linked, John, says: 

The parameter "sameas" is acceptable for the Find A Grave template since it is used to communicate link-related machine-readable information but does not print anything on the page.

Related questions

+16 votes
3 answers
+29 votes
7 answers
+12 votes
0 answers
+10 votes
0 answers
+9 votes
0 answers
+21 votes
2 answers
+11 votes
0 answers

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...