FTAnalyzer icon indicating copy to clipboard operation
FTAnalyzer copied to clipboard

Errors Report - mark as not an error

Open ShammyLevva opened this issue 7 years ago • 4 comments

In the data errors report allow user to flag a row as not an error.

ShammyLevva avatar Dec 11 '18 10:12 ShammyLevva

Tricky as it is difficult to know if the tree loaded is a modified version of old tree or a completely different one. Thus checking a specific individual's facts between files is challenging without some form of token in GEDCOM or pattern match for individual stored in a persistent store (database/registry/etc).

ShammyLevva avatar Dec 15 '18 00:12 ShammyLevva

Just had a thought - each report could have a "Not Error" token

If you then copy this as an "FTA" fact to the persons profile then it would ignore them when that specific report was run?

e.g.

"Spouses with same Surname" - "Not Error token ++12++"

In John Smiths and Mabel Smiths profiles I then enter a fact

FTA ++12++

Similar to how we have to flag Lost Cousins?

mee-david avatar Jan 13 '19 12:01 mee-david

That would work. A bit trickier with the different error types though vs just a year for Lost Cousins entry. I’ll have a think about how it might work.

ShammyLevva avatar Jan 14 '19 20:01 ShammyLevva

I imagined you could have a different code for every “error” so we could say that error ##12## was ok but not having a token for 1-11 would flag them as errors should Joe Bloggs ever show up.

Maybe just for those where the likelihood of it being ok is there. So “dad died 3 years before born” needs investigating and could never be “ok”. But “2 spouses with same surname” could potentially be ok. Etc

mee-david avatar Jan 14 '19 23:01 mee-david