As currently designed, sources are applied at the event level. I concur that for shared events, not all sources will apply to every role for that event, therefore we need to be able to specify which role(s) a given source applies to.
-----Original Message----- From: Jenny M Benson [mailto:[email protected]] Sent: Sunday, March 30, 2014 5:30 AM To: [email protected] Subject: Re: [LegacyUG] Shared Events and Sources On 30/03/2014 08:50, MikeFry wrote: > On 30 Mar 2014 03:01, David Newton wrote: > >> >I think the advent of event sharing is making us think more >> >carefully about what we are sourcing. I think a halfway house here >> >would be to move the registration index to the marriage notes once >> >it's detail has been superseded, and of course it can still be sourced if >> >necessary. > Or, convert it into a separate, Marriage Event. I think your and David's ideas are good ones. I had thought of making BMD Registrations different Events to the actual BMDs but didn't want to "lose" them when they were the only dates I had for those Events. Moving them when they are superseded makes very good sense. That's one problem dealt with, but I am sure there will be other occasions when non-applicable Sources get copied to someone sharing an Event. -- Jenny M Benson 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
