<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Ancestry Search: Improved Wildcard flexibility</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ancestry-search-improved-wildcard-flexibility</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Thu, 23 May 2013 03:10:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: claire</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43221</link>
		<dc:creator>claire</dc:creator>
		<pubDate>Sun, 17 Jan 2010 20:36:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43221</guid>
		<description>Yeah on the new feature...and a request. If possible the feature I would love added is the option to sort the search results by the column headings. 

Often I get hundreds of results. If I use too many filters I sometimes lose the very result I am looking for. The option to sort all the results by birth date, place, or surname would be a fantastic time saver!!! That way I could sort the information by the column I am most certain of. That way I can reduced the number I need to look through and, at the same time, keep in all the results that may have errors...misspelling wrong years, etc.</description>
		<content:encoded><![CDATA[<p>Yeah on the new feature&#8230;and a request. If possible the feature I would love added is the option to sort the search results by the column headings. </p>
<p>Often I get hundreds of results. If I use too many filters I sometimes lose the very result I am looking for. The option to sort all the results by birth date, place, or surname would be a fantastic time saver!!! That way I could sort the information by the column I am most certain of. That way I can reduced the number I need to look through and, at the same time, keep in all the results that may have errors&#8230;misspelling wrong years, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Lankshear</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43206</link>
		<dc:creator>Ron Lankshear</dc:creator>
		<pubDate>Sat, 16 Jan 2010 23:14:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43206</guid>
		<description>I am searching with
?ob*ns
for Robins or Robbins which sometimes also end ens or ans
and may start with D or other letters

?ob*ns seems to be in the terms of the new wildcard function

But for a week or so whilst I get results
There is also a message with red/pink background

&quot;Due to current technical difficulties, only partial search results are shown above. Please try your search again later to see full results.&quot;

I thought temporary but seems to be permanent now and appears when I try &quot;complex&quot; wildcard searches</description>
		<content:encoded><![CDATA[<p>I am searching with<br />
?ob*ns<br />
for Robins or Robbins which sometimes also end ens or ans<br />
and may start with D or other letters</p>
<p>?ob*ns seems to be in the terms of the new wildcard function</p>
<p>But for a week or so whilst I get results<br />
There is also a message with red/pink background</p>
<p>&#8220;Due to current technical difficulties, only partial search results are shown above. Please try your search again later to see full results.&#8221;</p>
<p>I thought temporary but seems to be permanent now and appears when I try &#8220;complex&#8221; wildcard searches</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elizabeth</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43196</link>
		<dc:creator>Elizabeth</dc:creator>
		<pubDate>Sat, 16 Jan 2010 18:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43196</guid>
		<description>This is great news and I am excited about being able to embark on many new searches!</description>
		<content:encoded><![CDATA[<p>This is great news and I am excited about being able to embark on many new searches!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nan Harvey</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43136</link>
		<dc:creator>Nan Harvey</dc:creator>
		<pubDate>Wed, 13 Jan 2010 17:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43136</guid>
		<description>This is absolutely wonderful.  Maybe I can find my Bromagem (Brumigen, etc.)  ancestors more easily.</description>
		<content:encoded><![CDATA[<p>This is absolutely wonderful.  Maybe I can find my Bromagem (Brumigen, etc.)  ancestors more easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackie Krear</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43125</link>
		<dc:creator>Jackie Krear</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43125</guid>
		<description>Keep working to get even MORE (like two letters and a wildcard)... and wildcards on BOTH ENDS (cause searches on the INTERIOR of words is NOT new science).

But thanks for small improvements of any kind.</description>
		<content:encoded><![CDATA[<p>Keep working to get even MORE (like two letters and a wildcard)&#8230; and wildcards on BOTH ENDS (cause searches on the INTERIOR of words is NOT new science).</p>
<p>But thanks for small improvements of any kind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ancestry.com Blog - &#187; Ancestry Search: Controlling your results with filters</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43119</link>
		<dc:creator>Ancestry.com Blog - &#187; Ancestry Search: Controlling your results with filters</dc:creator>
		<pubDate>Tue, 12 Jan 2010 14:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43119</guid>
		<description>[...] that 2010 is going to be an exciting year for Search at ancestry.com. As you know, we launched expanded wild card functionality at the beginning of this year. But that was only the start of things to [...]</description>
		<content:encoded><![CDATA[<p>[...] that 2010 is going to be an exciting year for Search at ancestry.com. As you know, we launched expanded wild card functionality at the beginning of this year. But that was only the start of things to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Polly Rubery</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43118</link>
		<dc:creator>Polly Rubery</dc:creator>
		<pubDate>Tue, 12 Jan 2010 13:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43118</guid>
		<description>Thank you for this great improvement - I&#039;ve already found quite a few &quot;missing people&quot; using it.

However there is one place where it doesn&#039;t work and where it would be a great help if it did.  And that is in the English &amp; Welsh GRO birth and death indexes from 1916-2005 (which are great BTW!).

This is because for the period 1916 to 1966 no full second names are recorded, but afterwards they are listed in full.

So it would be great to be able to search the whole database by using &quot;Adam A*&quot; but this is not allowed.

Thus to get all the results, both &quot;Adam A&quot; and &quot;Adam Afullname&quot; you have to search just for Adam, which (with more common names than my example) greatly increases the number of results one has to wade through.</description>
		<content:encoded><![CDATA[<p>Thank you for this great improvement &#8211; I&#8217;ve already found quite a few &#8220;missing people&#8221; using it.</p>
<p>However there is one place where it doesn&#8217;t work and where it would be a great help if it did.  And that is in the English &amp; Welsh GRO birth and death indexes from 1916-2005 (which are great BTW!).</p>
<p>This is because for the period 1916 to 1966 no full second names are recorded, but afterwards they are listed in full.</p>
<p>So it would be great to be able to search the whole database by using &#8220;Adam A*&#8221; but this is not allowed.</p>
<p>Thus to get all the results, both &#8220;Adam A&#8221; and &#8220;Adam Afullname&#8221; you have to search just for Adam, which (with more common names than my example) greatly increases the number of results one has to wade through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gen Jonely</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43115</link>
		<dc:creator>Gen Jonely</dc:creator>
		<pubDate>Mon, 11 Jan 2010 21:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43115</guid>
		<description>Helpful clarification of search options.</description>
		<content:encoded><![CDATA[<p>Helpful clarification of search options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virginia</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43114</link>
		<dc:creator>Virginia</dc:creator>
		<pubDate>Mon, 11 Jan 2010 16:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43114</guid>
		<description>Thanks for the improved wildcard search.

Recently, everytime I use Edit on my search, it comes back with Exact checked for all entries. It&#039;s tiresome to keep changing this back to what I had for the previous search.</description>
		<content:encoded><![CDATA[<p>Thanks for the improved wildcard search.</p>
<p>Recently, everytime I use Edit on my search, it comes back with Exact checked for all entries. It&#8217;s tiresome to keep changing this back to what I had for the previous search.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/04/ancestry-search-improved-wildcard-flexibility/#comment-43108</link>
		<dc:creator>Laura</dc:creator>
		<pubDate>Mon, 11 Jan 2010 00:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2672#comment-43108</guid>
		<description>YAY! I was finally able to test out some names using this new capability. The Brunschwilers in my husband&#039;s family NEVER have their name correctly on census records (not necessarily Ancestry&#039;s fault, since the writers of the census just wrote whatever they wanted, one time it was Bruni). But I needed the 1920 census and could never find it. Anyway, I typed Br*ler and sure enough, the VERY FIRST ONE is the one I want (Bruschoviler). THANK YOU! Off to test the next name!</description>
		<content:encoded><![CDATA[<p>YAY! I was finally able to test out some names using this new capability. The Brunschwilers in my husband&#8217;s family NEVER have their name correctly on census records (not necessarily Ancestry&#8217;s fault, since the writers of the census just wrote whatever they wanted, one time it was Bruni). But I needed the 1920 census and could never find it. Anyway, I typed Br*ler and sure enough, the VERY FIRST ONE is the one I want (Bruschoviler). THANK YOU! Off to test the next name!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
