FamilySearch is trying to standardize things, for obvious reasons, but I don't think they intend to impose that standard on any other programs or services. They are not trying to change genealogical standards; they are using set standardized locations so when you have someone in Chicago, it is recorded the same way for everyone in Chicago (Chicago, Cook, Illinois, United States) instead of Chiccago..., or Chicago, Illinois, USA or Chic., IL; it would be too intensive to get the computers to recognize all of the possible ways of recording that one city. These days the programs are recognizing the places and pointing you to maps and doing automatic searches. The only way to do that is to have standardized places. They don't care how you record it in your own personal family history software, but it is the smart thing to get in the habit of doing. Legacy allows us to record in any way that we want; the 'warnings' for various things can be turned off. Legacy will only warn us about problems if we want it to and it's a huge help to me to have Legacy keep an eye on my work :-)
Kathy On Tue, Jun 14, 2011 at 8:29 PM, Bob Vary <[email protected]> wrote: > Personally, I hope that Legacy never becomes so rigid that we won't have > the option to ignore standards if that is our wish or need. > > > -----Original Message----- > From: Kirsten Bowman [mailto:[email protected]] > Sent: Tuesday, June 14, 2011 9:31 PM > To: [email protected] > Subject: RE: [LegacyUG] webinar comment > > > There's no question that genealogical practice recommends using the name of > the place as it was at the time of the event (and in the language of the > place, if you want to go that far). I'm just wondering how that and other > location issues that Legacy allows will integrate with FamilySearch's goal > to standardize data entry of locations. From an earlier response I gather > that the standard can be ignored, but what's the use of a standard that is > ignored--or does the standard perhaps somehow take into account the > situations mentioned? > > Kirsten > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp<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<http://www.legacyfamilytree.com/Help.asp> > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog > (http://news.LegacyFamilyTree.com<http://news.legacyfamilytree.com/> > ). > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp<http://www.legacyfamilytree.com/LegacyLists.asp> > > > -- Kathy Meyer Technology is both blessing and curse, depending on what it's doing for you (or to you) on any particular day. 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
