* Import ged from Ancestry to FH, general advice needed

[GrahamJWood]

Moving on from the Marriage discussion, the first few exceptions now look like this

---------------------------------------------------------

Record Type=Individual. Gedcom Id=P7. Record Number=7.
l.192 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 BIRT Upper End"

Record Type=Individual. Gedcom Id=P9. Record Number=9.
l.282 - INFO ONLY: Loaded uncategorised data (non-GEDCOM): "2 SOUR @S-1300701919@"
l.283 - INFO ONLY: Loaded uncategorised data (non-GEDCOM): "3 NOTE http://search.ancestry.co.uk/cgi-bin/ss ... try&gss=pt"
l.284 - INFO ONLY: Loaded uncategorised data (non-GEDCOM): "3 DATA "
l.285 - INFO ONLY: Loaded uncategorised data (non-GEDCOM): "4 TEXT Name: XXXXXXXXXXXXX Birth: Jun 1954 in Scunthorpe, Northamptonshire, Lincolnshire Death: "

Record Type=Individual. Gedcom Id=P10. Record Number=10.
l.321 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"

Record Type=Individual. Gedcom Id=P11. Record Number=11.
l.358 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Son"
l.379 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Other Records: Child"

Record Type=Individual. Gedcom Id=P12. Record Number=12.
l.414 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"
l.428 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 DEAT Age at Death: 74"

Record Type=Individual. Gedcom Id=P13. Record Number=13.
l.499 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Son"
l.508 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Step Son"

Record Type=Individual. Gedcom Id=P18. Record Number=18.
l.602 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Wife"
l.643 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Head"
l.652 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Age: 8Relation: Daughter"
l.658 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relationship to Head: Servant"

Record Type=Individual. Gedcom Id=P22. Record Number=22.
l.845 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Wife"

Record Type=Individual. Gedcom Id=P23. Record Number=23.
l.872 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relationship: Son"
l.896 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Head"
l.902 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 DEAT Age at Death: 74"

Record Type=Individual. Gedcom Id=P25. Record Number=25.
l.938 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"

The "1 DEAT Age at Death: 74" like entries are further examples of additional data on tag lines, so not a major issue.

The main problem is census lines exported as RESI. Without the complete source restructuring using Ancestral Sources, is there a plugin based way to turn these into census events?

Regards
Graham

[tatewise]

Assuming that all the 1 RESIdence tags are meant to be 1 CENSus tags, then the Change Any Fact Tag Plugin will change them all in one go. Check the Obtain Help & Advice button for instructions.

The only snag might be if there are any genuine 1 RESIdence tags, then they will get changed too.
You could try filtering on Date where you repeat the process for each Census Date from 1841 to 1911 such that only 1 RESIdence tags with a matching Date get changed.

[GrahamJWood]

Mike,
I added date filters to be safer, and that seemed to work, the top level census records are now in place

I am now left with the relationship information which shows up as exceptions for example:-

Record Type=Individual. Gedcom Id=P10. Record Number=10.
l.321 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"

Record Type=Individual. Gedcom Id=P11. Record Number=11.
l.358 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Son"
l.379 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Other Records: Child"

Record Type=Individual. Gedcom Id=P12. Record Number=12.
l.414 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"
l.428 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 DEAT Age at Death: 74"

Record Type=Individual. Gedcom Id=P13. Record Number=13.
l.499 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Son"
l.508 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Step Son"

Record Type=Individual. Gedcom Id=P18. Record Number=18.
l.602 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Wife"
l.643 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Head"
l.652 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Age: 8Relation: Daughter"
l.658 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relationship to Head: Servant"

Record Type=Individual. Gedcom Id=P22. Record Number=22.
l.845 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Wife"

Record Type=Individual. Gedcom Id=P23. Record Number=23.
l.872 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relationship: Son"
l.896 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Head"
l.902 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 DEAT Age at Death: 74"

Record Type=Individual. Gedcom Id=P25. Record Number=25.
l.938 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"

Record Type=Individual. Gedcom Id=P27. Record Number=27.
l.1011 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Niece (Great Niece)"
l.1037 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelation to Head of House: Wife"

Record Type=Individual. Gedcom Id=P28. Record Number=28.
l.1096 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Daughter"
l.1105 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: SingleRelation to Head of House: Step Daughter"

