<?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 for Robot Librarian</title>
	<atom:link href="http://robotlibrarian.billdueber.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://robotlibrarian.billdueber.com</link>
	<description>Disclaimer: I'm not actually a robot.</description>
	<pubDate>Sat, 04 Jul 2009 14:57:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Sending MARC(ish) data to Refworks by Export to RefWorks from Evergreen &#171; Libre-arian</title>
		<link>http://robotlibrarian.billdueber.com/sending-marcish-data-to-refworks/comment-page-1/#comment-104</link>
		<dc:creator>Export to RefWorks from Evergreen &#171; Libre-arian</dc:creator>
		<pubDate>Wed, 17 Jun 2009 16:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=71#comment-104</guid>
		<description>&lt;p&gt;[...] Sending citations to RefWorks can be done with a callback. Essentially, you add a link to RefWorks&#8217; import function page and send it your credentials, as well as a callback URL that RefWorks uses to grab the record from your ILS&#8230;in a RefWorks-supported format. The problem is that RefWorks doesn&#8217;t accept MODS, MARC, or even MARCXML. They say they accept MARC, but it&#8217;s actually what I call &#8220;MARC text&#8221; (it is described very well by Bill Dueber). [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Sending citations to RefWorks can be done with a callback. Essentially, you add a link to RefWorks&#8217; import function page and send it your credentials, as well as a callback <acronym title="Uniform Resource Locator">URL</acronym> that RefWorks uses to grab the record from your ILS&#8230;in a RefWorks-supported format. The problem is that RefWorks doesn&#8217;t accept MODS, <acronym title="MAchine Readable Cataloging">MARC</acronym>, or even MARCXML. They say they accept <acronym title="MAchine Readable Cataloging">MARC</acronym>, but it&#8217;s actually what I call &#8220;<acronym title="MAchine Readable Cataloging">MARC</acronym> text&#8221; (it is described very well by Bill Dueber). [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ask, and you shall receive, and it shall be AWESOME! by Naomi Dushay</title>
		<link>http://robotlibrarian.billdueber.com/ask-and-you-shall-receive-and-it-shall-be-awesome/comment-page-1/#comment-103</link>
		<dc:creator>Naomi Dushay</dc:creator>
		<pubDate>Thu, 11 Jun 2009 00:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=51#comment-103</guid>
		<description>&lt;p&gt;Bill,
