Ward, You are not alone in the desire to want Legacy to export *your* data cleanly. You arguments are valid.
On Fri, Dec 6, 2013 at 1:31 PM, Ward Walker <[email protected]> wrote: > Jay, I have reread this several times and cannot understand what point > you are making. > > 1. To clarify, I have not exported any data to any online software. My > point was simply that it makes no difference whether my newly-found cousin > maintains their tree online or on their computer. If they want to add my > branch of the family, I need to create a GEDCOM export. > > 2. I hope it is clear to all that when Legacy exports SW sources to > GEDCOM, it irreversibly changes the data (in the process of creating > GEDCOM-compatible, ‘basic’ style sources). There is nothing that the target > software can do about it. The desired formatting of the citation cannot be > recreated, even if re-imported to Legacy. > > 3. How could this be resolved? It sounds like there are two approaches: > (a) bury the intelligent formatting data in custom GEDCOM codes that > certain target systems are then programmed to unbury and use; or (b) make > do with a compromise workaround that is transparent to the target system > and thus works for all target systems. The latter is what I had been > advocating, for SW. > > The Subject line is about Shared Events. Today’s e-mails raise questions > about whether there is even a problem. Leonard’s observation suggests that > perhaps approach (b), above, has already been implemented for this feature. > (That would be that, while the structure of shared events is lost, at least > the events are copied to all applicable individuals.) And yesterday’s > comments suggest that approach (a) was also done, for RM. > > Ward > > *From:* Jay 1FamilyTree <[email protected]> > *Sent:* Thursday, December 05, 2013 11:00 PM > *To:* [email protected] > *Subject:* Re: Exporting Shared Events [WAS: Re: [LegacyUG] Shared vital > Events] > > I will add one comment on this subject and then move on.... > > In one of the previous messages was stated > > > Collaborating Online: I would think that exporting a significant chunk of > Legacy data to a web-based tree usually involves the same GEDCOM > interchange, aside from special implementations like FamilySearch Family > Tree. Anyway, if a newly-found cousin/researcher wants to import a > significant portion of my tree, seeing it online won’t help them. I have > to send them a file. Usually they barely know how to operate the software > that they have (often FTM) and are not open to starting over with a new > product just to accommodate me. If their tree is only online (e.g., > Ancestry), then yes, they could grant me access to add my branch > interactively. Painful. > > > The reason you have to send your new cousin / researcher a file, is > because whatever online software you exported your Gedcom to > did NOT properly import or use all of the data that was in a Legacy > created gedcom. > > > 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 > -- James Cook GED Utils, Ancestry Utils http://loosestacks.blogspot.com/ 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
