Create a search list by date and last name wild card

+17 votes
305 views
In trying to clean up and merge pre-1600 profiles, the hardest part is all the variations on the spelling of the last name.   My example is Youngs, Young, Yonges, Younges...

If we had the ability to do a search based on a date or birth or century of birth and have a wildcard in the last name field, I think it would help.   In the above example, if I could search for date of birth 1585 +/- 12 years and last name 'Yo*', I could find all the duplicates and work them in one list.   Right now I open up 5-6 tabs of the surnames, sorted by birth, and then bounce back and forth trying to find duplicates.

Does this interest others?   I realize that this would have to be well thought through to create a manageable list (under 100 profiles), but, I think it would help those of us trying to clean up the multitude of duplicate profiles that exist just due to alternate spellings.
in WikiTree Tech by Robin Lee G2G6 Pilot (870k points)
retagged by Keith Hathaway
Thanks Robin! I added this to the To-Do list we started last week to help the team keep track of suggestions and....well... to-dos. :)

http://www.wikitree.com/wiki/To-Do

That would be really great indeed and very helpfull, so YES this really does interest others yes Thanks for posting and Eowyn thanks for adding this to the To-Do list smiley

I love the idea.
You can already search using wildcards in the People:Search page. I usually put in the first name (or part with an *) then in your case I would use Yo*, set the date to plus/minus 12 or 30, depending on how common the name is.
I'm confused, can't you already do this, as Anne says? http://www.wikitree.com/wiki/Special:SearchPerson

Is there something we're not understanding?

Taking off the to-do list for now.

2 Answers

+7 votes
 
Best answer
Great suggestion, Robin!  You don't need to go back to the 17th century to find spelling variations in last names - I have a lot from the 19th century.  I'm sure that adding a wild card search in the last name will help a lot of us find more people, and maybe avoid duplicate entries.

And thanks for posting the list to the new To-Do List, Eowyn.  What a great idea!  I hope it appears in the WikiTree email blast and spur the creative ideas of other contributors.
by Star Kline G2G6 Pilot (727k points)
selected by Robin Lee
+5 votes
This would be awesome! For now ... we do have the custom Google name search to circumvent the internal name search. it's here:

 

https://cse.google.com/cse/home?cx=partner-pub-5983849578006601:2801067696

 

It's alright, but it gets slammed by the most popular hits to particular profiles.

 

I also made my own Google custom search anyone can use. It sweeps up the content from the entire site: profiles, categories, spaces, G2G forum, etc.

 

https://cse.google.com/cse/publicurl?cx=012267546731583674077:odrk-noypve
by Living Ogle G2G6 Mach 3 (31.4k points)

Bree, what do you mean by "it gets slammed by the most popular hits to particular profiles. "?

It's the typical Google popularity game... The more a link gets clicked, the more it gets pushed to the top of the results, and tends to bury the less trafficked links.
Thanks for the clarification. What's the impact of that on wikitreers using it here?

Pretty much take it at face value. The custom search is a Google product. And Google's search is subject to the programming of Google's algorithm ... which changes from time to time. 

What does not change is that Google hits aren't based on the best selection (i.e. -- the most relevant/logical choice) ... it's literally based on popularity. So for instance... if I use the custom search for categories, and I type in slave-owner... It will serve me up the slave owners specifically in Virginia at the top of the list. There's no alphabetical sense to it... Google gives me that hit because that particular page has grabbed the most traffic.

 

So with any custom search, if we type in say... a particular last name, the most popular person with that last name (i.e. -- the person whose gained the most hits), will be the first seen. This is okay... but it can be problematic when we get to names like John Smith. That's when we we want to be more specific in our searches with dates, locations, biographical info, etc...

 

I want to add something important here... WikiTree has one significant advantage that I absolutely adore. The VITALS section of every profile uses "MICRODATA". Without boring everybody... that basically boosts the ranking of every profile page. In fact, I personally believe that because we have the luxury of this awesome technical feature... it's not necessary to repeat that information in the biography text section. 

 

I might go one step further and say... I'm even against repeating that info [word for word]... because Google demotes a page for redundant content.

 

However, consistency is the recommended approach by the staff, and our Style Standards are meant to support that... [This helps the members get up and running without having to be SEO gurus.]... So it's okay that members do, especially since it may be the only info they know about an ancestor. So the key is then to REWORD that info or list it out in a different manner, so Google doesn't bust the page.

Wow, that's really important to understand. Thank you!!
I'm so glad I didn't bore you! Normally, I'm afraid to talk about this stuff since it's very dry conversation:D

Related questions

+3 votes
1 answer
181 views asked Dec 24, 2012 in Genealogy Help by Sandi Wiggins G2G6 Mach 7 (70.7k points)
+7 votes
2 answers
127 views asked Jul 30, 2015 in WikiTree Tech by Carole Taylor G2G6 Mach 7 (74.7k points)
+9 votes
0 answers
+26 votes
2 answers
+5 votes
0 answers
97 views asked Dec 20, 2014 in WikiTree Tech by Steve Broyles G2G6 (8.3k points)
+10 votes
1 answer
115 views asked Nov 23, 2014 in WikiTree Tech by Anne B G2G Astronaut (1.3m points)
+5 votes
1 answer
149 views asked Nov 6, 2014 in WikiTree Tech by Cynthia B G2G6 Pilot (140k points)
+8 votes
1 answer

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...