It appears that Cathy is pointing me towards what I want and TNG will accept custom tags as well. Yes, a separate tree would seem the likely solution BUT, the surname is the same as my family focus, just not from the same individual. However, in multiple instances the families ARE actually related due to marriages so I want them as part of the same tree, just want to have an identifier that says the surname is not descended from the same original couple.
All said, I think I've got it. I only wish there were a more blatant way to make that identification on the LFT individual screen. But, since the current tag color can be changed, it works... Thanks for the input -----Original Message----- From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On Behalf Of Ward Walker Sent: Tuesday, May 12, 2020 4:02 PM To: Legacy User Group Subject: Re: [LegacyUG] Exporting to Gedcom with Hashtag information - Identifying specific individuals Larry, If they are not related, then you would not stumble upon them while traversing your main tree in Legacy, except when searching or using master lists. If your focus is your TNG site, then it seems to me that using multiple trees in TNG would be ideal - and separate Legacy files. I have 4 TNG sites, one per grandparent. But I only have one main Legacy file, plus small files for separate trees much like yours. For example, members of my Ward line have Y-DNA matches with descendants of another Ward line. We do not know who the common ancestor is. I created a separate Legacy file to model that other line. On TNG, my Ward site has two trees, one from an export of just the Ward line from my main Legacy file, and the other from that separate file. On the TNG site, each Individual information page clearly shows which tree that person is in. Same with search results. Ward -----Original Message----- From: Cathy Pinner Sent: Tuesday, May 12, 2020 10:41 AM To: Legacy User Group Subject: Re: [LegacyUG] Exporting to Gedcom with Hashtag information - Identifying specific individuals Larry, No you can't get the background to change colour etc. You can include your hashtag as one of your 5 fields that display on Family View. You can use the Legacy style gedcom with TNG. In fact I think it's recommended that you do. Hashtags can be included in it and displayed on TNG. Sorry I don't do it myself but know that it is done. When you choose the Legacy style and then see the the list of tags exported under the Customise button, you'll see it includes Hashtag. Cathy > Larry Lachance <mailto:la...@lachance.org> > Tuesday, 12 May 2020 10:33 PM > > I am looking for suggestions/best way to handle – this is a combination > question that involves Legacy Family Tree and TNG The Next Generation of > Genealogy Sitebuilding. > > For more than 20 years everything with my tree has been great but, as in > life, “stuff happens”! > > I want to add a large group of individuals to my Legacy database who share > the same surname BUT are not descended from the “original immigrant” and > in fact, they are not actually related as they are descended from a > completely different surname. Actually this group “should be” a separate > family tree but that’s not what I want to do because I want them IN my > tree because of the common surname today. > > What I want is a way to “tag” or “hashtag” or place a marker or color on > the “family view” for anyone related to this particular name such that it > is immediately clear that the individual is of another family group. I > suspect this can be accomplished by using the tag or hashtag feature > without issue but I’d prefer a change in color, or a big exclamation point > on the screen to tell me “this individual is from the OTHER family” which > makes for quick ID purposes. I know I can change the colors of the “tag” > based on which tag I’m using but I’d like a blatantly obvious change like > changing the background color of the Name field in the Family View based > on the tag or hashtag used??? Is this even possible? > > Something like the above would remedy my Legacy question but... > > …then there is the hard part (that’s because I’m not sure how to do it or > even it’s possible) – I want to be able to export the file to a standard > GEDCOM 5.5.1 file AND have those individuals I’ve identified somehow > marked such that when I “publish” the GEDCOM to my TNG – The Next > Generation online database, those I have tagged are separately > identified. Is it possible that using a custom event, such as already > exists like _TAG Record Tag 1, would work? > > I will also post this query to the forum related to the other database for > input. > > Suggestions appreciated… > > Larry Lachance – www.lachance.org/genealogy > <http://www.lachance.org/genealogy> – Jacksonville, FL > > ** > > > -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ -- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
