GEDCOM Question
Moderator: MOD_nyhetsgrupper
GEDCOM Question
I used to import gedcoms indiscriminately between RootsMagic and
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Re: GEDCOM Question
You can import from PAF to either program; I think you can actually import
the PAF database itself to both programs; and it will keep what you entered
in PAF intact and unmolested.
I am not sure that will specifically solve your problem with how to import a
special tag specific to one program, though.
I am pretty certain Rootsmagic will let you create any tag your creativity
can dream up.
I wonder if you could create the tag and then be able to import from Legacy
with the extra field.
--
Yours,
Dora Smith
Austin, TX
[email protected]
"J. Hugh Sullivan" <[email protected]> wrote in message
news:[email protected]...
the PAF database itself to both programs; and it will keep what you entered
in PAF intact and unmolested.
I am not sure that will specifically solve your problem with how to import a
special tag specific to one program, though.
I am pretty certain Rootsmagic will let you create any tag your creativity
can dream up.
I wonder if you could create the tag and then be able to import from Legacy
with the extra field.
--
Yours,
Dora Smith
Austin, TX
[email protected]
"J. Hugh Sullivan" <[email protected]> wrote in message
news:[email protected]...
I used to import gedcoms indiscriminately between RootsMagic and
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Re: GEDCOM Question
On Sat, 07 Oct 2006 05:46:57 GMT, "Dora Smith"
<[email protected]> wrote:
If RM could import a name source and export back to Legacy as a name
source vice "Unspecified" I suspect Bruce would have told me how. If I
am the only one with the problem I don't expect it to be solved. I
think the problem is that Legacy considers "name" an event and RM does
not consider "name" a fact or event. I draw no conclusions as to
proper GEDCOM protocol.
There may be a way to create a "name" fact or event in RM that would
eliminate the problem but I have not tried and I may not be
accomplished enough to do it without expert advice.
I presently only use Legacy GEDCOMS and import to RM to look at and
print some reports. I never export RM GEDCOMS any more. I expect to
continue to upgrade both programs until I resolve the problem because
each has certain advantages.
Thank you for the comments.
Hugh
<[email protected]> wrote:
You can import from PAF to either program; I think you can actually import
the PAF database itself to both programs; and it will keep what you entered
in PAF intact and unmolested.
I am not sure that will specifically solve your problem with how to import a
special tag specific to one program, though.
I am pretty certain Rootsmagic will let you create any tag your creativity
can dream up.
I wonder if you could create the tag and then be able to import from Legacy
with the extra field.
If RM could import a name source and export back to Legacy as a name
source vice "Unspecified" I suspect Bruce would have told me how. If I
am the only one with the problem I don't expect it to be solved. I
think the problem is that Legacy considers "name" an event and RM does
not consider "name" a fact or event. I draw no conclusions as to
proper GEDCOM protocol.
There may be a way to create a "name" fact or event in RM that would
eliminate the problem but I have not tried and I may not be
accomplished enough to do it without expert advice.
I presently only use Legacy GEDCOMS and import to RM to look at and
print some reports. I never export RM GEDCOMS any more. I expect to
continue to upgrade both programs until I resolve the problem because
each has certain advantages.
Thank you for the comments.
Hugh
Re: GEDCOM answer
J. Hugh Sullivan <[email protected]> wrote:
Manipulation of a gedcom : RootsMagic 15 Legacy 11
see : Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
I used to import gedcoms indiscriminately between RootsMagic and
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Manipulation of a gedcom : RootsMagic 15 Legacy 11
see : Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
Re: GEDCOM answer
On Sat, 7 Oct 2006 21:34:03 +0400, [email protected] (Tehenne) wrote:
Je ne parle Francais. Merci.
Hugh
J. Hugh Sullivan <[email protected]> wrote:
I used to import gedcoms indiscriminately between RootsMagic and
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Manipulation of a gedcom : RootsMagic 15 Legacy 11
see : Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
Je ne parle Francais. Merci.
Hugh
Re: GEDCOM answer
J. Hugh Sullivan <[email protected]> wrote:
All the examples are in gedcom!
In made tests, RootMagics is globally better than Legacy.
In your case, it would be necessary to see the original gedcom
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
On Sat, 7 Oct 2006 21:34:03 +0400, [email protected] (Tehenne) wrote:
J. Hugh Sullivan <[email protected]> wrote:
I used to import gedcoms indiscriminately between RootsMagic and
Legacy to view different reports. I stopped because Legacy allows me
to source an individual's name and that is incompatible with RM. When
I import an RM gedcom back into Legacy the name source is removed from
the name and placed in "Unspecified".
The name is sourced in RM reports even thought there is not a separete
name source fact.
Is there a method to import into Legacy from RM and retain the name
source vice switching it to an entry that means nothing? I've spent
countless hours re-sourcing names and I'm not through yet.
Hugh
Manipulation of a gedcom : RootsMagic 15 Legacy 11
see : Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
Je ne parle Francais. Merci.
All the examples are in gedcom!
In made tests, RootMagics is globally better than Legacy.
In your case, it would be necessary to see the original gedcom
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
Re: GEDCOM answer
On Sun, 8 Oct 2006 06:11:54 +0400, [email protected] (Tehenne) wrote:
[snip earlier posts]
Actually when importing an RM GEDCOM Legacy assigns the correct source
to the name in the printed Descendant Narrative Report. But in the
fact list the source is in the event "Unspecified" vice the event
"Name". It probably doesn't make any difference except to a nitpicker
like me. RM does not have an event "Name".
I inserted a new fact "Name" in RM and the source came up right when
printed. But I did not see how to make a global entry to insert the
fact for thousands of people. And, even if I did, I'm not sure it
would GED back properly.
I'm not too interested in a workaround since it would probably be
time-consuming or complex or both.
I'm not sure what you mean by "made tests". Legacy is generally ranked
higher in ratings I have seen but in my opinion RM is just as good -
and faster.
Hugh
J. Hugh Sullivan <[email protected]> wrote:
[snip earlier posts]
Manipulation of a gedcom : RootsMagic 15 Legacy 11
see : Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
--
Téhenne Saint-Denis de la Réunion
Je ne parle Francais. Merci.
All the examples are in gedcom!
In made tests, RootMagics is globally better than Legacy.
In your case, it would be necessary to see the original gedcom
Actually when importing an RM GEDCOM Legacy assigns the correct source
to the name in the printed Descendant Narrative Report. But in the
fact list the source is in the event "Unspecified" vice the event
"Name". It probably doesn't make any difference except to a nitpicker
like me. RM does not have an event "Name".
I inserted a new fact "Name" in RM and the source came up right when
printed. But I did not see how to make a global entry to insert the
fact for thousands of people. And, even if I did, I'm not sure it
would GED back properly.
I'm not too interested in a workaround since it would probably be
time-consuming or complex or both.
I'm not sure what you mean by "made tests". Legacy is generally ranked
higher in ratings I have seen but in my opinion RM is just as good -
and faster.
Hugh
Re: GEDCOM answer
J. Hugh Sullivan <[email protected]> wrote:
I took one or several gedcom containing all the data recommended by the
format.
I read this gedcoms by programs, and then I exported results in a new
gedcom.
For example,
ORIGINAL and ROOTSMAGIC
1 NATI Malgache
1 PROP 3 cochons et 17 poules
LEGACY
1 EVEN Nationality
2 TYPE Nationality
1 EVEN 3 cochons et 17 poules
2 TYPE Property
or ...
ORIGINAL
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR Mairie annexe
2 ADR1 132 Allée de Turquoises
2 ADR2 Bellepierre
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
1 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
IMPORTED AND EXPORTED by LEGACY
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR Mairie annexe
2 CONT Saint-Denis, Île de la Réunion 97400 FRANCE
2 _NAME Archives Municipales
2 ADR1 Mairie annexe
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
2 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
2 CONT Saint-Denis, Île de la Réunion 97400 FRANCE
2 _NAME Le Bistrot du Coin
2 ADR1 3 rue Balzac
2 ADR2 16789 Bringuezac
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
IMPORTED AND EXPORTED by ROOTSMAGIC
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR 132 Allée de Turquoises
2 CONT Bellepierre
2 CONT Saint-Denis, Île de la Réunion 97400
2 CONT FRANCE
2 ADR1 132 Allée de Turquoises
2 ADR2 Bellepierre
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
2 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
2 ADR1 3 rue Balzac
2 ADR2 16789 Bringuezac
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
I'm not sure what you mean by "made tests". Legacy is generally ranked
higher in ratings I have seen but in my opinion RM is just as good -
and faster.
I took one or several gedcom containing all the data recommended by the
format.
I read this gedcoms by programs, and then I exported results in a new
gedcom.
For example,
ORIGINAL and ROOTSMAGIC
1 NATI Malgache
1 PROP 3 cochons et 17 poules
LEGACY
1 EVEN Nationality
2 TYPE Nationality
1 EVEN 3 cochons et 17 poules
2 TYPE Property
or ...
ORIGINAL
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR Mairie annexe
2 ADR1 132 Allée de Turquoises
2 ADR2 Bellepierre
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
1 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
IMPORTED AND EXPORTED by LEGACY
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR Mairie annexe
2 CONT Saint-Denis, Île de la Réunion 97400 FRANCE
2 _NAME Archives Municipales
2 ADR1 Mairie annexe
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
2 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
2 CONT Saint-Denis, Île de la Réunion 97400 FRANCE
2 _NAME Le Bistrot du Coin
2 ADR1 3 rue Balzac
2 ADR2 16789 Bringuezac
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
IMPORTED AND EXPORTED by ROOTSMAGIC
0 @R1@ REPO
1 NAME Archives Municipales
1 ADDR 132 Allée de Turquoises
2 CONT Bellepierre
2 CONT Saint-Denis, Île de la Réunion 97400
2 CONT FRANCE
2 ADR1 132 Allée de Turquoises
2 ADR2 Bellepierre
2 CITY Saint-Denis
2 STAE Île de la Réunion
2 POST 97400
2 CTRY FRANCE
2 NOTE Ouverture les jours ouvrés de 9h à 16h
0 @R2@ REPO
1 NAME Le Bistrot du Coin
1 ADDR 3 rue Balzac
2 CONT 16789 Bringuezac
2 ADR1 3 rue Balzac
2 ADR2 16789 Bringuezac
--
Téhenne Saint-Denis de la Réunion
Logiciel de généalogie ohmiGene (Mac & PC): http://www.nauze.com/
Comparatif Import-Export Gedcom : http://perso.wanadoo.fr/cajun/
Disget du format Gedcom : http://www.nauze.com/gmc/indexGED.html
Re: GEDCOM answer
On Sun, 8 Oct 2006 08:37:14 +0400, [email protected] (Tehenne) wrote:
I looked at the Legacy and RM GEDCOM. Each has a source for name but
they were different - which was not unexpected.
The difference is simply that Name in Legacy is an Event and Name in
RM is not a Fact/Event. Thus the Name fact is not imported as such in
RM and not Deported (Exported) as a Fact or Event. Said another way
the imported Name in RM is sourced just like Legacy but is not a
Fact/Event in RM.
For purporses of reports there is no difference in name and source
that I can distinguish so the difference appears to be programmer
preference. I think I am the problem - I like symmetry. But I really
can't expect Bruce and/or Legacy to service my eccentricity.
If there was a global way to delete the "Unspecified" source in Legacy
and move it to "Name" my whim would be served.
I appreciate your interest in my situation but, since there are no
other interested parties contributing, I am probably just wasting
bandwidth.
Merci beaucoup,
Hugh
J. Hugh Sullivan <[email protected]> wrote:
I'm not sure what you mean by "made tests". Legacy is generally ranked
higher in ratings I have seen but in my opinion RM is just as good -
and faster.
I took one or several gedcom containing all the data recommended by the
format.
I read this gedcoms by programs, and then I exported results in a new
gedcom.
For example,
ORIGINAL and ROOTSMAGIC
1 NATI Malgache
1 PROP 3 cochons et 17 poules
LEGACY
1 EVEN Nationality
2 TYPE Nationality
1 EVEN 3 cochons et 17 poules
2 TYPE Property
I looked at the Legacy and RM GEDCOM. Each has a source for name but
they were different - which was not unexpected.
The difference is simply that Name in Legacy is an Event and Name in
RM is not a Fact/Event. Thus the Name fact is not imported as such in
RM and not Deported (Exported) as a Fact or Event. Said another way
the imported Name in RM is sourced just like Legacy but is not a
Fact/Event in RM.
For purporses of reports there is no difference in name and source
that I can distinguish so the difference appears to be programmer
preference. I think I am the problem - I like symmetry. But I really
can't expect Bruce and/or Legacy to service my eccentricity.
If there was a global way to delete the "Unspecified" source in Legacy
and move it to "Name" my whim would be served.
I appreciate your interest in my situation but, since there are no
other interested parties contributing, I am probably just wasting
bandwidth.
Merci beaucoup,
Hugh