


<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: What&#8217;s in a Web Site: Collections Search</title>
	<atom:link href="http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/</link>
	<description>The IMA blog is a space to discuss everything related to the Indianapolis Museum of Art.</description>
	<lastBuildDate>Wed, 22 May 2013 01:41:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: stephen poole</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65642</link>
		<dc:creator>stephen poole</dc:creator>
		<pubDate>Thu, 11 Feb 2010 11:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65642</guid>
		<description><![CDATA[Great looking site will have hours of fun looking through it thanks ...]]></description>
		<content:encoded><![CDATA[<p>Great looking site will have hours of fun looking through it thanks &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65561</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Wed, 10 Feb 2010 01:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65561</guid>
		<description><![CDATA[I think you should be able to search by accession number in addition to name, artist, etc.]]></description>
		<content:encoded><![CDATA[<p>I think you should be able to search by accession number in addition to name, artist, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65517</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 09 Feb 2010 18:17:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65517</guid>
		<description><![CDATA[I think one of the coolest features is that you can easily grab a url for your search too. Say you wanted to share a search of &lt;a href=&quot;http://www.imamuseum.org/art/collections/search#search=skull&amp;has_image=1&amp;limit=20&quot; rel=&quot;nofollow&quot;&gt;skulls&lt;/a&gt; with &quot;has image&quot; checked on.

http://www.imamuseum.org/art/collections/search#search=skull&amp;has_image=1&amp;limit=20]]></description>
		<content:encoded><![CDATA[<p>I think one of the coolest features is that you can easily grab a url for your search too. Say you wanted to share a search of <a href="http://www.imamuseum.org/art/collections/search#search=skull&#038;has_image=1&#038;limit=20" rel="nofollow">skulls</a> with &#8220;has image&#8221; checked on.</p>
<p><a href="http://www.imamuseum.org/art/collections/search#search=skull&#038;has_image=1&#038;limit=20" rel="nofollow">http://www.imamuseum.org/art/collections/search#search=skull&#038;has_image=1&#038;limit=20</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65503</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Tue, 09 Feb 2010 17:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65503</guid>
		<description><![CDATA[Thanks for the feedback guys.  We absolutely have a lot of data cleanup to do, but some of this would have never been discovered if we simply printed this information on the record pages.  Tools like this are proving to help us internally as much as the web site visitor.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the feedback guys.  We absolutely have a lot of data cleanup to do, but some of this would have never been discovered if we simply printed this information on the record pages.  Tools like this are proving to help us internally as much as the web site visitor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Solas</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65497</link>
		<dc:creator>Nate Solas</dc:creator>
		<pubDate>Tue, 09 Feb 2010 17:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65497</guid>
		<description><![CDATA[Wow, you&#039;ve already fixed the things I was going to tell you about (tag searches used to be sticky with no way to turn them off, materials didn&#039;t seem to be indexed).  Two things I can think of offhand:

- it seems like you&#039;ve got the AJAX back button implementation half-working.  It changes the URL hash correctly, but it seems like the timer that&#039;s supposed to be watching for that change and reloading the page isn&#039;t firing?  I&#039;m on the latest unstable Chrome on Linux, if maybe it&#039;s just me?
- the fields driving the autocomplete for Materials and Object Type are a bit raw.  Two quick examples: type &quot;cer&quot; into Materials, and there&#039;s a misspelled &quot;cermaic&quot; (that then returns nothing?), and then type &quot;photo&quot; into either field.  The Materials field is full of variations on that word, and even the Object Type has both &quot;photograph&quot; and &quot;photographs&quot; (although those seem to stem to the same actual result set).  We had a big struggle with this same problem and ended up pretty aggressively reducing terms to a common theme, so people could actually find all the photographs regardless of initial classification by the registrars.  Not sure if something like that is practical?

Ooh, finally, seems like Object Type isn&#039;t in the index.  I was going to try a search for &quot;photograph&quot; in the keyword field to see if that actually gave me the results for every photograph, but it doesn&#039;t pick up the ones in Object Type.  To see it more easily, pick &quot;photoaquatint&quot; from Object Type, then add this same word as a keyword - drops to 0 results.

These are nitpicky little things, though, from a guy who just spent way too long thinking about collection search for his MW paper.  Overall, I stand by my initial tweet: phenomenal, and I&#039;m stealing everything.  :)  The addition of filters by Artist and Tag is a great one.

(And I second Michael&#039;s wish for more post-launch reporting!  Are people using the Materials field or still typing &quot;painting&quot; into the keyword field?)]]></description>
		<content:encoded><![CDATA[<p>Wow, you&#8217;ve already fixed the things I was going to tell you about (tag searches used to be sticky with no way to turn them off, materials didn&#8217;t seem to be indexed).  Two things I can think of offhand:</p>
<p>- it seems like you&#8217;ve got the AJAX back button implementation half-working.  It changes the URL hash correctly, but it seems like the timer that&#8217;s supposed to be watching for that change and reloading the page isn&#8217;t firing?  I&#8217;m on the latest unstable Chrome on Linux, if maybe it&#8217;s just me?<br />
- the fields driving the autocomplete for Materials and Object Type are a bit raw.  Two quick examples: type &#8220;cer&#8221; into Materials, and there&#8217;s a misspelled &#8220;cermaic&#8221; (that then returns nothing?), and then type &#8220;photo&#8221; into either field.  The Materials field is full of variations on that word, and even the Object Type has both &#8220;photograph&#8221; and &#8220;photographs&#8221; (although those seem to stem to the same actual result set).  We had a big struggle with this same problem and ended up pretty aggressively reducing terms to a common theme, so people could actually find all the photographs regardless of initial classification by the registrars.  Not sure if something like that is practical?</p>
<p>Ooh, finally, seems like Object Type isn&#8217;t in the index.  I was going to try a search for &#8220;photograph&#8221; in the keyword field to see if that actually gave me the results for every photograph, but it doesn&#8217;t pick up the ones in Object Type.  To see it more easily, pick &#8220;photoaquatint&#8221; from Object Type, then add this same word as a keyword &#8211; drops to 0 results.</p>
<p>These are nitpicky little things, though, from a guy who just spent way too long thinking about collection search for his MW paper.  Overall, I stand by my initial tweet: phenomenal, and I&#8217;m stealing everything.  <img src='http://www.imamuseum.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   The addition of filters by Artist and Tag is a great one.</p>
<p>(And I second Michael&#8217;s wish for more post-launch reporting!  Are people using the Materials field or still typing &#8220;painting&#8221; into the keyword field?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Jenkins</title>
		<link>http://www.imamuseum.org/blog/2010/02/09/whats-in-a-web-site-collections-search/comment-page-1/#comment-65477</link>
		<dc:creator>Michael Jenkins</dc:creator>
		<pubDate>Tue, 09 Feb 2010 16:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.imamuseum.org/blog/?p=10866#comment-65477</guid>
		<description><![CDATA[I dig the date slider. I hope that a few months from now, after you have use stats, you will post on what worked and didn&#039;t work with the collections search design.

Keep up the good work!]]></description>
		<content:encoded><![CDATA[<p>I dig the date slider. I hope that a few months from now, after you have use stats, you will post on what worked and didn&#8217;t work with the collections search design.</p>
<p>Keep up the good work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
