<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: my del.icio.us issues, plus blog tagging</title>
	<link>http://libraryclips.blogsome.com/2006/05/05/my-delicious-issues-plus-blog-tagging/</link>
	<description>sharing ideas thoughts and feedback</description>
	<pubDate>Sat, 28 Nov 2009 13:41:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Ricardo Niederberger Cabral</title>
		<link>http://libraryclips.blogsome.com/2006/05/05/my-delicious-issues-plus-blog-tagging/#comment-32502</link>
		<pubDate>Sun, 08 Jun 2008 02:48:30 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2006/05/05/my-delicious-issues-plus-blog-tagging/#comment-32502</guid>
					<description>I've just written a web tool for cleaning your del.icio.us tags: it can detect and merge your duplicate tags automatically. Available at http://delicious.isnotworking.com/</description>
		<content:encoded><![CDATA[	<p>I&#8217;ve just written a web tool for cleaning your del.icio.us tags: it can detect and merge your duplicate tags automatically. Available at <a href='http://delicious.isnotworking.com/' rel='nofollow'>http://delicious.isnotworking.com/</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: i1277</title>
		<link>http://libraryclips.blogsome.com/2006/05/05/my-delicious-issues-plus-blog-tagging/#comment-31135</link>
		<pubDate>Sun, 14 May 2006 17:55:36 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2006/05/05/my-delicious-issues-plus-blog-tagging/#comment-31135</guid>
					<description>For del.icio.us to work there has to be a balance between the use being as simple as possible, yet with a sufficient level of &quot;return of investment&quot;. The easiness of tagging a page is the reason for the del.icio.us success in the first place, &lt;em&gt;but&lt;/em&gt; I agree the results can be pretty messy. Like with the  &quot;awkward tags&quot; (that aren't beneficial to the del.icio.us community, and perhaps just as important: are unintuitive for personal retrieving purposes). 

The flat &quot;all tags are equal&quot;-structure leaves no way to describe the relationships between tags. Unless one creates some ad-hoc-system there are no forms of qualification. A lot of context is peeled away, so I have to rely on my memory to tell if my weinberger tag signifies an item written &lt;em&gt;by&lt;/em&gt; Weinberger or &lt;em&gt;about&lt;/em&gt; Weinberger. 

Having to deal with a lot of fields might alienate users, but for me adding a few optional facet fields would be pretty handy. I'd like to be able to do see some simple facets: A &quot;what&quot; field (article? Blog post? Web site?), and a related source field (if it's a news site, which one?), a &quot;by&quot; field. These aren't always relevant or interesting, but I'd like to be able to sort content from my favourite writers or sources. (Ideally, these data should be automatically retrieveded from the document itself, as we move on to more structured websites). The regular tag field could then be left for subjects and descriptive words, much like today. 

As you point out in another post, each tags &quot;weighs&quot; just as much, which for most people will be a good thing because of the saved mental effort in having to calculate &quot;tag weight&quot;. Personally I'm using a primitive numeral ranking system in order to sort the more from the less important items.</description>
		<content:encoded><![CDATA[	<p>For del.icio.us to work there has to be a balance between the use being as simple as possible, yet with a sufficient level of &#8220;return of investment&#8221;. The easiness of tagging a page is the reason for the del.icio.us success in the first place, <em>but</em> I agree the results can be pretty messy. Like with the  &#8220;awkward tags&#8221; (that aren&#8217;t beneficial to the del.icio.us community, and perhaps just as important: are unintuitive for personal retrieving purposes). </p>
	<p>The flat &#8220;all tags are equal&#8221;-structure leaves no way to describe the relationships between tags. Unless one creates some ad-hoc-system there are no forms of qualification. A lot of context is peeled away, so I have to rely on my memory to tell if my weinberger tag signifies an item written <em>by</em> Weinberger or <em>about</em> Weinberger. </p>
	<p>Having to deal with a lot of fields might alienate users, but for me adding a few optional facet fields would be pretty handy. I&#8217;d like to be able to do see some simple facets: A &#8220;what&#8221; field (article? Blog post? Web site?), and a related source field (if it&#8217;s a news site, which one?), a &#8220;by&#8221; field. These aren&#8217;t always relevant or interesting, but I&#8217;d like to be able to sort content from my favourite writers or sources. (Ideally, these data should be automatically retrieveded from the document itself, as we move on to more structured websites). The regular tag field could then be left for subjects and descriptive words, much like today. </p>
	<p>As you point out in another post, each tags &#8220;weighs&#8221; just as much, which for most people will be a good thing because of the saved mental effort in having to calculate &#8220;tag weight&#8221;. Personally I&#8217;m using a primitive numeral ranking system in order to sort the more from the less important items.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
