PloneFacetedClassification
Category: Layout and presentation, Miscellaneous
—
Other products by this author
Current release
No stable release available yet.
Experimental releases
Upcoming and alpha/beta/candidate releases
- Alpha releases should only be used for testing and development.
- Beta releases and Release Candidates are normally released for production testing, but should not be used on mission-critical sites.
- Always install on a separate test server first, and make sure you have proper backups before installing.
Release roadmap for PloneFacetedClassification…
Project Description
- Project resources
Purpose and use
Plone Faceted Classification allows users (with some editing privileges) to associate different words from different vocabularies previously defined (by a site manager) with ATVocabularyManager. The user can do it by the content classification tab where (s)he finds a list of keywords grouped in different vocabularies. The user has to check the keywords in to associate them with the content. It's not possible to propose a new keyword because the vocabularies are intentionally enforced to reduce the noise and increase the classification's accuracy.
In a general browsing page (one per site), whoever can browse all the contents classified with PFC at once. It's a very simple way to filter also a huge amount of contents, quickly find what you are looking for and, in the while, learn something more about the 'big picture' of the kind of data contained in the site.
To make PFC usable, first, the site manager must define many different vocabularies in ATVocabularyManager as (s)he needs. The site manager has to be careful about using the TreeVocabulary type and only the first 2 levels of the vocabulary (say vocabulary A and its defined keywords).
Then, in the ZMI, the manager has to add manually the portal action named "faceted_classification" to the portal types (s)he wants to classify with PFC.
Dependencies
ATVocabularyManager
Known issues
At the moment, it works only in a Plone 2.1.x instance.
Unfortunately the browsing page has serious performance issues when the vocabularies have many keywords so it is recommendable to use the Exhibit framework as browsing interface. We did so in a project for our customer and it works very well.