Products.PloneKeywordManager 2.0

Plone Keyword Manager allows you to change, merge and delete keywords in Plone and updates all corresponding objects automatically. It uses a similiarity search to support you in identifying similar keywords. Keywords can be cleaned up from time to time by a site manager to create a consistent vocabulary.

Plone Keyword Manager

Plone Keyword Manager allows you to change, merge and delete keywords (aka tags or subjects) in Plone and updates all corresponding objects automatically. It uses a similiarity search to support you in identifying similar keywords. PloneKeywordManager helps you to build an inductive vocabulary with several people working on the same Plone site. Keywords can be cleaned up from time to time by a site-manager to create a consistent vocabulary.

Plone Keyword Manager is a quite simple solution to a major problem in the real world use of Plone: If you can’t work with restricted vocbularies, your keyword-vocabulary will get duplicate entries very quickly - depending on your authors’ interpretation of existing keywords.

Installation

In your buildout add Products.PloneKeywordManager to your instances eggs section. Run buildout. Activate it at Site Setups Add Ons page.

Usage

After installing, you will find an entry in Site Setup a section called Keyword Manager. Inside, you will see an alphabetical listing and a selection for all keywords existing in your site.

Use the last one to see similar terms for a single keyword. Use the former one if you want to see a list of all keywords starting with letter ‘b’, click it. The Plone Keyword Manager will then search all keywords starting with ‘b’ and will also look for similar keywords. You can now select several keywords and delete them for example. If you only want to change a single keyword, select it, then enter the new keyword and click on merge. If you want to merge several keywords into one new one, select them, enter the new keyword and click on merge.

The last selected keyword is entered automatically into the textbox if JavaScript is enabled. This may be irritating at first glance, but you’ll learn to appreciate quite fast. If you use it the right way, you don’t have to copy&paste into the textbox. Try it yourself, you’ll get the idea behind it…

For developer and integrator

You can also use KeywordManager to import your keywords with genericsetup. Just add a keywords.txt in your profile with one keyword per line. This step add or update a Document with an id to ‘keywords’. Let it in private state so only the administrator will be able to manage it.

Source Code

Source code of this project is in the Plone Collective

For instructions how to contribute please read the Collective Information Page

Further development focuses on Plone 4.2 and higher.

Credits

PloneKeywordManager was mainly coded by Maik Jablonski during the Plone Paderborn Sprint (September 2003), founded by the Bertelsmann Foundation.

Main code – Maik Jablonski

User Interface updates and Setup Code – Alexander Limi from Plone Solutions.

Thanks to Joe Geldart from “Netalley Networks”:http://www.netalleynetworks.com for updating the template to Plone 2.0 format.

We would also like to thank Maik for letting us put this code in the Collective - so it can be improved and expanded by the Collective developers.

Changelog

2.0 (2013-04-24)

• take plone.app.multilingual into acount and set Language=all on change. [jensens]

• Use png icon as gif icon has been removed. [thomasdesvenain]

• Fix index update on keyword delete not to reindex all attributes. [leorochael]

• Add support for dexterity (and generic DublinCoreImpl subclasses). [leorochael]

• Tests use now plone.app.testing; test coverage improved. [hvelarde]

• Fix package distribution. [hvelarde]

• Do not create a keywords Document in the plone-site in case the keywords.txt file is empty. (useful for sites not having Document globally allowed) [fRiSi]

• Allow Site Administrators too access the keyword managment [fRiSi]

• Make installation possible for dexterity-based Documents [pysailor]

1.9 (2011-06-22)

• Fixed critical error at index update. [thomasdesvenain]

• Upgrade imports for Zope 2.13. Remove deprecation warnings. [toutpt]

1.8 (2011-04-08)

• Add tests related to skins-directories. [WouterVH]

• remove old-style Install.py. [WouterVH]

• Add uninstall-profile. [WouterVH]

• Fix marker-file for setuphandlers.py. [WouterVH]

• Add MANIFEST.in to include docs in release. [WouterVH]

• Upgrade imports for Zope 2.13. Remove deprecation warnings. [thomasdesvenain]

• Manage python-Levenshtein dependency as a setuptools extras_require. [thomasdesvenain]

• French translation. [thomasdesvenain]

• Internationalization fixes. [thomasdesvenain]

• Added the z3c.autoinclude entry point so this package is automatically loaded on Plone 3.3 and above. [WouterVH]

• Remove the old-style refresh.txt and version.txt. Version is now specified in setup.py [WouterVH]

• Cleanup install-instructions. [WouterVH]

1.7 (20/08/2010)

• Added ability to mix unicode and non-unicode keywords and changes. Fixes a bug with collective.dancing (and plone.z3cform) upgrading form inputs to unicode automagically. [dunlapm]

• Restify the CHANGES.txt file. [toutpt]

• Add keywords import through genericsetup. [toutpt]

• Add a default profile based on Extensions/Install.py. [toutpt]

• remove zope2 interface. [toutpt]

1.6 (19/03/2009)

• Fixed handling of non-ASCII Keywords in Controller Python Scripts prefs_keywords_action_change.cpy and prefs_keywords_action_delete.cpy [disko]

• Added tests for the above mentioned bugfixes. [disko]

• Added German translation. [disko]

1.6b2 (15-11-2008)

• No longer assumes that the index name is the same as the name of the underlying schema field. [jessesnyder]

1.6b1 (09-09-2008)

• Eggification from PloneKeywordManager into Products.PloneKeywordManager. This package is only supported for Plone 3 now. It may or may not work in Plone 2.5. [dunlapm]

• Added support for multiple keyword indexes. If you have more than one keyword field on your content type(s) then you will still be able to manage all of your keywords. If you only use the single default field then you will get the normal interface.

1.5-alpha1 (28-11-2007)

• Plone 2.5 and Plone 3 compatibility for product PloneKeywordManager. [glenfant]

0.4 (unknown)

• Added Brazilian Portuguese i18n support. [Rafahela Bazzanella <[e-mail]>]

0.3 (05-04-2005)

• Refactored code to run from a portal tool.

• Minor clean ups.

• Introduced the permission “Manage Keywords” to have better control about who can manage keywords.