<?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: Dynamic OpenURL lookup with document delivery</title>
	<atom:link href="http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/</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: Ian Palmer</title>
		<link>http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/comment-page-1/#comment-4684</link>
		<dc:creator>Ian Palmer</dc:creator>
		<pubDate>Sat, 15 Nov 2008 16:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/#comment-4684</guid>
		<description>Steve: Great post and I think you&#039;re spot on in your first-comment reply.  link resolvers that are implemented with the controls &quot;to work&quot; are a win-win for the end user, the information center, and the company. The alternative is dissatisfied end users and costly/manual workarounds. Glad to see you spreading the gospel about the benefits for an integrated document delivery-link resolver relationship.  In my biased opinion (working for a document delivery provider: Reprints Desk), the two really to form a much stronger union and provide great benefit for delivering access to journal articles; However, the union definitely isn&#039;t &quot;right&quot; for every environment.</description>
		<content:encoded><![CDATA[<p>Steve: Great post and I think you&#39;re spot on in your first-comment reply.  link resolvers that are implemented with the controls &#8220;to work&#8221; are a win-win for the end user, the information center, and the company. The alternative is dissatisfied end users and costly/manual workarounds. Glad to see you spreading the gospel about the benefits for an integrated document delivery-link resolver relationship.  In my biased opinion (working for a document delivery provider: Reprints Desk), the two really to form a much stronger union and provide great benefit for delivering access to journal articles; However, the union definitely isn&#39;t &#8220;right&#8221; for every environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Palmer</title>
		<link>http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/comment-page-1/#comment-4529</link>
		<dc:creator>Ian Palmer</dc:creator>
		<pubDate>Sat, 15 Nov 2008 09:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/#comment-4529</guid>
		<description>Steve: Great post and I think you&#039;re spot on in your first-comment reply.  link resolvers that are implemented with the controls &quot;to work&quot; are a win-win for the end user, the information center, and the company. The alternative is dissatisfied end users and costly/manual workarounds. Glad to see you spreading the gospel about the benefits for an integrated document delivery-link resolver relationship.  In my biased opinion (working for a document delivery provider: Reprints Desk), the two really to form a much stronger union and provide great benefit for delivering access to journal articles; However, the union definitely isn&#039;t &quot;right&quot; for every environment.</description>
		<content:encoded><![CDATA[<p>Steve: Great post and I think you&#39;re spot on in your first-comment reply.  link resolvers that are implemented with the controls &#8220;to work&#8221; are a win-win for the end user, the information center, and the company. The alternative is dissatisfied end users and costly/manual workarounds. Glad to see you spreading the gospel about the benefits for an integrated document delivery-link resolver relationship.  In my biased opinion (working for a document delivery provider: Reprints Desk), the two really to form a much stronger union and provide great benefit for delivering access to journal articles; However, the union definitely isn&#39;t &#8220;right&#8221; for every environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FamManLib</title>
		<link>http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/comment-page-1/#comment-4511</link>
		<dc:creator>FamManLib</dc:creator>
		<pubDate>Tue, 28 Oct 2008 13:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/#comment-4511</guid>
		<description>Jonathan,&lt;br&gt;&lt;br&gt;It&#039;s not rocket science or whiz bang stuff unfortunately. We&#039;re making two&lt;br&gt;calls, one to the Journal Subscription API and another to the SFX API. In&lt;br&gt;addition we are requiring that the user inputs sufficiently complete&lt;br&gt;metadata. In other words we evaluate the data on-the-fly and will not even&lt;br&gt;bother with the API lookup if we don&#039;t have sufficient metadata to work&lt;br&gt;with.  For instance, if the user neglects to input pages or even just a&lt;br&gt;start page, then the lookup process won&#039;t even proceed.&lt;br&gt;&lt;br&gt;Steve</description>
		<content:encoded><![CDATA[<p>Jonathan,</p>
<p>It&#39;s not rocket science or whiz bang stuff unfortunately. We&#39;re making two<br />calls, one to the Journal Subscription API and another to the SFX API. In<br />addition we are requiring that the user inputs sufficiently complete<br />metadata. In other words we evaluate the data on-the-fly and will not even<br />bother with the API lookup if we don&#39;t have sufficient metadata to work<br />with.  For instance, if the user neglects to input pages or even just a<br />start page, then the lookup process won&#39;t even proceed.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://www.familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/comment-page-1/#comment-4509</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Tue, 28 Oct 2008 00:20:29 +0000</pubDate>
		<guid isPermaLink="false">http://familymanlibrarian.com/2008/10/26/dynamic-openurl-lookup-with-document-delivery/#comment-4509</guid>
		<description>Interesting. Can you provide more information about what you&#039;ve done to make the SFX link work more of the time?  Because, yeah, anyone that works with SFX knows the links don&#039;t work as often as we&#039;d like. So what did you do to improve things?</description>
		<content:encoded><![CDATA[<p>Interesting. Can you provide more information about what you&#39;ve done to make the SFX link work more of the time?  Because, yeah, anyone that works with SFX knows the links don&#39;t work as often as we&#39;d like. So what did you do to improve things?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

