<?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: Museums In the Digital Domain, Part Two &#8211; Disruptive Technology</title>
	<atom:link href="http://kovenjsmith.com/archives/258/feed" rel="self" type="application/rss+xml" />
	<link>http://kovenjsmith.com/archives/258</link>
	<description>&#34;Making dreams reality since 1975.&#34;</description>
	<lastBuildDate>Tue, 09 Feb 2010 20:47:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Martha Hagood</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-11516</link>
		<dc:creator>Martha Hagood</dc:creator>
		<pubDate>Thu, 05 Nov 2009 22:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-11516</guid>
		<description>Thank you for clarifying a problem I had teaching the art history survey --- I had to deal with Wikipedia as a competing voice, and it was hell to get students to go to on more authoritative sources. The ones I pushed --- hard --- were the best-quality museum sites, and the Met&#039;s Timeline was way out in front.

Heard your interview with Paul Miller online and am enjoying this series of posts. I worked at the Met briefly in 2006, helping with the Gilman collection of photographs. Wish I were there now.</description>
		<content:encoded><![CDATA[<p>Thank you for clarifying a problem I had teaching the art history survey &#8212; I had to deal with Wikipedia as a competing voice, and it was hell to get students to go to on more authoritative sources. The ones I pushed &#8212; hard &#8212; were the best-quality museum sites, and the Met&#8217;s Timeline was way out in front.</p>
<p>Heard your interview with Paul Miller online and am enjoying this series of posts. I worked at the Met briefly in 2006, helping with the Gilman collection of photographs. Wish I were there now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maria Mortati</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8582</link>
		<dc:creator>Maria Mortati</dc:creator>
		<pubDate>Mon, 26 Oct 2009 23:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8582</guid>
		<description>&lt;a href=&quot;#comment-8549&quot; rel=&quot;nofollow&quot;&gt;@Koven&lt;/a&gt; 
Yup, I&#039;m in agreement with your evaluation. That said, museums have a variety of reasons to protect their data. As I mentioned they have their audience&#039;s needs, and often there are stipulations around the usage of &quot;data&quot;.  They may not own it all themselves. It is a more complicated, more nuanced problem than even having the long-term view of building technological infrastructure (I&#039;m working with some fairly small institutions and run into this with them).

What I&#039;m hearing you suggest is a need for creating better vehicles to evaluate the accessibility of a museum&#039;s resources and determining what is open for use (I too run into situations where the museum doesn&#039;t see the potential it has).

I&#039;m also hoping we&#039;ll have a sea change in terms of accessibility-- because that is the likely the only kind of  political will that can make what you are suggesting possible. Being institutions, we&#039;re often at the end of the long tail, so it takes time. 

To play devil&#039;s advocate, I wonder if museums HAVE to get out in front of the data access wave, and I&#039;m curious to see what happens if they don&#039;t. I believe in any case that they present a pretty unique service to their communities by being able to dig deeper into a topic than you or I (with or without Wikipedia) could ever get. So we&#039;ll see.</description>
		<content:encoded><![CDATA[<p><a href="#comment-8549" rel="nofollow">@Koven</a><br />
Yup, I&#8217;m in agreement with your evaluation. That said, museums have a variety of reasons to protect their data. As I mentioned they have their audience&#8217;s needs, and often there are stipulations around the usage of &#8220;data&#8221;.  They may not own it all themselves. It is a more complicated, more nuanced problem than even having the long-term view of building technological infrastructure (I&#8217;m working with some fairly small institutions and run into this with them).</p>
<p>What I&#8217;m hearing you suggest is a need for creating better vehicles to evaluate the accessibility of a museum&#8217;s resources and determining what is open for use (I too run into situations where the museum doesn&#8217;t see the potential it has).</p>
<p>I&#8217;m also hoping we&#8217;ll have a sea change in terms of accessibility&#8211; because that is the likely the only kind of  political will that can make what you are suggesting possible. Being institutions, we&#8217;re often at the end of the long tail, so it takes time. </p>
<p>To play devil&#8217;s advocate, I wonder if museums HAVE to get out in front of the data access wave, and I&#8217;m curious to see what happens if they don&#8217;t. I believe in any case that they present a pretty unique service to their communities by being able to dig deeper into a topic than you or I (with or without Wikipedia) could ever get. So we&#8217;ll see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maria Mortati</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8580</link>
		<dc:creator>Maria Mortati</dc:creator>
		<pubDate>Mon, 26 Oct 2009 23:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8580</guid>
		<description>&lt;a href=&quot;#comment-8549&quot; rel=&quot;nofollow&quot;&gt;@Koven&lt;/a&gt; 
Yup, I&#039;m in agreement with your evaluation. That said, museums have a variety of reasons to protect their data. As I mentioned they have their audience&#039;s needs, and often there are stipulations around the usage of &quot;data&quot;.  They may not own it all themselves. It is a more complicated, more nuanced problem than even having the long-term view of building technological infrastructure. 

What I&#039;m hearing you suggest is a need for creating better vehicles to evaluate the accessibility of a museum&#039;s resources and determining what is open for use (I too run into situations where the museum doesn&#039;t see the potential it has).

I&#039;m also hoping we&#039;ll have a sea change in terms of accessibility-- because that is the likely the only kind of  political will that can make what you are suggesting possible. Being institutions, we&#039;re often at the end of the long tail, so it takes time. 

To play devil&#039;s advocate, I wonder if museums HAVE to get out in front of the data access wave, and I&#039;m curious to see what happens if they don&#039;t. I believe in any case that they present a pretty unique service to their communities by being able to dig deeper into a topic than you or I (with or without Wikipedia) could ever get. So we&#039;ll see.</description>
		<content:encoded><![CDATA[<p><a href="#comment-8549" rel="nofollow">@Koven</a><br />
Yup, I&#8217;m in agreement with your evaluation. That said, museums have a variety of reasons to protect their data. As I mentioned they have their audience&#8217;s needs, and often there are stipulations around the usage of &#8220;data&#8221;.  They may not own it all themselves. It is a more complicated, more nuanced problem than even having the long-term view of building technological infrastructure. </p>
<p>What I&#8217;m hearing you suggest is a need for creating better vehicles to evaluate the accessibility of a museum&#8217;s resources and determining what is open for use (I too run into situations where the museum doesn&#8217;t see the potential it has).</p>
<p>I&#8217;m also hoping we&#8217;ll have a sea change in terms of accessibility&#8211; because that is the likely the only kind of  political will that can make what you are suggesting possible. Being institutions, we&#8217;re often at the end of the long tail, so it takes time. </p>
<p>To play devil&#8217;s advocate, I wonder if museums HAVE to get out in front of the data access wave, and I&#8217;m curious to see what happens if they don&#8217;t. I believe in any case that they present a pretty unique service to their communities by being able to dig deeper into a topic than you or I (with or without Wikipedia) could ever get. So we&#8217;ll see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koven</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8549</link>
		<dc:creator>Koven</dc:creator>
		<pubDate>Mon, 26 Oct 2009 14:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8549</guid>
		<description>&lt;a href=&quot;#comment-8544&quot; rel=&quot;nofollow&quot;&gt;@Maria Mortati&lt;/a&gt; 
Agreed.  I think this has been an issue for museums for quite a while, in that each content endpoint (whether it&#039;s a Web site, a &#039;newfangled touch-screen interactive&#039;, a mobile device, or whatever) has always been viewed as a self-contained entity, with content produced &lt;em&gt;specifically&lt;/em&gt; for that endpoint.  Because content developed for those endpoints is often not repurpose-able, each one of those self-contained content endpoints is a missed opportunity to create technical/content infrastructure.  Much of my work has been about trying to correct that misunderstanding; if you develop a strong content infrastructure, then any of this information can be made available to whatever output you choose.  It&#039;s definitely a harder sell, though--you&#039;re basically making the case that by developing this infrastructure, each content &#039;thing&#039; you make will become cheaper and cheaper to produce over the long term.  But it also means that you&#039;re developing a technical infrastructure that&#039;s probably overkill for the first project or two, and that&#039;s often hard to justify if you&#039;re dealing with decision-makers (be they museum administration, funders, whatever) who have a hard time seeing the long-term benefit of doing that.

But I would also say that a lot of museums self-censor their own content before this even becomes an issue.  Time and again, I see content that &lt;em&gt;already exists&lt;/em&gt;, that is already in a database, that could be put out for public consumption &lt;em&gt;tomorrow&lt;/em&gt;, that isn&#039;t put out, because we&#039;ve decided that &quot;our public isn&#039;t interested in that.&quot;  It&#039;s this self-censoring that most concerns me, because it&#039;s often exactly this highly specialized content that is unique to museums--you can&#039;t find it anywhere else.</description>
		<content:encoded><![CDATA[<p><a href="#comment-8544" rel="nofollow">@Maria Mortati</a><br />
Agreed.  I think this has been an issue for museums for quite a while, in that each content endpoint (whether it&#8217;s a Web site, a &#8216;newfangled touch-screen interactive&#8217;, a mobile device, or whatever) has always been viewed as a self-contained entity, with content produced <em>specifically</em> for that endpoint.  Because content developed for those endpoints is often not repurpose-able, each one of those self-contained content endpoints is a missed opportunity to create technical/content infrastructure.  Much of my work has been about trying to correct that misunderstanding; if you develop a strong content infrastructure, then any of this information can be made available to whatever output you choose.  It&#8217;s definitely a harder sell, though&#8211;you&#8217;re basically making the case that by developing this infrastructure, each content &#8216;thing&#8217; you make will become cheaper and cheaper to produce over the long term.  But it also means that you&#8217;re developing a technical infrastructure that&#8217;s probably overkill for the first project or two, and that&#8217;s often hard to justify if you&#8217;re dealing with decision-makers (be they museum administration, funders, whatever) who have a hard time seeing the long-term benefit of doing that.</p>
<p>But I would also say that a lot of museums self-censor their own content before this even becomes an issue.  Time and again, I see content that <em>already exists</em>, that is already in a database, that could be put out for public consumption <em>tomorrow</em>, that isn&#8217;t put out, because we&#8217;ve decided that &#8220;our public isn&#8217;t interested in that.&#8221;  It&#8217;s this self-censoring that most concerns me, because it&#8217;s often exactly this highly specialized content that is unique to museums&#8211;you can&#8217;t find it anywhere else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maria Mortati</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8544</link>
		<dc:creator>Maria Mortati</dc:creator>
		<pubDate>Mon, 26 Oct 2009 04:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8544</guid>
		<description>Great article, and so far, it all sounds... sound. 

In working with new or reinventing museums, am finding it&#039;s hard to create access to their data for a variety of reasons. Part of it is your so noted cultural unwillingness (they&#039;re called &quot;institutions&quot; for a reason). The other is because it&#039;s matched up with something that is intangible in terms of outcome. 

Technological infrastructure is what we&#039;re utlimately talking about, and is costly, complex, and a less sexy sell than &quot;we could put that info on the floor in them thar newfangled touch-screen interactive&quot;. 

In my world the hurdles tend to be: institutional value system, money, ownership, protection of kids, funders stipulations and... money. 

Looking forward to part 3.</description>
		<content:encoded><![CDATA[<p>Great article, and so far, it all sounds&#8230; sound. </p>
<p>In working with new or reinventing museums, am finding it&#8217;s hard to create access to their data for a variety of reasons. Part of it is your so noted cultural unwillingness (they&#8217;re called &#8220;institutions&#8221; for a reason). The other is because it&#8217;s matched up with something that is intangible in terms of outcome. </p>
<p>Technological infrastructure is what we&#8217;re utlimately talking about, and is costly, complex, and a less sexy sell than &#8220;we could put that info on the floor in them thar newfangled touch-screen interactive&#8221;. </p>
<p>In my world the hurdles tend to be: institutional value system, money, ownership, protection of kids, funders stipulations and&#8230; money. </p>
<p>Looking forward to part 3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koven</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8461</link>
		<dc:creator>Koven</dc:creator>
		<pubDate>Fri, 23 Oct 2009 03:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8461</guid>
		<description>&lt;a href=&quot;#comment-8458&quot; rel=&quot;nofollow&quot;&gt;@John Hiemstra&lt;/a&gt; 
Thanks, John!  I hope I didn&#039;t take up too much of #Gugg50&#039;s feed with discussions of the merits of various museums as roller-skating venues.  In the next post I get a little more into the findability/accessibility aspect of things; I&#039;d be interested to hear your take on that.  Thanks for reading!</description>
		<content:encoded><![CDATA[<p><a href="#comment-8458" rel="nofollow">@John Hiemstra</a><br />
Thanks, John!  I hope I didn&#8217;t take up too much of #Gugg50&#8217;s feed with discussions of the merits of various museums as roller-skating venues.  In the next post I get a little more into the findability/accessibility aspect of things; I&#8217;d be interested to hear your take on that.  Thanks for reading!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hiemstra</title>
		<link>http://kovenjsmith.com/archives/258/comment-page-1#comment-8458</link>
		<dc:creator>John Hiemstra</dc:creator>
		<pubDate>Fri, 23 Oct 2009 03:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://kovenjsmith.com/?p=258#comment-8458</guid>
		<description>I must say that these two articles are really well done for works in progress and that you&#039;ve hit on a couple of my recent harangues and put them far more eloquently, especially the paragraph on search results, Wikipedia and Flickr, Peter Chernin&#039;s &quot;You can&#039;t protect old business models artificially&quot; and using the word &quot;findability&quot; for that modern day requirement-for-success.

Thanks, I&#039;m looking forward to part 3.

Oh yeah, I found you through Twitter #Gugg50 event this week.</description>
		<content:encoded><![CDATA[<p>I must say that these two articles are really well done for works in progress and that you&#8217;ve hit on a couple of my recent harangues and put them far more eloquently, especially the paragraph on search results, Wikipedia and Flickr, Peter Chernin&#8217;s &#8220;You can&#8217;t protect old business models artificially&#8221; and using the word &#8220;findability&#8221; for that modern day requirement-for-success.</p>
<p>Thanks, I&#8217;m looking forward to part 3.</p>
<p>Oh yeah, I found you through Twitter #Gugg50 event this week.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
