Ward, No, the event note does not show up on other persons, and I agree with others that the Primary Person should be given a role, which currently is not part of the shared event software. In the example I would have wanted to assign Martin Peters as Head of Household.
AND, I think that the "Role Definitions" should become "Global" settings and not start from scratch with every new file. On Fri, Dec 6, 2013 at 1:37 PM, Ward Walker <wnkwal...@rogers.com> wrote: > OK. Now I see. Both Leonard and Kristry were correct. The export uses > custom tags that Legacy, RM, and perhaps future products can use to > intelligently import Shared Events. All other target systems that only > import standard GEDCOM tags would ignore these custom tags and thus only > associate the event with one individual. > > Now, back to the earlier question. Is it reasonable to expect Legacy to > also implement an export option that serves as a workaround for all these > other target systems? Such a workaround would avoid custom tags and would > copy the event to the other individuals, but it would also have to somehow > add an indication of the role, in order to avoid confusion. > > A related question (I hesitate to ask): What happens now if you link a > Legacy individual involved in a shared event with an individual in > FamilySearch Family Tree? > > Ward > > P.S.: Jay, does your event Note (Listed as Head of H.) show up for each > person in the share? I think someone commented a while back about a need > for a role for the primary individual. Is this an example? > > *From:* Jay 1FamilyTree <1familytree....@gmail.com> > *Sent:* Friday, December 06, 2013 2:40 PM > *To:* LegacyUserGroup@LegacyUsers.com > *Subject:* Re: [LegacyUG] Shared events > > Leonard is correct. > > The event share is exported in the Gedcom as part of the primary person. > > The problem is that no other pieces of software other than RootsMagic and > Legacy, know how to handle the data in the Gedcom when importing that data. > Just because the data is in gedcom format, doesnt mean the software KNOWS > what to do with it. > > A snippet of a gedcom might look like this > > 0 @I793@ INDI > 1 NAME Martin Albert /Peters/ > 2 GIVN Martin Albert > 2 SURN Peters > 1 SEX M > 1 BIRT > 2 DATE 9 Sep 1878 > 2 PLAC Appleton, Outagamie, Wisconsin, USA > 1 DEAT > 2 DATE 2 Aug 1960 > 2 PLAC Portland, Multnomah, Oregon, USA > > 1 EVEN > 2 TYPE 1920 Census > 2 DATE 1920 > 2 PLAC Portland, Multnomah, Oregon, USA > 2 NOTE Listed as Head of Household age 42. > 2 _SHAR @I908@ > 3 ROLE son > 2 _SHAR @I909@ > 3 ROLE daughter > 2 _SHAR @I697@ > 3 ROLE wife > 2 _SHAR @I907@ > 3 ROLE son > > 1 OCCU Unknown > 2 DATE Bef 2 Aug 1960 > 1 CHAN > 2 DATE 6 Dec 2013 > 3 TIME 11:09 > 1 FAMS @F345@ > 1 NOTE @NI793@ > > > So within the events for Martin, it lists the persons that event is shared > with and their role. > The gedcom does not list the event within the events of each of the shared > persons. > > Hope that helps clear things up. > > Jay > > > On Fri, Dec 6, 2013 at 10:46 AM, Ward Walker <wnkwal...@rogers.com> wrote: > >> Interesting. So what is the difference between Leonard’s observations >> and what Kristy reported yesterday morning? They seem contradictory. >> >> Ward >> >> *From:* Leonard Johnson <legacy8.swed...@gmail.com> >> *Sent:* Friday, December 06, 2013 11:24 AM >> *To:* LegacyUserGroup@LegacyUsers.com >> *Subject:* Re: [LegacyUG] Shared events >> >> Ron, Cheryl et al, >> >> I have used Shared Events often. Ron you wrote ".....for those who >> export their database via GEDCOM is that the shared event exports as a >> single event for the primary participant only. It does not export for >> those sharing the event." You are correct in that it exports for the >> "primary participant" however it also exports for all others that share the >> same event. I have checked this out for shared events, the GEDCOM contains >> not only the primary participant it even contains the events that are >> shared by others. >> >> Have a nice day, >> >> >> Leonard Johnson-Källbom >> > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
