<?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: Roadblock to full OpenURLness [Updated]</title>
	<atom:link href="http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/</link>
	<description>A blog about family, technology, and libraries</description>
	<lastBuildDate>Wed, 25 Jan 2012 15:34:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: <![CDATA[Rick]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2103</link>
		<dc:creator><![CDATA[Rick]]></dc:creator>
		<pubDate>Fri, 31 Aug 2007 09:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2103</guid>
		<description>Quick followup in case anyone has to repeat
the process of turning COinS into links to a particular SFX resolver.

Instead of refbase (as I suggested) or a text editor/regular expressions (as Steve used), one could simply use a COinS resolver in their browser.

So dust off your institution&#039;s version of LibX or one of the various other OpenURL extensions/bookmarklets.  Then just re-save the resulting page!

This gives a static page that uses the resolver specified in LibX (or whatever) for everyone else.  Depending on the method you used to auto-link COinS, the COinS entries will remain too.</description>
		<content:encoded><![CDATA[<p>Quick followup in case anyone has to repeat<br />
the process of turning COinS into links to a particular SFX resolver.</p>
<p>Instead of refbase (as I suggested) or a text editor/regular expressions (as Steve used), one could simply use a COinS resolver in their browser.</p>
<p>So dust off your institution&#8217;s version of LibX or one of the various other OpenURL extensions/bookmarklets.  Then just re-save the resulting page!</p>
<p>This gives a static page that uses the resolver specified in LibX (or whatever) for everyone else.  Depending on the method you used to auto-link COinS, the COinS entries will remain too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Steve]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2102</link>
		<dc:creator><![CDATA[Steve]]></dc:creator>
		<pubDate>Mon, 30 Jul 2007 14:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2102</guid>
		<description>Matthias, thanks for clarifying this feature.</description>
		<content:encoded><![CDATA[<p>Matthias, thanks for clarifying this feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Matthias]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2101</link>
		<dc:creator><![CDATA[Matthias]]></dc:creator>
		<pubDate>Thu, 26 Jul 2007 23:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2101</guid>
		<description>Steve, the current version of refbase allows the database admin to globally specify the base URL to an OpenURL resolver, but it doesn&#039;t yet allow regular users to define user-specific OpenURL settings. So, at the moment, you&#039;d need to setup your own refbase installation to provide for custom OpenURL resolvers.

refbase was build to allow individual researchers and/or scientific institutions to dynamically publish their bibliographies online, with links to full texts (if available or permitted). In that way, a dedicated refbase instance on your institution&#039;s own server might be what you&#039;re looking for.</description>
		<content:encoded><![CDATA[<p>Steve, the current version of refbase allows the database admin to globally specify the base URL to an OpenURL resolver, but it doesn&#8217;t yet allow regular users to define user-specific OpenURL settings. So, at the moment, you&#8217;d need to setup your own refbase installation to provide for custom OpenURL resolvers.</p>
<p>refbase was build to allow individual researchers and/or scientific institutions to dynamically publish their bibliographies online, with links to full texts (if available or permitted). In that way, a dedicated refbase instance on your institution&#8217;s own server might be what you&#8217;re looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Steve]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2100</link>
		<dc:creator><![CDATA[Steve]]></dc:creator>
		<pubDate>Thu, 26 Jul 2007 18:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2100</guid>
		<description>Rick,

Thanks for the tip about refbase.  I hadn&#039;t heard of it before.  I imported citations into that system but I can&#039;t (yet) figure out how to specify an SFX resolver.</description>
		<content:encoded><![CDATA[<p>Rick,</p>
<p>Thanks for the tip about refbase.  I hadn&#8217;t heard of it before.  I imported citations into that system but I can&#8217;t (yet) figure out how to specify an SFX resolver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Rick]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2099</link>
		<dc:creator><![CDATA[Rick]]></dc:creator>
		<pubDate>Thu, 26 Jul 2007 15:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2099</guid>
		<description>If you have to do this more than once (or with a lot of data), a web-based reference management system might make sense.  &lt;a href=&quot;http://www.refbase.org/&quot; rel=&quot;nofollow&quot;&gt;refbase&lt;/a&gt; is free/open source &amp; automatically creates a COinS entry and unAPI+MODS for every single reference &amp; seems to be compatible with Zotero and LibX.

It can also automagically import from a number of formats (including RIS).  It also lets you specify an SFX resolver for OpenURL links.

So, it might take the double-checking &amp; manual generation of COinS out of the workflow.</description>
		<content:encoded><![CDATA[<p>If you have to do this more than once (or with a lot of data), a web-based reference management system might make sense.  <a href="http://www.refbase.org/" rel="nofollow">refbase</a> is free/open source &amp; automatically creates a COinS entry and unAPI+MODS for every single reference &amp; seems to be compatible with Zotero and LibX.</p>
<p>It can also automagically import from a number of formats (including RIS).  It also lets you specify an SFX resolver for OpenURL links.</p>
<p>So, it might take the double-checking &amp; manual generation of COinS out of the workflow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Steve]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2098</link>
		<dc:creator><![CDATA[Steve]]></dc:creator>
		<pubDate>Sat, 21 Jul 2007 23:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2098</guid>
		<description>Hi Mark,

I don&#039;t know exactly why some items get COinS and some don&#039;t, but I &lt;em&gt;do&lt;/em&gt; know that in order to get all of the COinS to work initially when I was setting up my bibliography, I had to manually input them one by one in the COinS generator form.  I suspect that what you are experiencing might be due to incomplete metadata, but cannot be sure at all.

Anyway, I agree that all of this needs to be simplified further.  Not taking away from Zotero&#039;s achievement, nor of COinS, but still.</description>
		<content:encoded><![CDATA[<p>Hi Mark,</p>
<p>I don&#8217;t know exactly why some items get COinS and some don&#8217;t, but I <em>do</em> know that in order to get all of the COinS to work initially when I was setting up my bibliography, I had to manually input them one by one in the COinS generator form.  I suspect that what you are experiencing might be due to incomplete metadata, but cannot be sure at all.</p>
<p>Anyway, I agree that all of this needs to be simplified further.  Not taking away from Zotero&#8217;s achievement, nor of COinS, but still.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: <![CDATA[Mark]]></title>
		<link>http://www.familymanlibrarian.com/2007/07/20/roadblock-to-full-openurlness-updated/comment-page-1/#comment-2097</link>
		<dc:creator><![CDATA[Mark]]></dc:creator>
		<pubDate>Sat, 21 Jul 2007 15:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/?p=659#comment-2097</guid>
		<description>Steve, I don&#039;t have an answer to your specific question but some general comments on the not-quite-ready for prime-time-ness of all this.

As you know, I&#039;m now trying to output COinS data from Zotero for use in my weekly reading lists, to add them to the citations of old papers of mine that I&#039;m posting to the web, etc.

But even though it is a &quot;shiny new thing&quot; the process is archaic as all get out. 1) Have to get the citation into Zotero (understandable!) 2) Have to output as a bibliography in HTML. 3) Have to open web page and get as source code (possibly multi-step process). 4) Copy and paste source code for each item into blog source code, or web page. 5) Rinse; repeat.

This is simply insane! And I&#039;m not even attempting the level of local integration that you are. I only want them in and then people with Zotero or an OpenURL resolver will see them.

Without even addressing your issues, although this is a part of the overall process, I need Zotero to just output the code to perhaps the clipboard, or even better to paste it into whatever open application I have at the insertion point.

Once that becomes simple I might have the energy to try and do even more with it.

Question though ... have you noticed any sort of specifics as to which items get COinS and which do not? Sometimes books and more often my articles don&#039;t. I think it&#039;s the ones I have entered by hand, but I haven&#039;t actually done a real test to determine for sure. Any observations?</description>
		<content:encoded><![CDATA[<p>Steve, I don&#8217;t have an answer to your specific question but some general comments on the not-quite-ready for prime-time-ness of all this.</p>
<p>As you know, I&#8217;m now trying to output COinS data from Zotero for use in my weekly reading lists, to add them to the citations of old papers of mine that I&#8217;m posting to the web, etc.</p>
<p>But even though it is a &#8220;shiny new thing&#8221; the process is archaic as all get out. 1) Have to get the citation into Zotero (understandable!) 2) Have to output as a bibliography in HTML. 3) Have to open web page and get as source code (possibly multi-step process). 4) Copy and paste source code for each item into blog source code, or web page. 5) Rinse; repeat.</p>
<p>This is simply insane! And I&#8217;m not even attempting the level of local integration that you are. I only want them in and then people with Zotero or an OpenURL resolver will see them.</p>
<p>Without even addressing your issues, although this is a part of the overall process, I need Zotero to just output the code to perhaps the clipboard, or even better to paste it into whatever open application I have at the insertion point.</p>
<p>Once that becomes simple I might have the energy to try and do even more with it.</p>
<p>Question though &#8230; have you noticed any sort of specifics as to which items get COinS and which do not? Sometimes books and more often my articles don&#8217;t. I think it&#8217;s the ones I have entered by hand, but I haven&#8217;t actually done a real test to determine for sure. Any observations?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

