<?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: MIT&#8217;s SIMILE timeline widget	</title>
	<atom:link href="./index.html" rel="self" type="application/rss+xml" />
	<link>./../index.html</link>
	<description>Artist- and Librarian-At-Large</description>
	<lastBuildDate>
	Sat, 04 Jun 2016 18:04:58 +0000	</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.1.8</generator>
			<item>
				<title>
				By: Jonathan Rochkind				</title>
				<link>./../comment-page-1/index.html#comment-7975</link>
		<dc:creator><![CDATA[Jonathan Rochkind]]></dc:creator>
		<pubDate>Tue, 21 Dec 2010 13:56:14 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=707#comment-7975</guid>
					<description><![CDATA[I considered the best feasible way to visualize dates in our result sets. When you can have a  thousands (or tens or hundreds of thousands) of documents in your result set, putting each one of them on a timeline seemed infeasible, both in terms of performance and in terms of usable interface.  What I was able to come up with instead was a sort of histogram/bar-graph timeline that grouped the results into a sort of fixed resolution.

Check it out:  Click on &#039;Publication Year&#039; on any result set after doing a search [or click on the graph on the main page, but I think it&#039;s more useful after a search], and see a timeline; you can also &#039;drill down&#039; into the timeline, and you&#039;ll then see a sort of &#039;zoomed in&#039; timeline of the range you selected.  

https://blacklight.mse.jhu.edu/demo

The resolution of the bars is currently set at around 10, but I believe the underlying Solr search engine powering this could handle higher -- 20, certainly -- 100, maybe but not sure. Haven&#039;t played with it, since this seemed good enough for now and I had other things to work on.  It&#039;s actually just a parameter in the code though, could be set to any number. And of course the graph could be displayed larger, as on the first page, but didn&#039;t seem useful in this interface to do so. 

I think it turned out pretty slick. 

That&#039;s an under development demo of the blacklight/solr powered opac replacement we&#039;re working on, it&#039;s not in production and is  a bit wonky occasionally. And yes, it&#039;s got a non-trusted SSL cert sorry, need to fix it soon.]]></description>
		<content:encoded><![CDATA[<p>I considered the best feasible way to visualize dates in our result sets. When you can have a  thousands (or tens or hundreds of thousands) of documents in your result set, putting each one of them on a timeline seemed infeasible, both in terms of performance and in terms of usable interface.  What I was able to come up with instead was a sort of histogram/bar-graph timeline that grouped the results into a sort of fixed resolution.</p>
<p>Check it out:  Click on &#8216;Publication Year&#8217; on any result set after doing a search [or click on the graph on the main page, but I think it&#8217;s more useful after a search], and see a timeline; you can also &#8216;drill down&#8217; into the timeline, and you&#8217;ll then see a sort of &#8216;zoomed in&#8217; timeline of the range you selected.  </p>
<p><a href="https://blacklight.mse.jhu.edu/demo" rel="nofollow">https://blacklight.mse.jhu.edu/demo</a></p>
<p>The resolution of the bars is currently set at around 10, but I believe the underlying Solr search engine powering this could handle higher &#8212; 20, certainly &#8212; 100, maybe but not sure. Haven&#8217;t played with it, since this seemed good enough for now and I had other things to work on.  It&#8217;s actually just a parameter in the code though, could be set to any number. And of course the graph could be displayed larger, as on the first page, but didn&#8217;t seem useful in this interface to do so. </p>
<p>I think it turned out pretty slick. </p>
<p>That&#8217;s an under development demo of the blacklight/solr powered opac replacement we&#8217;re working on, it&#8217;s not in production and is  a bit wonky occasionally. And yes, it&#8217;s got a non-trusted SSL cert sorry, need to fix it soon.</p>
]]></content:encoded>
						</item>
						<item>
				<title>
				By: Tweets that mention MIT’s SIMILE timeline widget « Infomotions Mini-Musings -- Topsy.com				</title>
				<link>./../comment-page-1/index.html#comment-7967</link>
		<dc:creator><![CDATA[Tweets that mention MIT’s SIMILE timeline widget « Infomotions Mini-Musings -- Topsy.com]]></dc:creator>
		<pubDate>Tue, 21 Dec 2010 02:41:27 +0000</pubDate>
		<guid isPermaLink="false">./../../../../index.html?p=707#comment-7967</guid>
					<description><![CDATA[[...] This post was mentioned on Twitter by infopeep, Eric Lease Morgan. Eric Lease Morgan said: I took a stab at learning how to implement a MIT SIMILE timeline widget -- http://bit.ly/fSHeCT [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] This post was mentioned on Twitter by infopeep, Eric Lease Morgan. Eric Lease Morgan said: I took a stab at learning how to implement a MIT SIMILE timeline widget &#8212; <a href="http://bit.ly/fSHeCT" rel="nofollow">http://bit.ly/fSHeCT</a> [&#8230;]</p>
]]></content:encoded>
						</item>
			</channel>
</rss>
