I’d agree except that DSCR is handled fine. TITL is not. Both appear to be
valid gedcom 5.5 tags, and least in the standards I’ve found online, since 1995
from what I see, and I’d assume both would be processed the same way.
n DSCR <PHYSICAL_DESCRIPTION> {1:1} p.
+1 <<EVENT_DETAIL>> {0:1} p.
n TITL <NOBILITY_TITLE> {1:1} p.
+1 <<EVENT_DETAIL>> {0:1} p.
(Both have details, dates, etc.)
Legacy accepts the DSCR just fine, but ignores the TITL, considering each
instance of TITL a unique custom tag.
The reason I have Titles and not just Alt.Names is that the peerage acquired,
retained, and lost various titles over their lives, so dates are a prominent
fact of the title. Once using a witness feature, and now I think I could do
the same with share, I even linked the titles from predecessor, holder,
successor. So I could move up and down the change of “Earls of Suffolk” for
example, from the 1st to the nth.
Not sure if I can do a bulk change of every TITL to EVEN-STYLE in RM.
I must have nearly 3,000 TITL entries in my gedcom. That’s 1) a lot of data
that’s suddenly lost, and 2) a lot of trash in my events selection.
If TITL were a custom, user-made, tag, I’d understand having to format it like
Style which comes through as EVEN-STYLE.
What’s funny is that all the rest of my old custom tags came through just fine
as custom tags. (Like my Style, Arms, Annals 4M, and so on.) What I can’t
account for is TITL is transferred out of RM as a gedcom tag but Legacy won’t
accept it as a standard gedcom tag, and since it’s not formatted as a custom
tag (which it isn’t) it makes a mess of it and treats each instance as a new
unique custom tag.
Any ideas of how to convert some 3,000 1 TITL entries into 1 EVEN 2 Title and
retain the text would be great.
I’m confident I can’t do it in RM, it would require some fancy text replacement
machinations in GedPAD, and while MS Access 2013 will open all the tables, a
primer on what table I should tackle to affect the changes (not the first time
I’ve worked a massive database into shape) I’d try it.
Sorry to belabor this, but where was the information regarding which of the
standard gedcom tags Legacy supports and which they don’t. For a program with
surprising attention to detail this seems to be a big issue. (Or I’m not
familiar enough with it to make the fix myself.)
From: Paul Gray [mailto:[email protected]]
Sent: Wednesday, April 9, 2014 7:58 AM
To: [email protected]
Subject: RE: [LegacyUG] Bad TITL import
Hello Robert,
If I understand you correctly, you want ‘events’ or ‘facts’ called title. In
your first export example that did not work as you wished , the level 1 tag is
not 1 EVEN.
Looking at the second example that did work as you wanted, level 1 is EVEN and
level 2 is TYPE of ‘Style’.
If you want Legacy to treat them them the same (create events or tags) I would
think the export would need to have level 1 of EVEN and level 2 of TYPE with
value of Title or something similar.
To create an event/fact for title, I suspect Legacy needs level 1 needs to be
EVEN.
Paul Gray
From: Robert Stewart [mailto:[email protected]]
Sent: April-08-14 11:58 PM
To: [email protected] <mailto:[email protected]>
Subject: [LegacyUG] Bad TITL import
TITL is a standard Gedcom 5.5 tag.
>From the gedcom I exported from RootMagic 6 and imported into Legacy 8, I have
>two examples of titles. One uses the TITL tag, the other was a custom tag I
>created called Style.
1 TITL Earl of Mercia
2 DATE ABT 886
2 SOUR @S438@
3 PAGE pg. xlix
3 _TMPLT
4 FIELD
5 NAME Page
5 VALUE pg. xlix
This is how it is exported.
But upon being imported by Legacy, “Earl of Mercia” is now the tag. (And the
1000s of other titles I’ve created are now also custom tags, each one of them,
quite obscuring the “real” tags I want to use.)
I also, at some point, created a tag, called it Style, and it imported
correctly.
It works, it displays as it ought to, and I’ve got a Style tag on the list to
choose from, build a sentence around, etc.
1 EVEN
2 TYPE Style
2 DATE 1177
2 NOTE Dei Gratia Rex Anglorum, dux Normannorum, dux Aquitanorum et comes Ande
3 CONC gavorum, dominus Hiberniae
I understand that this is still an EVENT but the type has the event called
Style where a name is required.
But TITL is on the same level as EVEN (Will, Probate, etc.) in the gedcom 5.5
standard. Why isn’t it treated the same way by Legacy?
TITL {TITLE}: =
A description of a specific writing or other work, such as the title of a book
when used in a source context, or a formal designation used by an individual in
connection with positions of royalty or other social status, such as Grand Duke.
EVEN {EVENT}: =
A noteworthy happening related to an individual, a group, or an organization.
TYPE {TYPE}: =
A further qualification to the meaning of the associated superior tag. The
value does not have any computer processing reliability. It is more in the form
of a short one or two word note that should be displayed any time the
associated data is displayed.
Another example:
1 TITL Lieutenant-Colonel, U.S. Army
2 DATE 20 FEB 1968
2 SOUR @S485@
3 _TMPLT
4 FIELD
5 NAME Page
Created a tag called “Lieutenant-Colonel, U.S. Army”.
1 DSCR Height 6 ft 2 in, Weight 185 lbs, Color of Eyes Blue, Color of Hair Red/B
2 DATE 3 MAY 1972
2 SOUR @S460@
3 _TMPLT
4 FIELD
5 NAME Page
Does not create a tag called “Height 6 ft 2 in, Weight 185 lbs, Color of Eyes
Blue, Color of Hair Red/B”.
I don’t see how I can make RootsMagic export these TITLs more “properly” into a
gedcom that Legacy will read and process correctly so that these 1,000s of
titles, now tags, are all handled by one tag called Title.
Creating a dummy file in Legacy, and looking to add tags, I see 62 tags to pick
from, albeit Title is not one of them. Physical Description (DSCR) is.
Is there software that will convert
1 TITL Lieutenant-Colonel, U.S. Army
in a gedcom to
1 EVEN
2 TYPE Title
2 NOTE Lieutenant-Colonel, U.S. Army
That’s where LTools could come in? A global replace, with wildcards, and
multiple lines?
_____
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2014.0.4355 / Virus Database: 3882/7318 - Release Date: 04/08/14
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
