<?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: Patchwork Prototyping a Collections Dashboard</title>
	<atom:link href="http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/feed/" rel="self" type="application/rss+xml" />
	<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/</link>
	<description>The Humanities and Technology Camp</description>
	<lastBuildDate>Tue, 04 May 2010 07:52:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Liste non exhaustive des thématiques abordées lors des THATCamp &#124; ThatCamp Paris 2010</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-5442</link>
		<dc:creator>Liste non exhaustive des thématiques abordées lors des THATCamp &#124; ThatCamp Paris 2010</dc:creator>
		<pubDate>Tue, 04 May 2010 07:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-5442</guid>
		<description>[...] http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/" rel="nofollow">http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sterling Fluharty</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-114</link>
		<dc:creator>Sterling Fluharty</dc:creator>
		<pubDate>Thu, 04 Jun 2009 17:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-114</guid>
		<description>I agree that ontologies can be time consuming.  Maybe what would work best is an experiment in crowdsourcing, where participants in a session have five to ten minutes to work out an ontology for the digital humanities.  This could at least raise awareness about the value and challenge of creating ontologies.

You can find some of my thoughts on how Google has affected research here:
http://cliomachine.org/wordpress/?p=65

I think young researchers who grew up on Google have lost some of the skills acquired by previous generations of researchers.  Our concepts and measurements of relevant search results has also been watered down as Google&#039;s influence has increased, in my opinion.</description>
		<content:encoded><![CDATA[<p>I agree that ontologies can be time consuming.  Maybe what would work best is an experiment in crowdsourcing, where participants in a session have five to ten minutes to work out an ontology for the digital humanities.  This could at least raise awareness about the value and challenge of creating ontologies.</p>
<p>You can find some of my thoughts on how Google has affected research here:<br />
<a href="http://cliomachine.org/wordpress/?p=65" rel="nofollow">http://cliomachine.org/wordpress/?p=65</a></p>
<p>I think young researchers who grew up on Google have lost some of the skills acquired by previous generations of researchers.  Our concepts and measurements of relevant search results has also been watered down as Google&#8217;s influence has increased, in my opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Musebrarian</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-107</link>
		<dc:creator>Musebrarian</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-107</guid>
		<description>@Patrick:  I think there are also new possibilities that open up when we start having large quantities of item-level metadata around for collections which were never described at that level of granularity before. When collections are described at higher levels, there is a certain amount of purposeful wandering that&#039;s necessary to get the lay of the land.  

I also think there is something very human-scale about working with certain kinds of physical collections (even for large archives, we still talk about &quot;linear feet&quot; of materials - a very human-scale measurement).  But digital collections are less tangible (measurements often rely on comparison to physical collections - how many times is the Library of Congress invoked as a yardstick for the capacity of some new digital medium?).  I see a collection dashboard as a way of quickly and easily grasping the the quantifiable features of a collection on a more human scale.</description>
		<content:encoded><![CDATA[<p>@Patrick:  I think there are also new possibilities that open up when we start having large quantities of item-level metadata around for collections which were never described at that level of granularity before. When collections are described at higher levels, there is a certain amount of purposeful wandering that&#8217;s necessary to get the lay of the land.  </p>
<p>I also think there is something very human-scale about working with certain kinds of physical collections (even for large archives, we still talk about &#8220;linear feet&#8221; of materials &#8211; a very human-scale measurement).  But digital collections are less tangible (measurements often rely on comparison to physical collections &#8211; how many times is the Library of Congress invoked as a yardstick for the capacity of some new digital medium?).  I see a collection dashboard as a way of quickly and easily grasping the the quantifiable features of a collection on a more human scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Musebrarian</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-105</link>
		<dc:creator>Musebrarian</dc:creator>
		<pubDate>Wed, 03 Jun 2009 22:40:30 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-105</guid>
		<description>@Sterling:  I think you&#039;re right about a need to explore the ontologies (both explicit and implicit) that are currently used to describe collections (and I&#039;m sure Mark M. might have a few things to say about EAD), but at the same time that might be too distracting for THATCamp. At least personally I&#039;d me more interested in exploring some grounded hunches that contours  matter.   

Do you think that Google&#039;s precision is de-skilling researchers or just obscuring things which are relevant (but do not have a high page-rank?)</description>
		<content:encoded><![CDATA[<p>@Sterling:  I think you&#8217;re right about a need to explore the ontologies (both explicit and implicit) that are currently used to describe collections (and I&#8217;m sure Mark M. might have a few things to say about EAD), but at the same time that might be too distracting for THATCamp. At least personally I&#8217;d me more interested in exploring some grounded hunches that contours  matter.   </p>
<p>Do you think that Google&#8217;s precision is de-skilling researchers or just obscuring things which are relevant (but do not have a high page-rank?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: patrickmj</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-49</link>
		<dc:creator>patrickmj</dc:creator>
		<pubDate>Thu, 28 May 2009 13:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-49</guid>
		<description>Very interesting....it might be related to the transformation from info being hard to dig up to info being all too easy to dig up.  When it was hard to dig up, one had to cast a wide net and focus in from there--a process that necessarily revealed those contours.  With info being easy to dig up, there&#039;s more need for filtering right off the bat, which immediately obscures the contours?</description>
		<content:encoded><![CDATA[<p>Very interesting&#8230;.it might be related to the transformation from info being hard to dig up to info being all too easy to dig up.  When it was hard to dig up, one had to cast a wide net and focus in from there&#8211;a process that necessarily revealed those contours.  With info being easy to dig up, there&#8217;s more need for filtering right off the bat, which immediately obscures the contours?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sterling Fluharty</title>
		<link>http://thatcamp.org/2009/patchwork-prototyping-a-collections-dashboard/comment-page-1/#comment-43</link>
		<dc:creator>Sterling Fluharty</dc:creator>
		<pubDate>Thu, 28 May 2009 06:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://thatcamp.org/?p=53#comment-43</guid>
		<description>This sounds like a fascinating topic.  We could have a pretty interesting discussion of how information gets encoded, represented, and recognized in finding aids for archival and manuscript collections.  I think you raise an interesting question of how aggregation impacts search techniques.  Your exploration of scale is on the right track, in my estimation.  What might be missing from your model, though, is an exploration of the ontologies necessary for making the most sense of finding aids.  In fact, I am of the opinion that in this era of Google-influenced keyword searching, researchers have actually gotten better at finding sources that exactly match their topic and worse at uncovering sources that are semantically related to their topic.  We could talk about whether this is the case and what the remedy might be.</description>
		<content:encoded><![CDATA[<p>This sounds like a fascinating topic.  We could have a pretty interesting discussion of how information gets encoded, represented, and recognized in finding aids for archival and manuscript collections.  I think you raise an interesting question of how aggregation impacts search techniques.  Your exploration of scale is on the right track, in my estimation.  What might be missing from your model, though, is an exploration of the ontologies necessary for making the most sense of finding aids.  In fact, I am of the opinion that in this era of Google-influenced keyword searching, researchers have actually gotten better at finding sources that exactly match their topic and worse at uncovering sources that are semantically related to their topic.  We could talk about whether this is the case and what the remedy might be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
