Suppressing age difference warning

[KJB]

In my genealogy, there is a married couple with an age difference of 23 years. This is above the maximum of 20 years, and hence flagged as a warning in the compliance report. I know that I can simply ignore the warning, but I'm striving to get no warnings or errors at all. Is there a way to suppress the warning for this specific couple, but leave it intact for any others? (There are none, but I might make a mistake in entering a birth date in the future.) Perhaps something like adding a VALID or VERIFIED entry?

[Zurga]

Yes you can.
Add a "_VALID" tag under the MARR tag
https://docs.ancestris.org/books/user-guide/page/validate-gedcom-compliance-and-data-consistency#bkmrk-utilisation

Zurga

[KJB]

I had several tried things in this direction already, but with no luck. I don't understand the User Documentation nor your explanation.
The anomaly warning highlights only the two individuals (I37 and I75 in my case) but not a family identity.
If I click the I37 text in the compliance report, a new window opens on the bottom left, where I can select the relevant family identity (I think) which is F23 in my case.
If I click that, I see the two individuals in the top right window which I think is the GEDCOM editor.
But at that point I don't know how to proceed. I don't see a MARR tag.
I've also looked in the GEDCOM directly with a text editor. I'm happy to edit there directly (e.g. adding a _VALID tag) if Ancestris can't do it, but I don't know how either. (But of course Ancestris can do it, if I only know how :-) )

[Zurga]

I have verified on my computer :
- Open the GEDCOM Editor with menu "View" => "Gedcom Editor"
- Display the FAM entity of the couple (F23 as far as I understand your previous message).
- Right-click on HUSB line and add a personalized tag "_VALID", put a value ("Y" typically).
- Do the same on WIFE line
- Launch again the Gedcom verification tool.

Zurga

[KJB]

About that third step:
If I right-click the HUSB line, a context-sensitive menu appears. In it, the closest thing to "add a personalized tag" is Add property via the assistant. I clicked that, then clicked "User-defined property..." then typed "_VALID Y" in that line. Did the same for WIFE.
I then ran the verification tool again. The marriage age difference warning is still there, for both the male and the female individuals.
If I look in Add property via the assistant again (after right-click on HUSB), then Available predefined properties is not empty anymore like it was before, but it contains "_VALID (_VALID)" in the left-hand panel, and "_VALID: Custom tag not defined in GEDCOM" in the right-hand panel.

I must be doing something wrong. Maybe it is significant that the warning in the compliance report appears for the two individual entities (I37 and I75), but not for the family entity (F23)?

[Zurga]

Sorry, next time I will check the exact label of the context menu.

When you create a user-defined tag, just put "_VALID" and press "OK".
After that, you can put the value ("Y" for example, any value is correct, you can put an explanation if you want).
Validate your entry.

Zurga

[KJB]

Before I try that, I want to get rid of the incorrect tag that I added. I tried to do this by rightclicking the _VALID tag under HUSB in the GEDCOM editor and then click delete. Indeed the incorrect line under HUSB disappeared. Similar for WIFE. So far so good.
However, when I proceed to rightclick HUSB again and then click "Add property via the assistant", like before, the list below "Available predefined properties" is not empty like it was initially before I started tampering with this, but contains "_VALID (_VALID)" on the lefthand side, and "_VALID: Custom tag not defined in GEDCOM". That looks to me like the invalid tag is not really gone.
Should I ignore it? Or perhaps use it to add _VALID and then put the value Y as you described? It's all quite puzzling to this new user, sorry.

[Zurga]

Close Ancestris and launch again.
The dynamic list could have not been updated and use a cache.

Zurga

[KJB]

The closing and re-opening has worked. The incorrect tags are gone. That part is solved.
I proceeded to add _VALID to both HUSB and WIFE, and gave the value Y for each. In itself, that seemed to work OK as well.
However, if I re-run the GEDCOM compliance report, the warning about the age difference is still there. So the issue that I started with is not yet solved.
Are we sure that the _VALID Y tags that I added, refer to the age of both individuals, as opposed to the individuals being VALID in a general sense? And also, does Ancestris recognise _VALID in the first place? I' asking because it is apparently a non-standard tag, since I first had to add it before I could assign a value.
I closed and re-opened Ancestris just to be sure that it wasn't a cache issue again - quod non.

[Zurga]

Donc forget to check the preferences to "Ignore the anomalies with _VALID"
https://docs.ancestris.org/books/user-guide/page/validate-gedcom-compliance-and-data-consistency#bkmrk-personnalisation

_VALID is a tag invented by Ancestris to manage theses cases.
So only Ancestris manage this tag and, yes, the code is able to manage this tag.

Zurga

[KJB]

Thank you, that did the trick. Issue solved.
I wasn't aware of that setting, although I could have been if I had thoroughly read the whole documentation. But it's a bit much...