<?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: Elsevier and RSS</title>
	<atom:link href="http://davidrothman.net/2006/07/17/elsevier-and-rss/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/</link>
	<description>Health Information &#124; Geekery</description>
	<lastBuildDate>Wed, 01 Feb 2012 21:49:12 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: davidrothman.net &#187; Blog Archive &#187; Scopus RSS: a very brief review</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-108</link>
		<dc:creator>davidrothman.net &#187; Blog Archive &#187; Scopus RSS: a very brief review</dc:creator>
		<pubDate>Tue, 25 Jul 2006 02:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-108</guid>
		<description>[...] At my request, Damien promptly set up temporary access to Scopus so I could check out and review its RSS features here. It is appropriate to again thank Damien for this. This sort of open communication between vendors and libraryfolk serves the interests of both, and his willingness to do this will always positively color my perception of the Scopus team at Elsevier.&#160; Marketing, PR, and Sales: Please take note of this. [...]</description>
		<content:encoded><![CDATA[<p>[...] At my request, Damien promptly set up temporary access to Scopus so I could check out and review its RSS features here. It is appropriate to again thank Damien for this. This sort of open communication between vendors and libraryfolk serves the interests of both, and his willingness to do this will always positively color my perception of the Scopus team at Elsevier.&nbsp; Marketing, PR, and Sales: Please take note of this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidrothman.net &#187; Blog Archive &#187; Notes on Scopus RSS features forthcoming</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-71</link>
		<dc:creator>davidrothman.net &#187; Blog Archive &#187; Notes on Scopus RSS features forthcoming</dc:creator>
		<pubDate>Wed, 19 Jul 2006 19:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-71</guid>
		<description>[...] Damien was good as his word, and has quickly arranged for me access to Scopus so I can review its RSS features. Expect notes on them here within the next week or so. [...]</description>
		<content:encoded><![CDATA[<p>[...] Damien was good as his word, and has quickly arranged for me access to Scopus so I can review its RSS features. Expect notes on them here within the next week or so. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Drew</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-62</link>
		<dc:creator>Bill Drew</dc:creator>
		<pubDate>Tue, 18 Jul 2006 17:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-62</guid>
		<description>My question is, why isn&#039;t in production now?</description>
		<content:encoded><![CDATA[<p>My question is, why isn&#8217;t in production now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-60</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Tue, 18 Jul 2006 15:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-60</guid>
		<description>Great!  Looking forward to it!  Also, my sincere apologies for having previously missppelled your name, Damien.  

Folks, expect a look at Scopus RSS in the reasonably near future!</description>
		<content:encoded><![CDATA[<p>Great!  Looking forward to it!  Also, my sincere apologies for having previously missppelled your name, Damien.  </p>
<p>Folks, expect a look at Scopus RSS in the reasonably near future!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: damien sherman</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-59</link>
		<dc:creator>damien sherman</dc:creator>
		<pubDate>Tue, 18 Jul 2006 15:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-59</guid>
		<description>Hi David

we are more than happy for you to take a look at our product and features, and we are interested to hear what you think of them/ it.

I am setting you up with review access as we speak. Details forthcoming.

Point taken about Elsevier needing to make up some ground in this area.

regards
damien</description>
		<content:encoded><![CDATA[<p>Hi David</p>
<p>we are more than happy for you to take a look at our product and features, and we are interested to hear what you think of them/ it.</p>
<p>I am setting you up with review access as we speak. Details forthcoming.</p>
<p>Point taken about Elsevier needing to make up some ground in this area.</p>
<p>regards<br />
damien</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hope Leman</title>
		<link>http://davidrothman.net/2006/07/17/elsevier-and-rss/comment-page-1/#comment-45</link>
		<dc:creator>Hope Leman</dc:creator>
		<pubDate>Mon, 17 Jul 2006 15:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2006/07/17/elsevier-and-rss/#comment-45</guid>
		<description>Elsevier needs to understand that people won’t subscribe to its incredibly expensive journals if they have never heard of the highly expensive journals. RSS feeds spread the word and generate interest and garner subscribers. Elsevier should set up RSS feeds to its tables of contents forthwith. Its secrecy is antiquated and only hurts it as a business.

Many libraries subscribe to many of Elsevier’s incredibly expensive journals but have no money left over for its other incredibly expensive products, like Scopus. How can librarians alert medical providers to interesting publications such as many of Elsevier’s are if they have no RSS feeds? Get with it, Elsevier. Your secrecy is only feeding the open access movement.</description>
		<content:encoded><![CDATA[<p>Elsevier needs to understand that people won’t subscribe to its incredibly expensive journals if they have never heard of the highly expensive journals. RSS feeds spread the word and generate interest and garner subscribers. Elsevier should set up RSS feeds to its tables of contents forthwith. Its secrecy is antiquated and only hurts it as a business.</p>
<p>Many libraries subscribe to many of Elsevier’s incredibly expensive journals but have no money left over for its other incredibly expensive products, like Scopus. How can librarians alert medical providers to interesting publications such as many of Elsevier’s are if they have no RSS feeds? Get with it, Elsevier. Your secrecy is only feeding the open access movement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