Record Type=Individual. Gedcom Id=P29. Record Number=29.
l.1141 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: SingleRelation to Head of House: Boarder"
l.1170 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head: Son"

Record Type=Individual. Gedcom Id=P30. Record Number=30.
l.1252 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Relation to Head of House: Daughter"
l.1258 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Marital Status: MarriedRelationship to Head: Wife"
l.1264 - INFO ONLY: Detected & fixed field format error (data loaded using Uncategorised Data Field): "1 RESI Age: 30Relation: Wife"

This is presumably in as Uncategorised Data Fields, how do I convert these to notes? or is there a better way to handle them?
Regards
Graham

[AdrianBruce]

Adrian,
please read my earlier post. ...

Indeed Graham - so if I'd re-read that earlier post about the resolution, then you confirm my speculation in the last paragraph. I just thought it useful to give an instance of how Ancestry got itself into that knot in the first place. Not sure if there are any source collections other than the FreeBMD and Ancestry's own England & Wales marriage indexes that give rise to this anomaly.

[tatewise]

Graham, as I said earlier on Thu Aug 03:-
Whether FH puts it in 2 _UNCAT or 2 NOTE depends on Tools > Preferences > File Load/Save and Move invalid data into note fields where possible.
Try importing with that option both ticked and unticked to see the differences.
The advantage of putting into 2 _UNCAT is it allows a custom Plugin to move the _UNCAT values to Address in most cases, or wherever is appropriate for each type of fact.

I have a Plugin to Move _UNCAT to Address for all Events and Residence facts.
It could be easily adapted with an exception for Census Events and move _UNCAT to the Note field.
There may need to be other exceptions after you have investigated further.

[GrahamJWood]

Adrian,
I think any marriage source which doesn't directly link the spouses would trigger this issue. I think my separate issue with duplicates was a failure to match to a preexisting marriage, for example when a full date was present and was not matched to a quarter date.
Regards
Graham

[GrahamJWood]

Mike,
adapting your plugin sounds like a great idea, I looked in the plugin store but couldn't find it, could you let me have a link please.
Regards
Graham

[tatewise]

No it is not published in the Plugin Store, but is one of several custom Plugins I've written over the years, usually to assist with imported Gedcom data.

I have adapted it such that _UNCAT text is appended to the Note field of Census Events, and to the Cause field of Death Events, and otherwise to the Address field of all other Events and Residence facts, but you may find other cases are needed.

See Attachment Move _UNCAT to Another Field Plugin Version 0.1 Date 04 Aug 2017.

Prior to running the Plugin use File > Backup/Restore > Small Backup just in case!

After running Plugin the Result Set lists all the moved text, and clicking on any Uncategorised text field will open the Property Box with that field displayed.

If any changes are unsatisfactory then use Edit > Undo Plugin Updates BEFORE CLOSING FH.

[GrahamJWood]

MIke,
I fear I may have given you duff information about exactly where the tags were. I took a backup, ran the plugin, the notes didn't appear where I expected, so I undid the changes, and took a look at the ged file with notebook++ I have attached the results below.

The _UNCAT tags seem to be under a subordinate SOUR tag, 1258 examples of this

1 CENS
...
2 SOUR %INDI.CENS._UNCAT% Relation to Head of House: Son ~ Invalid Tag

I think this needs to translate to something like (assuming that is the correct note syntax)

1 CENS
...
2 NOTE Relation to Head of House: Son

I would be grateful for anything you can do with this, please let me know if you need additional information
Regards
Graham

[tatewise]

Ah yes, sorry partly my mistake.
That is a side effect of the Change Any Fact Tag Plugin, which if the Fact it is changing has anything it cannot handle, such as the _UNCAT UDF, the Plugin moves it to a Source Note that logs the problem.
So it was an INDI.RESI._UNCAT field but becomes an INDI.CENS.SOUR field that logs the _UNCAT invalid tag.

However, that is easily detected, so the attachment Plugin now caters for both _UNCAT fields and SOUR fields that log _UNCAT invalid tags.

[GrahamJWood]

Mike,
Excellent job see attachment. With a handful of exceptions the only UDF tags left now are _APID or APID (Military service) ones which can stay. Thanks very much for your help.
Regards
Graham