<?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: How Plone Keywords Should Work</title>
	<atom:link href="http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/</link>
	<description>Politics, the environment, technology, activism. And stuff.</description>
	<pubDate>Sun, 07 Sep 2008 07:02:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Grouped Plone keywords &#171; Simbiosis</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-327050</link>
		<dc:creator>Grouped Plone keywords &#171; Simbiosis</dc:creator>
		<pubDate>Thu, 05 Jul 2007 12:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-327050</guid>
		<description>&lt;p&gt;[...] not great. There is a few alternative such as Portal Taxonomy, and it is quite well discussed elsewhere. However, most systems I&#8217;ve seen replace the keywords system entirely, meaning that only [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] not great. There is a few alternative such as Portal Taxonomy, and it is quite well discussed elsewhere. However, most systems I&#8217;ve seen replace the keywords system entirely, meaning that only [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Gehrich</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-322490</link>
		<dc:creator>Greg Gehrich</dc:creator>
		<pubDate>Wed, 27 Jun 2007 18:46:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-322490</guid>
		<description>&lt;p&gt;I use keywords extensively to control which items show up in different SmartFolders for a small group working on a project.  This is working very well with a few exceptions.
1. Unable to mass tag as mentioned above.
2. Unable to add keywords when editing (should be fixed soon).
3. I added the keyword display at the top per Shane's how-to.  It will be helpful in our use case and is consistent with how tags work with my personal stuff.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I use keywords extensively to control which items show up in different SmartFolders for a small group working on a project.  This is working very well with a few exceptions.<br />
1. Unable to mass tag as mentioned above.<br />
2. Unable to add keywords when editing (should be fixed soon).<br />
3. I added the keyword display at the top per Shane&#8217;s how-to.  It will be helpful in our use case and is consistent with how tags work with my personal stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Stahl</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321708</link>
		<dc:creator>Jon Stahl</dc:creator>
		<pubDate>Tue, 26 Jun 2007 23:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321708</guid>
		<description>&lt;p&gt;@Alec - thanks for the wise perspective!  :-)  I think free-text entry is actually a good thing in this use case, but a toggable switch is definitely a good idea.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Alec - thanks for the wise perspective!  <img src='http://blogs.onenw.org/jon/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  I think free-text entry is actually a good thing in this use case, but a toggable switch is definitely a good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Stahl&#8217;s Journal &#187; Blog Archive &#187; Plone Taxonomy, Revisted</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321654</link>
		<dc:creator>Jon Stahl&#8217;s Journal &#187; Blog Archive &#187; Plone Taxonomy, Revisted</dc:creator>
		<pubDate>Tue, 26 Jun 2007 21:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321654</guid>
		<description>&lt;p&gt;[...] you&#8217;re interested in this topic, you may also want to see my recent musings about Plone Keywords, which is somewhat [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] you&#8217;re interested in this topic, you may also want to see my recent musings about Plone Keywords, which is somewhat [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alec Mitchell</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321537</link>
		<dc:creator>Alec Mitchell</dc:creator>
		<pubDate>Tue, 26 Jun 2007 18:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-321537</guid>
		<description>&lt;p&gt;As the original author of the AT autocomplete widget, I'd recommend against using it. :-)  It's ancient stuff, and based on some old js that wasn't so nice to begin with.  However, something like this could be built using KSS fairly easy.&lt;/p&gt;

&lt;p&gt;Ideally, the widget used would have a mode that disallowed free-form keyword entry based on permission/role/condition, though an autocomplete that doesn't allow arbitrary text entry is probably a tricky thing to get right.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As the original author of the AT autocomplete widget, I&#8217;d recommend against using it. <img src='http://blogs.onenw.org/jon/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  It&#8217;s ancient stuff, and based on some old js that wasn&#8217;t so nice to begin with.  However, something like this could be built using KSS fairly easy.</p>
<p>Ideally, the widget used would have a mode that disallowed free-form keyword entry based on permission/role/condition, though an autocomplete that doesn&#8217;t allow arbitrary text entry is probably a tricky thing to get right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Papendieck</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-320413</link>
		<dc:creator>Adam Papendieck</dc:creator>
		<pubDate>Mon, 25 Jun 2007 20:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-320413</guid>
		<description>&lt;p&gt;5 seems like an extremely useful tool. We make concerted use of Plone as a document management system.  Plone is very good for organizing and re-organizing semi-structured content, but there is no way to apply keywords to a large number of documents in a single operation. I think a lot of people would find such functionality useful for breaking down folders of semi-organized documents to present targeted subsets.&lt;/p&gt;

&lt;p&gt;The "tagging interface" on the "ImageRepository" product is noteworthy in this regard. http://plone.org/products/imagerepository&lt;/p&gt;

&lt;p&gt;In the absence of the ideal--a dedicated librarian capable of maintaining a formal taxonomy--these semi-formal, rapidly updated folksonomies (using tags) are extremely important. They can be managed with the  "PloneKeywordManager"product.&lt;/p&gt;

&lt;p&gt;Nice to hear #4 is underway!&lt;/p&gt;

