I would like to see immigration/emigration with "to" and "from" fields as well. It seems to be quite a lot of extra work to have to enter all these dual immigration/emigration pairs that would be handled more efficiently in one entry.
I was able to work around this by including the word "from" in the description followed by the location name. It gives me one entry in one place so I don't have to go back and forth trying to view the information that is really all part of one event. If they immigrate to a country, recording another event for emigration from a country really clutters up the database as well as reports. Recording a separate event for migration and emigration is like recording separate events for when a persons head was born, then when the body was born, and then when the feet finally arrived. Why on earth would we do that??? Rick > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 21, 2004 2:43 AM > Subject: [LegacyUserGroup DIGEST] > > > <<<<<<<<<<<<<<<<<<<<<<<<<<< LEGACY >>>>>>>>>>>>>>>>>>>>>>>>>>> > > From: "John R. Bayle" <[EMAIL PROTECTED]> > Subject: Re: [LegacyUG] 'Getting It Right' - migration > Date: Tue, 20 Apr 2004 07:18:48 -0400 > Reply-To: [EMAIL PROTECTED] > Ron wrote: > > > for Legacy "wish list" - for a emigration/immigration event, we need a > "to" > > and a "from" location - actually maybe 3 or 4 locations if one wishes to > > enter e.g. > > "from": Ansbach, Bavaria > > "embark port": Hamburg > > "debark port" New York, > > and > > "to": Erie, Pa" > > My practice for now that I don't use either emigration or immigration > > events, rather created one I call migration. > > I put the "from" in the description and the landing port in the > location, > > and whatever else desired in the Event notes. A little > tinkering with the > > sentence structure takes care of the rest. > > > > RonKZ > > I understand Ron's concerns, but think it would be a mistake for > Legacy (or any other gen program) to adopt the approach he's > advocating. I hope Legacy is not changed in the future as he > suggests for two reasons; 1) It's not needed; 2) It's not in keeping > with the GEDCOM Standard. > > I don't think it's needed because of the nature of events. An > event is a single thing that happens at one point in time at one place. > Legacy and the GEDCOM standard both define (properly IMO) > an Emmigration Event and an Immigration event, as separate events. > Undoubtedly these events are linked together in pairs in most cases, > but need not be so as in the case of a person dying on the ship after > emmigrating from Germany and before Immgrating to America. > People relocating from Indiana to California (say) also died on the > journey. > > As stated earlier the GEDCOM standard defines Emmigration and > Immigration events. For Legacy to come up with a third "Event", for > migration, allowing for a multiple (unlimited?) chain of movements > would be a totally new kind of "un-Event" not currently used by either > Legacy or the GEDCOM standard. I belive it's important to stick to > the GEDCOM standard as much as possible, by using events and other > items specified in that standard to maximize ones ability to share > information > with others, or even to move ones own data from one program to another > for oneself. You may not want to now, but things change. > > The situation Ron describes is IMO better handled by creating a series > of Emmigration : Immigration pairs than by using his proposed Migration > event. To describe his example above he would thus have 4 pairs of > Emmigration : Immigration events. Or if he wanted to reserve Emmigration > Immigration pairs for crossing international boundaries, he could use the > Residence event to note a couple of moves. > > Always ready with a contrarian viewpoint!? > > > Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
