<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Search Implemented</title>
	<link>http://www.dftproject.org/blog/2007/01/15/search-implemented/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 19:30:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Yakov Shafranovich</title>
		<link>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-875</link>
		<author>Yakov Shafranovich</author>
		<pubDate>Wed, 17 Jan 2007 04:55:24 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-875</guid>
					<description>Have you looked at Google's Custom Search Engine. For example, the following query searchs PhpGedView pages across the web:

http://www.google.com/search?q=inurl:individual.php inurl:pid=

And the following quiery pulls up GEDCOM files:

http://www.google.com/search?q=adam filetype:ged</description>
		<content:encoded><![CDATA[<p>Have you looked at Google&#8217;s Custom Search Engine. For example, the following query searchs PhpGedView pages across the web:</p>
<p><a href="http://www.google.com/search?q=inurl:individual.php" rel="nofollow">http://www.google.com/search?q=inurl:individual.php</a> inurl:pid=</p>
<p>And the following quiery pulls up GEDCOM files:</p>
<p><a href="http://www.google.com/search?q=adam" rel="nofollow">http://www.google.com/search?q=adam</a> filetype:ged</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Hilton</title>
		<link>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-876</link>
		<author>Hilton</author>
		<pubDate>Wed, 17 Jan 2007 16:48:55 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-876</guid>
					<description>Thanks for the tip!  Search agents could definitely be written which leverage Google search to find data.  I'm currently working with PhpGedView sites directly because I anticipate some sort of feedback cycle: one where my work impacts the software that runs PGV sites so that they can automatically (or semi-automatically) link up together, creating a distributed network of genealogy in the process.  Google search results would certainly bring in more data, but that data won't be as actionable in this respect.  I hope to go down that avenue the future, however.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip!  Search agents could definitely be written which leverage Google search to find data.  I&#8217;m currently working with PhpGedView sites directly because I anticipate some sort of feedback cycle: one where my work impacts the software that runs PGV sites so that they can automatically (or semi-automatically) link up together, creating a distributed network of genealogy in the process.  Google search results would certainly bring in more data, but that data won&#8217;t be as actionable in this respect.  I hope to go down that avenue the future, however.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; On Sticking to the Spec</title>
		<link>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-879</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; On Sticking to the Spec</author>
		<pubDate>Fri, 19 Jan 2007 22:35:31 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-879</guid>
					<description>[...] If you&#8217;ll look at the most recent screenshot of Genesis, you&#8217;ll notice the search box is disabled and the &#8220;Go&#8221; button isÂ changed to a &#8220;Stop&#8221; button.Â  Contrary to the original spec, I made it so that when you search, you have to hit the &#8220;Stop&#8221; button and wait for all the threads to die before the search box is enabled and you can search again.Â  This really lengthened the cycle when I was testing searches because the threads can take a long time to properly die.Â  Finally getting fed up with, I decided to return to the original spec. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] If you&#8217;ll look at the most recent screenshot of Genesis, you&#8217;ll notice the search box is disabled and the &#8220;Go&#8221; button isÂ changed to a &#8220;Stop&#8221; button.Â  Contrary to the original spec, I made it so that when you search, you have to hit the &#8220;Stop&#8221; button and wait for all the threads to die before the search box is enabled and you can search again.Â  This really lengthened the cycle when I was testing searches because the threads can take a long time to properly die.Â  Finally getting fed up with, I decided to return to the original spec. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Enabling the Distributed Family Tree &#187; Blog Archive &#187; Piggybacking on Google</title>
		<link>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-1433</link>
		<author>Enabling the Distributed Family Tree &#187; Blog Archive &#187; Piggybacking on Google</author>
		<pubDate>Wed, 07 Mar 2007 03:54:25 +0000</pubDate>
		<guid>http://www.dftproject.org/blog/2007/01/15/search-implemented/#comment-1433</guid>
					<description>[...] months ago Yakov Shafranovich made an excellent recommendation: why not just use Google!?Â  I didn&#8217;t quite realize at the time how insightful he [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] months ago Yakov Shafranovich made an excellent recommendation: why not just use Google!?Â  I didn&#8217;t quite realize at the time how insightful he [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
