Rich in LA, I am not suggesting a soundex type search, but I can see some merit to it. All I am asking for is a simple index sort on birth date. Other genealogical programs have had that popular option for years.
Chick in Ventura On Tue, Aug 4, 2009 at 7:06 AM, RICHARD SCHULTHIES<fourpa...@verizon.net> wrote: > > What I may be hearing is a request for a variation of Soundex (first used on > US Census) tool. Using Search; Individual; Sounds like; Querido; would not > find Kerido nor Crudo either, but that is not the computer's nor the > program's fault. We have to go in the past and teach our ancestors how to > spell, and use exactly one name. > The other choices for 'Sounds Like' are 'Contains'; 'Starts with'; and Wild > card. It is already there. > Rich in LA CA > > --- On Mon, 8/3/09, Chick Lewis <cglewi...@gmail.com> wrote: > >> From: Chick Lewis <cglewi...@gmail.com> >> Subject: Re: [LegacyUG] Things I Would Like to See >> To: LegacyUserGroup@legacyfamilytree.com >> Date: Monday, August 3, 2009, 7:53 PM >> Ron, >> >> I agree the wildcard could be an additional feature, but a >> wild card >> search for the name Querido, which is the one I was looking >> for, would >> never turn up either Kerido or Crudo. However, those two >> names with >> similar birth dates stood out when the index was sorted on >> birth date >> and immediately raised a flag. >> >> When I am trying to find an elusive ancestor and know his >> birth date >> or approximate birth date, I use FTM to sort my DB by >> birth, and then >> look for a likely name in that date range. >> >> On occasion I have found a name that wasn't even close to >> the one I >> was looking for, but I recognized it as a family name. >> Further >> investigation found that person was living with a relative >> and using >> their name. Subsequent records proved that person was the >> missing >> ancestor. >> >> I agree that it can be done in Legacy using a date range in >> search and >> find, but just sorting the db by birth date is so much >> easier and >> simpler. >> >> As I'm sure you are aware, some cultures use the mother's >> maiden name >> as the family name and as you trace back in time you will >> find that >> they are sometimes interchanged. Surnames can also change >> from country >> to country and in some places didn't even exist before >> 1800. When >> tracing Jewish ancestry it gets even more complicated and >> multiple >> surnames may be found in the same family. I have seen cases >> where two >> brothers have different surnames. >> >> The ability to sort on birth date is a proven tool. >> >> Chick >> >> >> >> On Mon, Aug 3, 2009 at 5:44 PM, ronald ferguson<ronfe...@msn.com> >> wrote: >> > >> > Chick, >> > >> > I guess I did not express myself too well, the >> wildcard was suggested as an additional feature. >> > >> > Let us be realistic, one doesn't need any names at all >> to search by birth date, if two or more people are born on >> 16 Jan 1725 the odds are they are the same person or twins. >> This is not the problem. The problem arises mainly when the >> dates are different or no dates are available for at least >> one of the people. >> > >> > In the first case additional proof is needed to >> confirm, or otherwise, but if the names are miles apart in >> the list, and they could be if there is no date of birth, >> they may well not even be noticed if the name is different - >> unless wildcards are used. For example I commonly use F?rg* >> for my surname because of all the variations (and even that >> doesn't cover all of them!). >> > >> > >> > >> > >> > Ron Ferguson >> > >> > >> _____________________________________________________________________ >> > >> > Tutorials: Programme of adding videos commenced >> > http://www.fergys.co.uk/ >> > View the Grimshaw Family Tree at: >> > http://www.fergys.co.uk/Grimshaw/ >> > For The Fergusons of N.W. England See: >> > http://myweb.tiscali.co.uk/fergys/ >> > >> _____________________________________________________________________ >> > >> > >> > >> > >> > >> > ---------------------------------------- >> >> Date: Mon, 3 Aug 2009 16:30:25 -0700 >> >> Subject: Re: [LegacyUG] Things I Would Like to >> See >> >> From: cglewi...@gmail.com >> >> To: LegacyUserGroup@legacyfamilytree.com >> >> >> >> Ron, >> >> >> >> I raised this question again because I think it is >> important and is a >> >> strong feature if understood and used properly. >> With all due respect, >> >> (and I do respect your judgement, advice and >> excellent posts) your >> >> suggestion of using wild cards in the name in >> conjunction with a birth >> >> date search is at best a clumsy way of detecting >> possible duplicates. >> >> In the case of Rebecca's example of a Thomas >> Hughes b. 16 Jan 1725 and >> >> a T. Wilson Hewes b. 16 Jan 1725, they would stand >> out as a possible >> >> duplication by doing nothing more than sorting on >> birth date. In >> >> another example, I had a David Kerido and a >> floater Dave Crudo in my >> >> data base, both with close, but not exactly the >> same birth dates. When >> >> I sorted the index on birth date, the similarity >> was evident. Upon >> >> further investigation they turned out to be the >> same person. >> >> >> >> Chick >> >> >> >> >> >> On Mon, Aug 3, 2009 at 3:32 PM, ronald ferguson >> wrote: >> >>> >> >>> Chuck, >> >>> >> >>> We have had this discussion before, and I >> wonder why you have raised it agin. There is, as you know, a >> way of putting in an enhancement request on the Legacy Home >> Screen. >> >>> >> >>> For me, I would not wish to use this facility, >> and it would, therefore be program bloat. BTW, you did not >> indicate it would be "optional" in your first post. >> >>> >> >>> I do not agree with your comment regarding the >> use of search; if it is used properly, one can, for example, >> use wildcards in a name should you wish, and use it in >> conjunction with a date of birth. Much more useful and more >> pwerful then your proposal. >> >>> >> >>> Even in the indexes you can get all the people >> will the same surname, in date of birth order by selecting >> the RIN of the individual you wish to use as standard and >> then click the surname button at the top. >> >>> >> >>> >> >>> >> >>> Ron Ferguson >> >>> >> >>> >> _____________________________________________________________________ >> >>> >> >>> Tutorials: Programme of adding videos >> commenced >> >>> http://www.fergys.co.uk/ >> >>> View the Grimshaw Family Tree at: >> >>> http://www.fergys.co.uk/Grimshaw/ >> >>> For The Fergusons of N.W. England See: >> >>> http://myweb.tiscali.co.uk/fergys/ >> >>> >> _____________________________________________________________________ >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> ---------------------------------------- >> >>>> Date: Mon, 3 Aug 2009 14:58:19 -0700 >> >>>> Subject: Re: [LegacyUG] Things I Would >> Like to See >> >>>> From: cglewi...@gmail.com >> >>>> To: LegacyUserGroup@legacyfamilytree.com >> >>>> >> >>>> Ron, >> >>>> Why wouldn't you want the program to >> detect a possible duplicate when >> >>>> the name is entered? It could be a great >> time-saver and its use >> >>>> optional. As to the Search>Find option, >> I think we had this >> >>>> discussion once before. It does work in a >> round-about sort of way but >> >>>> is not the same thing and not near as >> effective. Rebecca gave an >> >>>> excellent example of this. >> >>>> >> >>>> Chick >> >>>> >> >>>> >> >>>> On Mon, Aug 3, 2009 at 12:26 PM, ronald >> ferguson wrote: >> >>>>> >> >>>>> Chick, >> >>>>> >> >>>>> I wouldn't want the first and the >> second you can already do by using the >> Search>Find>Detailed Search option. >> >>>>> >> >>>>> >> >>>>> >> >>>>> Ron Ferguson >> >>>>> >> >>>>> >> _____________________________________________________________________ >> >>>>> >> >>>>> Tutorials: Programme of adding videos >> commenced >> >>>>> http://www.fergys.co.uk/ >> >>>>> View the Grimshaw Family Tree at: >> >>>>> http://www.fergys.co.uk/Grimshaw/ >> >>>>> For The Fergusons of N.W. England >> See: >> >>>>> http://myweb.tiscali.co.uk/fergys/ >> >>>>> >> _____________________________________________________________________ >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> ---------------------------------------- >> >>>>>> Date: Mon, 3 Aug 2009 12:15:13 >> -0700 >> >>>>>> Subject: [LegacyUG] Things I Would >> Like to See >> >>>>>> From: cglewi...@gmail.com >> >>>>>> To: legacyusergroup@legacyfamilytree.com >> >>>>>> >> >>>>>> I have been using Legacy for >> almost a year now (since V7 came out.) >> >>>>>> My previous program was Family >> Tree Maker. Following are two features >> >>>>>> that I would like to see >> incorporated into Legacy: >> >>>>>> >> >>>>>> 1. The ability for Legacy to >> recognize a possible duplicate person >> >>>>>> when he/she is being entered. I >> search for duplicates quite often >> >>>>>> because I have inadvertenly >> entered a person without realizing he/she >> >>>>>> is already in my database. I know >> how to use the merge function and >> >>>>>> search for duplicates, but it >> would be nice if Legacy would "catch" a >> >>>>>> duplication when the name is being >> entered and warn that it is a >> >>>>>> possible duplicate. >> >>>>>> >> >>>>>> 2. The ability to sort/search the >> index by birth date as well as >> >>>>>> alphabetically or by RIN. This is >> one feature of FTM I really miss. I >> >>>>>> often found people who were the >> same, but had their names spelled >> >>>>>> slightly different. Comparing >> individuals by birth date rather than >> >>>>>> name will sometimes reveal the >> existence of an un-connected individual >> >>>>>> with a different name or name >> change. I have had several instances >> >>>>>> where I have been able to connect >> individuals to families by comparing >> >>>>>> birth dates. >> >>>>>> >> >>>>>> If enough of us request these >> features, maybe the powers to be will >> >>>>>> incorporate them into the next >> upgrade. >> >>>>>> >> >>>>>> Chick Lewis >> >>>>>> California >> >>> >> > >> _________________________________________________________________ >> > Windows Live Messenger: Thanks for 10 great >> years—enjoy free winks and emoticons. >> > http://clk.atdmt.com/UKM/go/157562755/direct/01/ >> > >> > >> > Legacy User Group guidelines: >> > http://www.LegacyFamilyTree.com/Etiquette.asp >> > Archived messages: >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> > Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp >> > >> > >> > >> > >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp >> >> >> >> > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
