<?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: metadata</title>
	<atom:link href="http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence</link>
	<description>Publishing, Technology, and the Future of the Academy</description>
	<lastBuildDate>Mon, 02 Jan 2012 17:10:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Natalia Cecire</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-325</link>
		<dc:creator>Natalia Cecire</dc:creator>
		<pubDate>Mon, 16 Nov 2009 18:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-325</guid>
		<description>Oh, yes, Google Scholar. Enter &quot;Wordsworth&quot; and you&#039;ll get obscure scientific studies with one co-author with the last name &quot;Wordsworth.&quot; There has to be a better way. It&#039;s not just a matter of &lt;em&gt;what&lt;/em&gt; they index, but also how. You&#039;re so right that &quot;it&#039;s just not the metadata that we might be most interested in, or that might produce the best results.&quot; There are ways to use metadata that are, for some purposes, close to meaningless.</description>
		<content:encoded><![CDATA[<p>Oh, yes, Google Scholar. Enter &#8220;Wordsworth&#8221; and you&#8217;ll get obscure scientific studies with one co-author with the last name &#8220;Wordsworth.&#8221; There has to be a better way. It&#8217;s not just a matter of &lt;em&gt;what&lt;/em&gt; they index, but also how. You&#8217;re so right that &#8220;it&#8217;s just not the metadata that we might be most interested in, or that might produce the best results.&#8221; There are ways to use metadata that are, for some purposes, close to meaningless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorothea Salo</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-161</link>
		<dc:creator>Dorothea Salo</dc:creator>
		<pubDate>Tue, 06 Oct 2009 20:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-161</guid>
		<description>They&#039;re not even making full use of the MARC records that participating libraries are giving them.</description>
		<content:encoded><![CDATA[<p>They&#8217;re not even making full use of the MARC records that participating libraries are giving them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Fitzpatrick</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-75</link>
		<dc:creator>Kathleen Fitzpatrick</dc:creator>
		<pubDate>Sat, 26 Sep 2009 21:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-75</guid>
		<description>That&#039;s helpful, Kari -- I meant to bring COinS into this chapter, and I&#039;m not sure why it didn&#039;t finally appear here!</description>
		<content:encoded><![CDATA[<p>That&#8217;s helpful, Kari &#8212; I meant to bring COinS into this chapter, and I&#8217;m not sure why it didn&#8217;t finally appear here!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kkraus</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-72</link>
		<dc:creator>kkraus</dc:creator>
		<pubDate>Sat, 26 Sep 2009 20:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-72</guid>
		<description>Just a quick addendum: the COinS metadata that Zotero interprets is relevant to your discussion of OpenURL in the next section.</description>
		<content:encoded><![CDATA[<p>Just a quick addendum: the COinS metadata that Zotero interprets is relevant to your discussion of OpenURL in the next section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kkraus</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-66</link>
		<dc:creator>kkraus</dc:creator>
		<pubDate>Sat, 26 Sep 2009 19:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-66</guid>
		<description>Users are also encouraged to make their personal websites and web resources Zotero-readable by, for example, adding Dublin Core or COinS metadata to their HTML; or by downloading and installing a plug-in for a supported content management system, such as WordPress.  See the documentation on &quot;Making Your Site Zotero Friendly&quot;: http://www.zotero.org/support/make_your_site_zotero_ready</description>
		<content:encoded><![CDATA[<p>Users are also encouraged to make their personal websites and web resources Zotero-readable by, for example, adding Dublin Core or COinS metadata to their HTML; or by downloading and installing a plug-in for a supported content management system, such as WordPress.  See the documentation on &#8220;Making Your Site Zotero Friendly&#8221;: <a href="http://www.zotero.org/support/make_your_site_zotero_ready" rel="nofollow">http://www.zotero.org/support/make_your_site_zotero_ready</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Fitzpatrick</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-55</link>
		<dc:creator>Kathleen Fitzpatrick</dc:creator>
		<pubDate>Fri, 25 Sep 2009 05:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-55</guid>
		<description>Absolutely.  I&#039;ve read about projects that are attempting to produce machine disambiguation, but I suspect they&#039;re a fair bit down the road as yet, and will likely still need expert supervision and training...</description>
		<content:encoded><![CDATA[<p>Absolutely.  I&#8217;ve read about projects that are attempting to produce machine disambiguation, but I suspect they&#8217;re a fair bit down the road as yet, and will likely still need expert supervision and training&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Fitzpatrick</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-54</link>
		<dc:creator>Kathleen Fitzpatrick</dc:creator>
		<pubDate>Fri, 25 Sep 2009 05:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-54</guid>
		<description>That&#039;s a helpful clarification, Amanda; thanks.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a helpful clarification, Amanda; thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amandafrench</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-41</link>
		<dc:creator>amandafrench</dc:creator>
		<pubDate>Wed, 23 Sep 2009 16:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-41</guid>
		<description>A small additional point about this paragraph: a key benefit of expert-produced ontologies is what librarians call &quot;authority control,&quot; an apparently tautological and tyrannical term that just means one can distinguish Jones, John M. 1911-1987 from Jones, John H. 1987-. Technology can sometimes do this kind of disambiguation, as well, but I can&#039;t think of any really good machine-generated examples, and of course users are likely simply to tag something &quot;John Jones.&quot;</description>
		<content:encoded><![CDATA[<p>A small additional point about this paragraph: a key benefit of expert-produced ontologies is what librarians call &#8220;authority control,&#8221; an apparently tautological and tyrannical term that just means one can distinguish Jones, John M. 1911-1987 from Jones, John H. 1987-. Technology can sometimes do this kind of disambiguation, as well, but I can&#8217;t think of any really good machine-generated examples, and of course users are likely simply to tag something &#8220;John Jones.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amandafrench</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-40</link>
		<dc:creator>amandafrench</dc:creator>
		<pubDate>Wed, 23 Sep 2009 15:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-40</guid>
		<description>Actually I don&#039;t think it&#039;s true that URLs to individual tweets cease to work, or at least, they haven&#039;t yet for some of the oldest tweets of mine that I can get my hands on (about 2 years old, dating from late 2007). The problem is that you can&#039;t *find* those tweets or their URLs after a period that is currently only 1.5 &lt;em&gt;weeks&lt;/em&gt;. That very short time &lt;a href=&quot;http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits&quot; rel=&quot;nofollow&quot;&gt;period&lt;/a&gt; is &quot;dynamic and subject to shrink as the number of tweets per day continues to grow&quot;; it used to be about four months.  

Therefore, the only methods of preserving Twitter are currently very ad hoc, and they have to be set up beforehand (TwapperKeeper, RSS, and so on). Still, if you save the URL of an individual tweet, you can link to it with reasonable confidence.</description>
		<content:encoded><![CDATA[<p>Actually I don&#8217;t think it&#8217;s true that URLs to individual tweets cease to work, or at least, they haven&#8217;t yet for some of the oldest tweets of mine that I can get my hands on (about 2 years old, dating from late 2007). The problem is that you can&#8217;t *find* those tweets or their URLs after a period that is currently only 1.5 <em>weeks</em>. That very short time <a href="http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits" rel="nofollow">period</a> is &#8220;dynamic and subject to shrink as the number of tweets per day continues to grow&#8221;; it used to be about four months.  </p>
<p>Therefore, the only methods of preserving Twitter are currently very ad hoc, and they have to be set up beforehand (TwapperKeeper, RSS, and so on). Still, if you save the URL of an individual tweet, you can link to it with reasonable confidence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Fitzpatrick</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-17</link>
		<dc:creator>Kathleen Fitzpatrick</dc:creator>
		<pubDate>Sun, 20 Sep 2009 20:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-17</guid>
		<description>I was there for that moment, and would also be curious to know why they&#039;re not making use of crowdsourcing for metadata correction.  Or even just allowing &lt;em&gt;known librarians&lt;/em&gt; to correct the data.  I&#039;ll hope that they&#039;re developing a system, too.

In the meantime, yeah, I&#039;m going to have to draw the line somehow on updates, but this one seems pretty key.</description>
		<content:encoded><![CDATA[<p>I was there for that moment, and would also be curious to know why they&#8217;re not making use of crowdsourcing for metadata correction.  Or even just allowing <em>known librarians</em> to correct the data.  I&#8217;ll hope that they&#8217;re developing a system, too.</p>
<p>In the meantime, yeah, I&#8217;m going to have to draw the line somehow on updates, but this one seems pretty key.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amandafrench</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-12</link>
		<dc:creator>amandafrench</dc:creator>
		<pubDate>Sun, 20 Sep 2009 07:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-12</guid>
		<description>I think you&#039;re probably right about the need to update this to take Nunberg into account -- though I hope you&#039;ve got a strategy for preventing yourself from updating *everything* as new news breaks. And were you there for the moment at DH 2009 when someone in the audience urgently asked Jon Orwant for that very functionality? I twittered it. :) 

I&#039;d be very grateful to learn why Google Books doesn&#039;t allow metadata correction. I suspect they&#039;re secretly developing a system to allow it, frankly.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re probably right about the need to update this to take Nunberg into account &#8212; though I hope you&#8217;ve got a strategy for preventing yourself from updating *everything* as new news breaks. And were you there for the moment at DH 2009 when someone in the audience urgently asked Jon Orwant for that very functionality? I twittered it. <img src='http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>I&#8217;d be very grateful to learn why Google Books doesn&#8217;t allow metadata correction. I suspect they&#8217;re secretly developing a system to allow it, frankly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathleen Fitzpatrick</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/four-preservation/metadata/#comment-5</link>
		<dc:creator>Kathleen Fitzpatrick</dc:creator>
		<pubDate>Mon, 31 Aug 2009 14:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/mcpress/plannedobsolescence/?page_id=158#comment-5</guid>
		<description>I think this paragraph really needs to be updated to think about what Geoff Nunberg has called the &quot;&lt;a href=&quot;http://languagelog.ldc.upenn.edu/nll/?p=1701&quot; rel=&quot;nofollow&quot;&gt;metadata train wreck&lt;/a&gt;&quot; of Google Books; relying on machine-generated rather than expert-produced metadata will be disastrous -- but even if one starts with that base layer of machine-generated error, &lt;em&gt;it could be corrected&lt;/em&gt; via crowd-sourcing.</description>
		<content:encoded><![CDATA[<p>I think this paragraph really needs to be updated to think about what Geoff Nunberg has called the &#8220;<a href="http://languagelog.ldc.upenn.edu/nll/?p=1701" rel="nofollow">metadata train wreck</a>&#8221; of Google Books; relying on machine-generated rather than expert-produced metadata will be disastrous &#8212; but even if one starts with that base layer of machine-generated error, <em>it could be corrected</em> via crowd-sourcing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