&lt;p&gt;Adam&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>5 seems like an extremely useful tool. We make concerted use of Plone as a document management system.  Plone is very good for organizing and re-organizing semi-structured content, but there is no way to apply keywords to a large number of documents in a single operation. I think a lot of people would find such functionality useful for breaking down folders of semi-organized documents to present targeted subsets.</p>
<p>The &#8220;tagging interface&#8221; on the &#8220;ImageRepository&#8221; product is noteworthy in this regard. <a href="http://plone.org/products/imagerepository" rel="nofollow">http://plone.org/products/imagerepository</a></p>
<p>In the absence of the ideal&#8211;a dedicated librarian capable of maintaining a formal taxonomy&#8211;these semi-formal, rapidly updated folksonomies (using tags) are extremely important. They can be managed with the  &#8220;PloneKeywordManager&#8221;product.</p>
<p>Nice to hear #4 is underway!</p>
<p>Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wichert Akkerman</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-318136</link>
		<dc:creator>Wichert Akkerman</dc:creator>
		<pubDate>Sat, 23 Jun 2007 12:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-318136</guid>
		<description>&lt;p&gt;John: I'm happy to see you almost agree. However I think the current behaviour which Alex just changed is wrong. In my experience the majority of people do &lt;em&gt;not&lt;/em&gt; want to see keywords shown on all pages, so the right default imho is to not show them but make it easy to add them. And the way Alex added them does not use a new viewlet, so we'll be reverting that.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>John: I&#8217;m happy to see you almost agree. However I think the current behaviour which Alex just changed is wrong. In my experience the majority of people do <em>not</em> want to see keywords shown on all pages, so the right default imho is to not show them but make it easy to add them. And the way Alex added them does not use a new viewlet, so we&#8217;ll be reverting that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Limi</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-318010</link>
		<dc:creator>Alexander Limi</dc:creator>
		<pubDate>Sat, 23 Jun 2007 05:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-318010</guid>
		<description>&lt;p&gt;Item #4 in your list is now in SVN, along with an improved search results page. Enjoy! :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Item #4 in your list is now in SVN, along with an improved search results page. Enjoy! <img src='http://blogs.onenw.org/jon/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Stahl</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-317898</link>
		<dc:creator>Jon Stahl</dc:creator>
		<pubDate>Sat, 23 Jun 2007 01:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-317898</guid>
		<description>&lt;p&gt;@Wichert
Yeah, not everyone will want to expose keywords to the public, but with viewlet manager, it will be very easy to turn public viewing of keywords off.&lt;br /&gt;
@ Sean
You make an important point, which is that hierarchical vocabularies are important too.  I think these are separate from simple keywords, but Plone should definitely have a reasonable out of the box story for these tool.  Drupal's flexible "taxonomy" module provides simple hierarchical vocabularies and is one of its stronger features. I've long thought it would be a great idea to steal.  Those with even more formal ontology needs would still be free to use a more complex package like PloneOntology.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Wichert<br />
Yeah, not everyone will want to expose keywords to the public, but with viewlet manager, it will be very easy to turn public viewing of keywords off.<br />
@ Sean<br />
You make an important point, which is that hierarchical vocabularies are important too.  I think these are separate from simple keywords, but Plone should definitely have a reasonable out of the box story for these tool.  Drupal&#8217;s flexible &#8220;taxonomy&#8221; module provides simple hierarchical vocabularies and is one of its stronger features. I&#8217;ve long thought it would be a great idea to steal.  Those with even more formal ontology needs would still be free to use a more complex package like PloneOntology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Stahl</title>
		<link>http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-317647</link>
		<dc:creator>Jon Stahl</dc:creator>
		<pubDate>Fri, 22 Jun 2007 15:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.onenw.org/jon/archives/2007/06/21/how-plone-keywords-should-work/#comment-317647</guid>
		<description>&lt;p&gt;@ Christian
I was just playing about with Haystack "old version" yesterday -- after resolving dependency hell, I was able to get it running. (Yay!)  It seemed to do a decent job of  generating summaries, but it didn't seem to do a very good job of generating keywords.  (I've heard the same from Hector Velarde, who has been using it in production at a big newspaper site in Mexico City.)&lt;br /&gt;
I think this is one of the big reasons Ben moved towards a different approach for Haystack 2.0, but I'm not sure if Haystack 2.0 was every really finished.  I do know that Ben Saller, its author, is off working on the OLPC project, and hasn't made a checkin to Haystack since February.&lt;/p&gt;

&lt;p&gt;@ Alex
Cool -- glad to hear that at least the template issues are being solve.  That's great.  RE: widget changes -- that's OK.  I don't even know if the Autocomplete Widget is all that modern -- it may need/deserve to be redone with KSS.  We may improvise in the meantime, which will be a fun experiment. :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@ Christian<br />
I was just playing about with Haystack &#8220;old version&#8221; yesterday &#8212; after resolving dependency hell, I was able to get it running. (Yay!)  It seemed to do a decent job of  generating summaries, but it didn&#8217;t seem to do a very good job of generating keywords.  (I&#8217;ve heard the same from Hector Velarde, who has been using it in production at a big newspaper site in Mexico City.)<br />
I think this is one of the big reasons Ben moved towards a different approach for Haystack 2.0, but I&#8217;m not sure if Haystack 2.0 was every really finished.  I do know that Ben Saller, its author, is off working on the OLPC project, and hasn&#8217;t made a checkin to Haystack since February.</p>
<p>@ Alex<br />
Cool &#8212; glad to hear that at least the template issues are being solve.  That&#8217;s great.  RE: widget changes &#8212; that&#8217;s OK.  I don&#8217;t even know if the Autocomplete Widget is all that modern &#8212; it may need/deserve to be redone with KSS.  We may improvise in the meantime, which will be a fun experiment. <img src='http://blogs.onenw.org/jon/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
