Try two (2) commas before Regards Laurence E Stephenson
------ Original Message ------ From: "magnoliasouth" <[email protected]> To: [email protected] Sent: 14/04/2014 7:37:52 AM Subject: Re: [LegacyUG] Location merging >Many, MANY thanks for the suggestions and the "sorry but you'll just >have to deal with it" answers. I appreciate the sentiments. lol! > >Oh and when I said 300, I meant 300 ways of Sumter County. lol! Who >knew? > >The search function doesn't appear to work properly either. To prove >the problem, I'll do my screen caps again. The short answer is that >I'll have a location that says Franklin, AL and when I go to replace >AL with Alabama it says there were 0 replacements, AL was not found. >REALLY???!!! It's all over the place! > >The list that displays the AL example above: http://goo.gl/5TjOsa >The operators I used to search and replace: http://goo.gl/6eO9ph >The results: http://goo.gl/JSRf3Y > >Oh and I if I remove the comma, it still says 0 replacements. I >thought maybe that was a problem, but alas, it was not. > >Anyway, because you were all so kind as to respond, I have responded >to each of you below. Hopefully I missed no one. :) > >On Sun, Apr 13, 2014 at 5:42 AM, Cathy Pinner <[email protected]> >wrote: >> >> Instead of merging each one to your final choice, you could merge the >> ones that are near each other first. >> However, with the examples you provide, they'd all be together if >> you were sorting left to right instead of right to left - but you >> probably have a number of towns included as well. > >I do. I saw that as an issue. There really needs to be a csv Location >merge function. There is no reason not to have one. You could then >also turn options on and off to match anything between commas. This >way it wouldn't mess up any entries with towns in them. > >I fully expected it to have this funciton and was very surprised it >didn't exist. I also felt like the replace function would work, but it >doesn't, as I mentioned above. > >On Sun, Apr 13, 2014 at 6:05 AM, C.G. Ouimet <[email protected]> >wrote: >> Yes CSV's for all list outputs would be good ... >> >> >> C.G. Ouimet >> Kingston ON > >That's exactly what I was wanting (I agree about the events too). I >was disappointed to find that a report of my locations required only a >pdf, but it also forced me into accepting (at the minimum) how many >individuals each was assigned to. I couldn't care less about that. All >I want is a report of locations. Anyway, the functionality of csv is >much better in fixing problems like this than whatever it is that this >does. > > >On Sun, Apr 13, 2014 at 7:02 AM, David Newton ><[email protected]> wrote: >> There is a way to tag all the locations containing Sumter but what >>you >> can do with the list after that I do not know. >> David > >LOL! Yeah, I agree. I like the functionality of the Master Source >view. You can tag certain sources then hide those not tagged. Then you >can merge and do whatnot. Now THAT was extremely helpful. I was very >pleased with how that worked out and it was simple. > >I could see something similar here. Tagging everything that says >Sumter then hiding all the other stuff so I can fix that one area. In >fact, if it had worked that way, I wouldn't have asked for any help on >the list. > >On Sun, Apr 13, 2014 at 9:09 AM, singhals <[email protected]> wrote: >> To reduce the pain a bit, though, you can select the version >> you want, copy the info, then just paste it over the other >> source names and then merge dupes. IME, it keeps the detail >> on each and saves a lot of rekeying. >> >> Cheryl > >I don't know why, because it sounds so simple, but this confuses me. >Wouldn't merging duplicates keep the details? Oh wait. I think I >understand what you mean. You mean copy/paste the location name I like >such as copying , , Sumter County, Georgia and pasting it over Sumter >Co., GA. > >I agree, that's the least painful way and that's what I did day before >yesterday and it took HOURS. I literally spent 8 hours fixing all my >locations. The unfortunate thing was that I realized there were a lot >of individual merges that weren't right, so I had to resort to going >back to the original file and starting all over again. I tell you, I >cried real tears. Real! > >On Sun, Apr 13, 2014 at 9:26 AM, David Abernathy ><[email protected]> wrote: >> Have you edited these entries with errors per the instructions from >>the Help? >> >> Combining Duplicate Locations >> >> When correcting misspelled place names, you may find that you end up >>with duplicates within the Master Location List. To remove these >>duplicates and clean up the list, choose the Combine option. Legacy >>then goes through the list, combines the duplicates and moves the >>links. >> >> Thanks, >> David C Abernathy > >Yes, thank you. In my original message I explained why that wasn't >working for me. The problem is the 300 same place names and scrolling >through thousands to go back and forth. > >On Sun, Apr 13, 2014 at 10:27 AM, Bob Austen <[email protected]> >wrote: >> Using Search and Replace might help you in this situation. >> Bob A > >You are so kind for those instructions and that was what I was hoping >for most. However the search didn't work for me for some reason. I >have screen caps above that you can take a look at and see what I >mean. > >Honestly, I thought I was in the twilight zone. Last night I went to >Findagrave.com and did a search with a name, location and death date >and it said zero results. I went to Google and had it search >Findagrave.com, entered the exact same information and it found what I >entered. lol! I was like "well maybe my computer is just in total love >with Google and refuses to search any other way." lol! ;) > >On Sun, Apr 13, 2014 at 3:25 PM, Jay 1FamilyTree ><[email protected]> wrote: >> I created a cvs spreadsheet and used that externally to group my >>common >> places. >> At least then I knew what to look for in the Legacy location listing. >> And I have over 5,000 locations... > >That's an interesting idea. You don't feel you're duplicating >information that way? > >I would love it if we could export a cvs list of locations, then >import and merge those. Wouldn't that be ideal? > >On Sun, Apr 13, 2014 at 1:09 AM, magnoliasouth ><[email protected]> wrote: >> I have a horrible list of locations. I understand how to combine >> locations, but that's not working for me. It involves way too much >> scrolling up and down and all around. Also, the "find" at the top >> isn't finding anything. It only looks for the first word which >>doesn't >> help me. >> >> What I need to do is do a search for one word and get a list of all >> locations that have that word in its various forms. For example: >> >> Let's say I want to search for Sumter. >> >> I want to get all of the results like this: >> >> Georgia, Sumter >> Georgia, Sumter County >> Georgia, Sumter Co. >> GA, Sumter >> GA, Sumter County >> USA, GA, Sumter >> USA, GA Sumter County >> USA, Ga. Sumter County >> United States, Georgia, Sumter >> Sumter >> >> You see the problem and I use this one because it's my worst >> nightmare. Sumter is all over the place and some location entries >> don't even have anything else in them. >> >> Now as you can see, when I have 300 locations and they're sorted they >> are at the top the middle the end and so on. Scrolling take WAY too >> long and that's just not an option. I'd rather not bother if I have >>to >> do it that way. >> >> How can I fix this? Please, tell me there is an easy way? >> >> Many thanks. :) >> >> >> >> 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 >> >> > > > >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 > > 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
