Unknown info (line 916) 1 MARR 2 DATE 14 Jun 1916 2 PLAC York, York, Ontario, Canada 2 SOUR @S-2133199186@ 3 NOTE http://search.ancestry.ca/cgi-bin/sse.dll?db=ontariomarr1858-1899_ga&h=1188506&ti=5543&indiv=try&gss=pt 3 NOTE 3 DATA 4 TEXT Birth date: abt 1886 Birth place: Palmerston Ont Marriage date: 14 Jun 1916 Marriage place: York, York, Ontario, Canada 3 _APID 1,7921::1188506Every instance (1870) of the custom 3 _APID tag was excepted, as might be expected since it is a custom tag. No other exceptions were reported.

"Unknown info" exception on MARR fact import from Ancestry
#1
Posted 18 July 2012 - 01:15 PM
Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
#2
Posted 19 July 2012 - 10:04 AM
RootsMagic
#3
Posted 19 July 2012 - 12:49 PM
So, whatever the interpretation of the GEDCOM standard, Ancestry exports the Marriage fact as an Individual fact along with its source(s) as well as exporting a Marriage fact as a Family fact, depending on the order in which persons are created, coupled and sourced. The INDI MARR fact cannot be undone in Ancestry it would appear except by deletion of the fact from each person, creating the spouse if not existing, creating a family marriage fact "Marriage to spousename", going to the source(s) and detaching them from both persons, and then re-attaching the source(s).
As I and I'm sure others use Ancestry Trees to build pro tem trees for research, and collecting sources, I daresay there might be some justification in wishing that RootsMagic would support INDI MARRs. While one might be puritanical that a MARR fact is inherently a family fact and requires two people, the truth is that maybe we are only interested in the one side. Maybe RM could convert the INDI MARR to a FAMS MARR with an automatically generated "Unknown Spouse", thereby preserving the event and the source that is evidence of it.

Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
#4
Posted 20 July 2012 - 12:01 PM
Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
#5
Posted 20 July 2012 - 12:19 PM
RootsMagic
#6
Posted 22 July 2012 - 03:53 PM
Married on 14 Jun 1916 Married at York, York, Ontario, Canada SEX: SOUR @S-2133199602@ NOTE http://search.ancestry.ca/cgi-bin/sse.dll?db=ontario_births&h=1248382&ti=5543&indiv=try&gss=pt NOTE DATA TEXT Name: Adda Jennie Estella Wooldridge Birth: 28 Nov 1884 in Ontario, Canada Death: _APID 1,8838::1248382The inclusion of "SEX: SOUR" ff in the note appears to be a bug in LFT picking up some tags from the SEX block later in the GEDCOM.
The note added to her spouse was simply:
Married on 14 Jun 1916 Married at York, York, Ontario, Canadai.e., despite there being a source listed on Ancestry, and exported in its GEDCOM:
1 MARR 2 DATE 14 Jun 1916 2 PLAC York, York, Ontario, Canada 2 SOUR @S-2133199186@ 3 NOTE http://search.ancestry.ca/cgi-bin/sse.dll?db=ontariomarr1858-1899_ga&h=2058386&ti=5543&indiv=try&gss=pt 3 NOTE 3 DATA 4 TEXT Birth date: abt 1886 Birth place: Ballinsfad Ont Marriage date: 14 Jun 1916 Marriage place: York, York, Ontario, Canada 3 _APID 1,7921::2058386, LFT ignored the source in the Note. In both cases, however, the sources were attached to the Name and to the Birth events.
Of course, one would not want RM to duplicate LFT bugs, but you will get the idea of how the latter handles unrecognised or "invalid" GEDCOM tags without total rejection.
Tom user of RM7630 FTM2017 Ancestry.ca FamilySearch.org FindMyPast.com wiki, exploiting the database in special ways >>>
app, a bundle of RootsMagic utilities.
Also tagged with one or more of these keywords: GEDCOM, Ancestry.com, Import, Bug
General →
RootsMagic Wish List →
Gedcom exportStarted by BevSmallwood, 07 Nov 2020 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic 7 →
Discussion →
Gedcom export - everybody is marked as deadStarted by Jesper Beenfeldt Nielsen, 29 Feb 2020 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic 7 →
Discussion →
Review of RM compliance with GEDcom 5.1 - GEDcom assessment toolStarted by GalinAZ, 11 Feb 2020 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic for Mac →
WarningStarted by RWells1938, 31 Jan 2020 ![]() |
|
![]() |
||
Product Support - Current Versions →
RootsMagic for Mac →
Plan to Switch from FTM 2019 Mac to Rootsmagic 8 MacStarted by Rooty, 20 Nov 2019 ![]() |
|
![]() |