<?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: Tag clouds</title>
	<atom:link href="http://freerangelibrarian.com/2007/10/07/tag-clouds/feed/" rel="self" type="application/rss+xml" />
	<link>http://freerangelibrarian.com/2007/10/07/tag-clouds/</link>
	<description>K.G. Schneider's blog on librarianship, writing, and everything else, since 2003.</description>
	<pubDate>Mon, 01 Dec 2008 23:16:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Anne Zarinnia</title>
		<link>http://freerangelibrarian.com/2007/10/07/tag-clouds/#comment-68747</link>
		<dc:creator>Anne Zarinnia</dc:creator>
		<pubDate>Thu, 11 Oct 2007 22:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/10/07/tag-clouds/#comment-68747</guid>
		<description>Plain folks who think have asked how to tag effectively.  They assume that, because I teach cataloging, I know!

I am thinking particularly of the student who managed my lab for five years, fell in love with all things Mac, and spent his spare time taking and sharing photographs on his own blog. After a while, he wanted to create tags that really did something productive.

Non-plain folks have been asserting rules of varying value. 

Plain folks have invented merged words, CamelFont, idjit words that they like, understand or can remember (Whats a mullet?). Non-plain sometimes deride.

Hey! Naked emperor really resonates - should it be two tags? "naked" "emperor" ???  What else might I want to combine with naked? Do I need naked for the idea? Aren't all emperors naked?

If we shortcut to lower case for everything, what should have upper case? Camels?  Or camels for camels and Camels for Camels.  Dromedaries anyone?? 

Will naked+emperor morph to an idea more easily expressed in my records as ne? nemp?? Will the people who network with me follow suit?

If we stick with the idea of  free flowing folksonomies, language change is likely to accelerate. All we need are the software people to put the popular options in front of us and Lakatos proff and refutation will rule. Should that have been "proof?" Or can I rely on Google to interpret my error?

If we want to help plain folks tag, it may well be that we offer some -simple- frameworks, e.g., metadata categories for images. Good luck! Or, just the simplest heuristics: 
- see what others have done, change it if you don't like it, stick with it if you do
-try to be consistent, consolidate occasionally
-dump the environments that constrain you
-look for the environments that let you connect to people with interesting tag clouds.

It is probably most useful at the moment to tolerate chaos and see what emerges. 

I wonder what you get if you search for nemp+mullets? Who posted those tags? When? What are their other interests? Maybe I missed all the really interesting nakedemperors! 

PS I begin cataloging class by using Flickr.</description>
		<content:encoded><![CDATA[<p>Plain folks who think have asked how to tag effectively.  They assume that, because I teach cataloging, I know!</p>
<p>I am thinking particularly of the student who managed my lab for five years, fell in love with all things Mac, and spent his spare time taking and sharing photographs on his own blog. After a while, he wanted to create tags that really did something productive.</p>
<p>Non-plain folks have been asserting rules of varying value. </p>
<p>Plain folks have invented merged words, CamelFont, idjit words that they like, understand or can remember (Whats a mullet?). Non-plain sometimes deride.</p>
<p>Hey! Naked emperor really resonates - should it be two tags? &#8220;naked&#8221; &#8220;emperor&#8221; ???  What else might I want to combine with naked? Do I need naked for the idea? Aren&#8217;t all emperors naked?</p>
<p>If we shortcut to lower case for everything, what should have upper case? Camels?  Or camels for camels and Camels for Camels.  Dromedaries anyone?? </p>
<p>Will naked+emperor morph to an idea more easily expressed in my records as ne? nemp?? Will the people who network with me follow suit?</p>
<p>If we stick with the idea of  free flowing folksonomies, language change is likely to accelerate. All we need are the software people to put the popular options in front of us and Lakatos proff and refutation will rule. Should that have been &#8220;proof?&#8221; Or can I rely on Google to interpret my error?</p>
<p>If we want to help plain folks tag, it may well be that we offer some -simple- frameworks, e.g., metadata categories for images. Good luck! Or, just the simplest heuristics:<br />
- see what others have done, change it if you don&#8217;t like it, stick with it if you do<br />
-try to be consistent, consolidate occasionally<br />
-dump the environments that constrain you<br />
-look for the environments that let you connect to people with interesting tag clouds.</p>
<p>It is probably most useful at the moment to tolerate chaos and see what emerges. </p>
<p>I wonder what you get if you search for nemp+mullets? Who posted those tags? When? What are their other interests? Maybe I missed all the really interesting nakedemperors! </p>
<p>PS I begin cataloging class by using Flickr.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Avi Rappoport</title>
		<link>http://freerangelibrarian.com/2007/10/07/tag-clouds/#comment-67912</link>
		<dc:creator>Avi Rappoport</dc:creator>
		<pubDate>Tue, 09 Oct 2007 19:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/2007/10/07/tag-clouds/#comment-67912</guid>
		<description>The new mullets!  Most people have no clue how to do tags, so they go all over the place.  CiteUSeek won't even let me delete wrong tags!</description>
		<content:encoded><![CDATA[<p>The new mullets!  Most people have no clue how to do tags, so they go all over the place.  CiteUSeek won&#8217;t even let me delete wrong tags!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.411 seconds -->
