<?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: We are experiencing technical problems with images in search results</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=we-are-experiencing-technical-problems-with-images-in-search-results</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Tue, 21 May 2013 21:32:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Tony Macklin</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43837</link>
		<dc:creator>Tony Macklin</dc:creator>
		<pubDate>Wed, 10 Feb 2010 00:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43837</guid>
		<description>Hi Hazel Re: 68

Thanks for reaching out to us with your concerns about the possible destruction of records – I share your concern over any historical records being lost.

Our content team has an ongoing relationship with the Archives in Georgia, and we were able to follow up with the County Clerk of Thomas County.  Fortunately, it looks like there has been a misunderstanding – and  I’d like to thank them for clarifying the actual situation: -

“In preparation for the courthouse renovation, the clerk sent out a notice to each county department asking them to review the retention schedules and to destroy eligible records. The remaining records are being housed at a climate controlled facility run by Secure Records Solutions (the county has contracted for the storage of temporary and historical records). No historical records have been destroyed. The county has also rented a warehouse (non-temperature controlled but clean and dry) for the storage of furniture that will go back into the courthouse upon completion of renovations.  NO RECORDS are in the warehouse.”

ie NO historical records are intended to be or have been destroyed.

I’m sure you’re as please as we were to hear this,  however, I would like to thank you for raising this and giving us the opportunity to look into it.

Regards

Tony

