<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
xmlns:media="http://search.yahoo.com/mrss/" 

	>
<channel>
	<title>Comments on: Visualizing Citations &#8211; Citeology project from Autodesk</title>
	<atom:link href="http://thesocietypages.org/graphicsociology/2012/01/04/visualizing-citations-citeology-project-from-autodesk/feed/" rel="self" type="application/rss+xml" />
	<link>http://thesocietypages.org/graphicsociology/2012/01/04/visualizing-citations-citeology-project-from-autodesk/</link>
	<description>Analyzing the visual presentation of social data. Each post, Laura Nor&#233;n takes a chart, table, interactive graphic or other display of sociologically relevant data and evaluates the success of the graphic.</description>
	<lastBuildDate>Sat, 31 Jan 2015 21:29:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Letta Page</title>
		<link>http://thesocietypages.org/graphicsociology/2012/01/04/visualizing-citations-citeology-project-from-autodesk/comment-page-1/#comment-10428</link>
		<dc:creator><![CDATA[Letta Page]]></dc:creator>
		<pubDate>Wed, 04 Jan 2012 15:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://thesocietypages.org/graphicsociology/?p=1969#comment-10428</guid>
		<description><![CDATA[As I just commented over at The Editor&#039;s Desk on a post of Chris Uggen&#039;s about Google Scholar and high-impact publication, my favorite part of your analysis here really gets at what (at least I think) TheSocietyPages is about:

&quot;It is a little unclear just how important it is to understand the boundaries of a discipline. For an academic trying to shape a particular kind of career... I guess it would be nice to have something like this so they can figure out what the core of popular articles has been so they can get themselves in the stream they’d like to be in. On the other hand, I’m not sure it is always good for academics to create loops in which everyone is citing the things everyone else in their circle has read. Seems problematically narrow to me.&quot;

Hear, hear!]]></description>
		<content:encoded><![CDATA[<p>As I just commented over at The Editor&#8217;s Desk on a post of Chris Uggen&#8217;s about Google Scholar and high-impact publication, my favorite part of your analysis here really gets at what (at least I think) TheSocietyPages is about:</p>
<p>&#8220;It is a little unclear just how important it is to understand the boundaries of a discipline. For an academic trying to shape a particular kind of career&#8230; I guess it would be nice to have something like this so they can figure out what the core of popular articles has been so they can get themselves in the stream they’d like to be in. On the other hand, I’m not sure it is always good for academics to create loops in which everyone is citing the things everyone else in their circle has read. Seems problematically narrow to me.&#8221;</p>
<p>Hear, hear!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Matejka</title>
		<link>http://thesocietypages.org/graphicsociology/2012/01/04/visualizing-citations-citeology-project-from-autodesk/comment-page-1/#comment-10427</link>
		<dc:creator><![CDATA[Justin Matejka]]></dc:creator>
		<pubDate>Wed, 04 Jan 2012 15:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://thesocietypages.org/graphicsociology/?p=1969#comment-10427</guid>
		<description><![CDATA[I&#039;m glad that you find Citeology interesting, and I think this is an excellent analysis of the tool. Thanks for taking the time to write about it.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m glad that you find Citeology interesting, and I think this is an excellent analysis of the tool. Thanks for taking the time to write about it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
