<?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"
	>
<channel>
	<title>Comments on: ResolveRef updated : now with auto-suggest and source code</title>
	<atom:link href="http://blog.pansapiens.com/2008/06/06/resolveref-updated-now-with-auto-suggest-and-source-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pansapiens.com/2008/06/06/resolveref-updated-now-with-auto-suggest-and-source-code/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 15:04:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: perry</title>
		<link>http://blog.pansapiens.com/2008/06/06/resolveref-updated-now-with-auto-suggest-and-source-code/#comment-107</link>
		<dc:creator>perry</dc:creator>
		<pubDate>Sat, 07 Jun 2008 09:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pansapiens.com/?p=56#comment-107</guid>
		<description>Thanks Alf ... I knew you would have a solution if anyone did.

Thinking about it more, I realize that it's not such a huge problem ... while in conversation scientists often refer to "PNAS", "JBC", and "JMB" (PubMed gets JMB 'wrong', and won't understand JBC at all), but if I actually look at reference lists in journals, those abbreviations are never used. It is always "J. Biol. Chem.", "J. Mol. Biol." and "Proc. Natl. Acad. Sci. U.S.A.". Not sure where I got it into my head that "JMB" was actually used in any real reference list.

The key "user story" I envisage for ResolveRef is something like:
"Dr X. has a printed journal article (or pdf) and quickly wants to link to an article in the reference list, then post that link to her blog. She quickly types the key details (journal/year/volume/page) directly into her blog (with the ResolveRef domain in front), presses "Preview" and tests the link. It forwards to the article as expected. Dr X. saves making a trip to HubMed (or maybe PubMed, or GoPubMed), and keeps working on her blog post". So as long as the user has the reference in front of them to copy, guessing at abbreviations like "JMB" shouldn't be a big issue.</description>
		<content:encoded><![CDATA[<p>Thanks Alf &#8230; I knew you would have a solution if anyone did.</p>
<p>Thinking about it more, I realize that it&#8217;s not such a huge problem &#8230; while in conversation scientists often refer to &#8220;PNAS&#8221;, &#8220;JBC&#8221;, and &#8220;JMB&#8221; (PubMed gets JMB &#8216;wrong&#8217;, and won&#8217;t understand JBC at all), but if I actually look at reference lists in journals, those abbreviations are never used. It is always &#8220;J. Biol. Chem.&#8221;, &#8220;J. Mol. Biol.&#8221; and &#8220;Proc. Natl. Acad. Sci. U.S.A.&#8221;. Not sure where I got it into my head that &#8220;JMB&#8221; was actually used in any real reference list.</p>
<p>The key &#8220;user story&#8221; I envisage for ResolveRef is something like:<br />
&#8220;Dr X. has a printed journal article (or pdf) and quickly wants to link to an article in the reference list, then post that link to her blog. She quickly types the key details (journal/year/volume/page) directly into her blog (with the ResolveRef domain in front), presses &#8220;Preview&#8221; and tests the link. It forwards to the article as expected. Dr X. saves making a trip to HubMed (or maybe PubMed, or GoPubMed), and keeps working on her blog post&#8221;. So as long as the user has the reference in front of them to copy, guessing at abbreviations like &#8220;JMB&#8221; shouldn&#8217;t be a big issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alf</title>
		<link>http://blog.pansapiens.com/2008/06/06/resolveref-updated-now-with-auto-suggest-and-source-code/#comment-104</link>
		<dc:creator>alf</dc:creator>
		<pubDate>Fri, 06 Jun 2008 10:05:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pansapiens.com/?p=56#comment-104</guid>
		<description>I could only find those flat-files too, but you could use something like http://tinyurl.com/6jar33 to see what PubMed expands a query to.</description>
		<content:encoded><![CDATA[<p>I could only find those flat-files too, but you could use something like <a href="http://tinyurl.com/6jar33" rel="nofollow">http://tinyurl.com/6jar33</a> to see what PubMed expands a query to.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