Tony Macklin &#124; Sr Director, Search &#124; ancestry.com</description>
		<content:encoded><![CDATA[<p>Hi Hazel Re: 68</p>
<p>Thanks for reaching out to us with your concerns about the possible destruction of records – I share your concern over any historical records being lost.</p>
<p>Our content team has an ongoing relationship with the Archives in Georgia, and we were able to follow up with the County Clerk of Thomas County.  Fortunately, it looks like there has been a misunderstanding – and  I’d like to thank them for clarifying the actual situation: -</p>
<p>“In preparation for the courthouse renovation, the clerk sent out a notice to each county department asking them to review the retention schedules and to destroy eligible records. The remaining records are being housed at a climate controlled facility run by Secure Records Solutions (the county has contracted for the storage of temporary and historical records). No historical records have been destroyed. The county has also rented a warehouse (non-temperature controlled but clean and dry) for the storage of furniture that will go back into the courthouse upon completion of renovations.  NO RECORDS are in the warehouse.”</p>
<p>ie NO historical records are intended to be or have been destroyed.</p>
<p>I’m sure you’re as please as we were to hear this,  however, I would like to thank you for raising this and giving us the opportunity to look into it.</p>
<p>Regards</p>
<p>Tony</p>
<p>Tony Macklin | Sr Director, Search | ancestry.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Macklin</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43699</link>
		<dc:creator>Tony Macklin</dc:creator>
		<pubDate>Sat, 30 Jan 2010 01:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43699</guid>
		<description>Thanks Jim #82 for bringing us back on topic!

We have now tracked down an intermittent issue with the image service and have made changes to resolve it. All newspapers and other images should now be loading correctly.

Please let me know if you find examples where this is the case

We will watch the performance closely over the next few days, and provided it looks good, we expect to restore the &quot;preview&quot; images in search results early next week.

Thank you all for your contributions to this blog post.

regards

Tony (tmacklin@ancestry.com)</description>
		<content:encoded><![CDATA[<p>Thanks Jim #82 for bringing us back on topic!</p>
<p>We have now tracked down an intermittent issue with the image service and have made changes to resolve it. All newspapers and other images should now be loading correctly.</p>
<p>Please let me know if you find examples where this is the case</p>
<p>We will watch the performance closely over the next few days, and provided it looks good, we expect to restore the &#8220;preview&#8221; images in search results early next week.</p>
<p>Thank you all for your contributions to this blog post.</p>
<p>regards</p>
<p>Tony (tmacklin@ancestry.com)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Livermore</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43658</link>
		<dc:creator>Jim Livermore</dc:creator>
		<pubDate>Thu, 28 Jan 2010 11:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43658</guid>
		<description>Can we please get back on topic? When will this image display problem be rectified?</description>
		<content:encoded><![CDATA[<p>Can we please get back on topic? When will this image display problem be rectified?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43620</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Thu, 28 Jan 2010 05:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43620</guid>
		<description>Hazel  R: #80

Just for the record... I&#039;m not part of the &quot;you guys&quot; crowd. I&#039;m not an Ancestry employee. I&#039;m just another paying subscriber.

How are you removing the current image number before you type in the new image number?

Do you just highlight it and hit delete key or do you put cursor in the box and backspace it out?

Try each way and see if it makes a difference - also what browser and version (not that it should make a difference but...)</description>
		<content:encoded><![CDATA[<p>Hazel  R: #80</p>
<p>Just for the record&#8230; I&#8217;m not part of the &#8220;you guys&#8221; crowd. I&#8217;m not an Ancestry employee. I&#8217;m just another paying subscriber.</p>
<p>How are you removing the current image number before you type in the new image number?</p>
<p>Do you just highlight it and hit delete key or do you put cursor in the box and backspace it out?</p>
<p>Try each way and see if it makes a difference &#8211; also what browser and version (not that it should make a difference but&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hazel Clack</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43618</link>
		<dc:creator>Hazel Clack</dc:creator>
		<pubDate>Thu, 28 Jan 2010 03:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43618</guid>
		<description>Andy #79

Apology accepted. I never even noticed.

I understand what you are saying.  That is exactly what I do.  If there are 45 pages and my search comes up on page 27, I type in 1 and click on GO.  It does not work.  It
doesn&#039;t &quot;GO&quot; anywhere. See, we...customers...can have problems and just because you guys don&#039;t seem to be able to duplicate them doesn&#039;t mean that we are not using the application correctly.  It doesn&#039;t matter what page # I put in...GO does not GO.</description>
		<content:encoded><![CDATA[<p>Andy #79</p>
<p>Apology accepted. I never even noticed.</p>
<p>I understand what you are saying.  That is exactly what I do.  If there are 45 pages and my search comes up on page 27, I type in 1 and click on GO.  It does not work.  It<br />
doesn&#8217;t &#8220;GO&#8221; anywhere. See, we&#8230;customers&#8230;can have problems and just because you guys don&#8217;t seem to be able to duplicate them doesn&#8217;t mean that we are not using the application correctly.  It doesn&#8217;t matter what page # I put in&#8230;GO does not GO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43610</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Wed, 27 Jan 2010 20:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43610</guid>
		<description>Hazel

My apologies for getting your name wrong in my post # 75</description>
		<content:encoded><![CDATA[<p>Hazel</p>
<p>My apologies for getting your name wrong in my post # 75</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonard page</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43609</link>
		<dc:creator>leonard page</dc:creator>
		<pubDate>Wed, 27 Jan 2010 16:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43609</guid>
		<description>you keep saying that you already have had this   comment ,but you donot say how to solve it...</description>
		<content:encoded><![CDATA[<p>you keep saying that you already have had this   comment ,but you donot say how to solve it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonard  page</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43608</link>
		<dc:creator>leonard  page</dc:creator>
		<pubDate>Wed, 27 Jan 2010 16:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43608</guid>
		<description>why does the progragme lock onto the [new tree] menu each time i log on...</description>
		<content:encoded><![CDATA[<p>why does the progragme lock onto the [new tree] menu each time i log on&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lenpage123</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43607</link>
		<dc:creator>lenpage123</dc:creator>
		<pubDate>Wed, 27 Jan 2010 15:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43607</guid>
		<description>why does the family tree suddenly lock up at the start of my tree        /all i get is the new tree each time?</description>
		<content:encoded><![CDATA[<p>why does the family tree suddenly lock up at the start of my tree        /all i get is the new tree each time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/15/we-are-experiencing-technical-problems-with-images-in-search-results/#comment-43606</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Wed, 27 Jan 2010 07:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2746#comment-43606</guid>
		<description>Heather Re; #73

I can&#039;t duplicate your problem.

Here is what I&#039;m doing:

1) Bring up census page
2) Place cursor in image # field right in front of &quot;go&quot; button
3) Delete image # that is there
4) Key in &quot;1&quot; (without quotes)
5) Hit enter or click go.

It always takes me to the first image of that set.</description>
		<content:encoded><![CDATA[<p>Heather Re; #73</p>
<p>I can&#8217;t duplicate your problem.</p>
<p>Here is what I&#8217;m doing:</p>
<p>1) Bring up census page<br />
2) Place cursor in image # field right in front of &#8220;go&#8221; button<br />
3) Delete image # that is there<br />
4) Key in &#8220;1&#8243; (without quotes)<br />
5) Hit enter or click go.</p>
<p>It always takes me to the first image of that set.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