This is freakin' awesome.  What a valuable thing for a library discovery service.  Thanks for bringing it to my attention.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Bill,
This is freakin&#8217; awesome.  What a valuable thing for a library discovery service.  Thanks for bringing it to my attention.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enough with the freakin&#8217; LC Call Number normalization! by Naomi Dushay</title>
		<link>http://robotlibrarian.billdueber.com/enough-with-the-freakin-lc-call-number-normalization/comment-page-1/#comment-102</link>
		<dc:creator>Naomi Dushay</dc:creator>
		<pubDate>Thu, 11 Jun 2009 00:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=54#comment-102</guid>
		<description>&lt;p&gt;I wrote a bunch of LC parsing (and dewey, too!) to get to shelving keys.  It's in the CallNumUtils of the solrmarc project.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I wrote a bunch of <acronym title="Library of Congress">LC</acronym> parsing (and dewey, too!) to get to shelving keys.  It&#8217;s in the CallNumUtils of the solrmarc project.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sending MARC(ish) data to Refworks by Dan Scott</title>
		<link>http://robotlibrarian.billdueber.com/sending-marcish-data-to-refworks/comment-page-1/#comment-84</link>
		<dc:creator>Dan Scott</dc:creator>
		<pubDate>Mon, 11 May 2009 21:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=71#comment-84</guid>
		<description>&lt;p&gt;Bill - thanks so much for this! A working example makes all the difference for other people following in your wake. (Once the waves finish washing over my head, I hope to implement RefWorks export in Evergreen...)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Bill - thanks so much for this! A working example makes all the difference for other people following in your wake. (Once the waves finish washing over my head, I hope to implement RefWorks export in Evergreen&#8230;)</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on MARC-Hash: a proposed format for JSON/YAML/Whatever-compatible MARC records by Bill</title>
		<link>http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/comment-page-1/#comment-78</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Mon, 13 Apr 2009 23:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/#comment-78</guid>
		<description>&lt;p&gt;Meh. I agree -- and hence the disclaimers --- that it's nothing special. But "nothing special that everyone agrees on" is better than no agreement at all, and for some people XML processing is a barrier they don't want to have to deal with. For all its seeming ubiquity, lots of folks never have to deal with XML in their programming.&lt;/p&gt;

&lt;p&gt;I guess my thing is, "IF we're going to serialize MARC as JSON/YAML/Whatnot, let's all do it the same way."&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Meh. I agree &#8212; and hence the disclaimers &#8212; that it&#8217;s nothing special. But &#8220;nothing special that everyone agrees on&#8221; is better than no agreement at all, and for some people <acronym title="Extensible Markup Language">XML</acronym> processing is a barrier they don&#8217;t want to have to deal with. For all its seeming ubiquity, lots of folks never have to deal with <acronym title="Extensible Markup Language">XML</acronym> in their programming.</p>

<p>I guess my thing is, &#8220;IF we&#8217;re going to serialize <acronym title="MAchine Readable Cataloging">MARC</acronym> as JSON/YAML/Whatnot, let&#8217;s all do it the same way.&#8221;</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on MARC-Hash: a proposed format for JSON/YAML/Whatever-compatible MARC records by Jonathan Rochkind</title>
		<link>http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/comment-page-1/#comment-77</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Mon, 13 Apr 2009 22:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/marc-hash-a-proposed-format-for-jsonyamlwhatever-compatible-marc-records/#comment-77</guid>
		<description>&lt;p&gt;This is basically just MARC-XML translated to JSON, yes?&lt;/p&gt;

&lt;p&gt;Do you really find it easier to work with than MARC-XML?  I guess if you're doing your work in javascript, maybe.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is basically just <acronym title="MAchine Readable Cataloging">MARC</acronym>-<acronym title="Extensible Markup Language">XML</acronym> translated to JSON, yes?</p>

<p>Do you really find it easier to work with than <acronym title="MAchine Readable Cataloging">MARC</acronym>-<acronym title="Extensible Markup Language">XML</acronym>?  I guess if you&#8217;re doing your work in javascript, maybe.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on A plea: use Solr to normalize your data by Jonathan Rochkind</title>
		<link>http://robotlibrarian.billdueber.com/a-plea-use-solr-to-normalize-your-data/comment-page-1/#comment-73</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Mon, 30 Mar 2009 22:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=56#comment-73</guid>
		<description>&lt;p&gt;Nice! Can you provide your lccn normalization routines too?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nice! Can you provide your lccn normalization routines too?</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enough with the freakin&#8217; LC Call Number normalization! by Jonathan Rochkind</title>
		<link>http://robotlibrarian.billdueber.com/enough-with-the-freakin-lc-call-number-normalization/comment-page-1/#comment-68</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Wed, 18 Mar 2009 20:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=54#comment-68</guid>
		<description>&lt;p&gt;Thanks for sticking it up on the web. I suspect Blacklight will want that at some point.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for sticking it up on the web. I suspect Blacklight will want that at some point.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ask, and you shall receive, and it shall be AWESOME! by Roddy MacLeod</title>
		<link>http://robotlibrarian.billdueber.com/ask-and-you-shall-receive-and-it-shall-be-awesome/comment-page-1/#comment-49</link>
		<dc:creator>Roddy MacLeod</dc:creator>
		<pubDate>Fri, 13 Feb 2009 14:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=51#comment-49</guid>
		<description>&lt;p&gt;Bill,&lt;/p&gt;

&lt;p&gt;The shetland pony is on it's way.  Would it also be useful to include the ticTOCs URLs for TOC feeds in the text file?  These URLs provide normalised (i.e. corrected, etc) content, which will display within ticTOCs.  e.g. http://www.tictocs.ac.uk/?action=displayJournal&#38;journalId=15711 would be the URL to the TOC of International Journal of Business and Emerging Markets.  etc.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Bill,</p>

<p>The shetland pony is on it&#8217;s way.  Would it also be useful to include the ticTOCs URLs for <acronym title="Table of Contents">TOC</acronym> feeds in the text file?  These URLs provide normalised (i.e. corrected, etc) content, which will display within ticTOCs.  e.g. <a href="http://www.tictocs.ac.uk/?action=displayJournal&amp;journalId=15711" rel="nofollow">http://www.tictocs.ac.uk/?action=displayJournal&amp;journalId=15711</a> would be the <acronym title="Uniform Resource Locator">URL</acronym> to the <acronym title="Table of Contents">TOC</acronym> of International Journal of Business and Emerging Markets.  etc.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ask, and you shall receive, and it shall be AWESOME! by Paul S.</title>
		<link>http://robotlibrarian.billdueber.com/ask-and-you-shall-receive-and-it-shall-be-awesome/comment-page-1/#comment-48</link>
		<dc:creator>Paul S.</dc:creator>
		<pubDate>Fri, 13 Feb 2009 08:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://robotlibrarian.billdueber.com/?p=51#comment-48</guid>
		<description>&lt;p&gt;Excellent work. I shall (go to it) on our own system.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Excellent work. I shall (go to it) on our own system.</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.437 seconds -->
