Author Topic: Names which cause problems with searches....  (Read 18611 times)

Offline peterfelgate

  • RootsChat Extra
  • **
  • Posts: 24
  • My grandparent's wedding, August Bank Holiday 1906
    • View Profile
Names which cause problems with searches....
« on: Wednesday 15 September 10 23:46 BST (UK) »
Why do I keep finding surnames that are common words and which cause havoc when searching genealogy sites as they so often are used in the text of messages?  So far I have Day and Branch, and Moth keeps finding "mother"!

Anyone else have similar examples?
Felgate/Day/Branch Essex/Suffolk
Daley/Pryor Essex
Pearson Warwicks
Parker Surrey/Berkshire/Hampshire borders
Spiers Mid Hampshire

Offline JayG

  • RootsChat Aristocrat
  • ******
  • Posts: 1,326
    • View Profile
Re: Names which cause problems with searches....
« Reply #1 on: Wednesday 15 September 10 23:51 BST (UK) »
Know exactly what you mean.

I'm looks for Falls, Parrott, Sparrow, Sivers to name a few!

Jay

Offline jericho

  • RootsChat Marquessate
  • *******
  • Posts: 3,153
    • View Profile
Re: Names which cause problems with searches....
« Reply #2 on: Thursday 16 September 10 00:12 BST (UK) »
I have a similar problem with the surnames Street and Shorter.   :)
Census information is Crown Copyright from www.nationalarchives.gov.uk

Offline aghadowey

  • RootsChat Honorary
  • RootsChat Marquessate
  • *******
  • Posts: 51,830
    • View Profile
Re: Names which cause problems with searches....
« Reply #3 on: Thursday 16 September 10 00:16 BST (UK) »
I have Wood, Hunter, Workman, Feld, Smyth, Clyde, Gardner, Dexter, Pidgeon, Arthur, Kane, etc. all of which bring up loads in any search engine so search using quotes for full name or surname and place, etc.
Away sorting out DNA matches... I may be gone for some time many years!


Offline Paul Caswell

  • RootsChat Aristocrat
  • ******
  • Posts: 1,674
  • Me in my natural state
    • View Profile
Re: Names which cause problems with searches....
« Reply #4 on: Thursday 16 September 10 00:18 BST (UK) »
My worst are Drury ... I cant get rid of references to Drury Lane!

Caswell ... oddly, Caswell County is very difficult to exclude.

Cousins ... almost impossible.

Paul
Caswell - Durham(Jarrow), Northumberland(Berwick), Dorset(Netherbury)
Drury - Middlesex(Kensington), Shropshire(Oswestry/Selattyn)
Turner - Dorset(Parkstone)
Speight - Essex(Braintree), Kent(Gravesend), Westmorland(Kendal)
Stockley - Dorset(Corfe Castle)
Amey - Suffolk(Haverhill)
Cousins - Norfolk(Ketteringham)
Sears - Bedfordshire(Potton), Cambridgeshire(Gamlingay)
Census information is Crown Copyright

Offline jrt

  • RootsChat Extra
  • **
  • Posts: 82
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Names which cause problems with searches....
« Reply #5 on: Thursday 16 September 10 00:23 BST (UK) »
 i know exactly what you mean

 black and then theres the wilsons!!!!!
lanarkshire, Lamond beecroft. Ross, McNeil, laird Lang ,,Scot ,McKay,reddiex struthers,Douglas Mullen turvey dunbartonshire johnston gunn Wilson nelson mcteer McCartney

Offline gazania

  • RootsChat Veteran
  • *****
  • Posts: 830
    • View Profile
Re: Names which cause problems with searches....
« Reply #6 on: Thursday 16 September 10 01:02 BST (UK) »
I can add Lane.  The surname Alderman is not all that common but just as hopeless for a Google search unless I can add a qualifier. Gazania
ALDERMAN, Bucks
BELK, Yorkshire, London
CARLING, Bedfordshire
CUNDITH,CUNDILL, Yorkshire, PALIN. Lincolnshire
FOX, Essex; Camberwell Surrey
LANE, Cork IE;Askeaton LIM, Liverpool, Clifton, Bristol
VOLLER, Surrey
WALL Clonlara Co Clare Ireland
WAREHAM, Esher, Surrey; London
WINCH, Surrey

Offline nickgc

  • RootsChat Aristocrat
  • ******
  • Posts: 1,602
  • GGF J. James McLellan 1864-1908
    • View Profile
Re: Names which cause problems with searches....
« Reply #7 on: Thursday 16 September 10 02:16 BST (UK) »
As stated earlier, use quotes if you know a first name: "Joseph Drury" shouldn't result in hits for Drury Lane.  Also, I have found combining the word genealogy or family with confusing names helps to limit the number of false hits.  You can either do this with or without quotes:  Clyde family scotland  Or "clyde family" scotland; "Street genealogy".

Look at the Google advanced search to see what you can do.  You can do Boolean searching (AND OR NOT) with AND being default.  So if you know first names of some relatives you can do a search like, "Elias Street" OR "Joseph Street" OR "Matilda Street".   You can also search drury aberdeen NOT "drury lane".

Hope this helps.

Nick
McLellan - Inverness
Greer - Renfrewshire
Manson - Aberdeen & Orkney
Simpson - Hereford, Devon, etc.
Flett - Orkney
Chisholm - Scotland
Wishart - Orkney
Shand - Aberdeen
Pirie - Aberdeen

-----
Theology is never any help; it is searching in a dark cellar at midnight for a black cat that isn't there.   -Robert Heinlein

Offline dbath

  • RootsChat Member
  • ***
  • Posts: 217
  • Census information Crown Copyright, from www.nationalarchives.gov.uk
    • View Profile
Re: Names which cause problems with searches....
« Reply #8 on: Thursday 16 September 10 04:41 BST (UK) »
If it makes you feel better, I also have Days, but the tree includes Bath (which can lead wrong directions), Church (thankfully leading the other direction), as well as directions (North, West), food (Rice, Trout), and countries (England, French, German, Irish), but my worst are those names that are common first names:  Bryan, Boyd, Dennis, George, Howard, Jack, James, John, Joseph, Kelly, Lee, Lewis, Matthew, Ray, Stanley, Stewart, Todd, and Wade (which show every person with these first names).  Even when you go to a site that only searches names, it is almost enough to cause despair.  There should be a law against it!
BATH - Stithians, Cornwall; HOLMAN, Gwennap, Cornwall; KNOWLES - Cornwall, Devon; REED - Cornwall; CLEGG - Oldham, Lancashire; OGDEN - Oldham, Lancashire; JAMES - Suffolk; REID/REED/READ - Hadleigh, Suffolk; SANDS - Stratford St Mary, Suffolk; TUCKER - Gravesend, Kent;