Vocabulary – ERP Content Classification and tags

This post describes a concept called VOCABULARY. It helps iDempiere admins to categorise records from simple classification to  awesome multi-perspective catalogisation  or  modern  CMS tagging solution.


After I analyzed our customers´ requirements about implementing multiple stores into Magento and iDempiere, the first important question was how should we categorise our products in a modern way. I’ve also asked some other people about their experiences on iDempiere´s forum thread. The top contributor Deepak from Logilite has recommended us to use Product Category for Accounting and Legacy categorization and  implement another solution for better categorisation. For better understanding: Product Category has one perspective to categorise products and it also has a Parent Category, which means that it is able  to implement a tree structure, but we can only define one structure. To make a long story short – we can´t implement multiple stores in this way.

Our requirements about the project

We´ve  made a requirement analysis and the following tools were classified as “must have”.

  • For eCommerce usage – each webstore should have its own tree category – so 1 product must be categorised into multiple trees
  • The solution should be implemented for feature usage by creating a so called “independent product”, which has to support any further database table.
  • Users want to assign products in batches – like “Mass Update”

Collect motivations

Some years ago my company implemented Alfresco (an open platform for business software) and Liferay (a free and open source enterprise portal software product). We also use WordPress, which works very well. My experiences from the world of CMS gave me a good starting point. However, there are the standards  – with the similar concept – where the content can be assigned to categories, which are organised into the tree structure.

The proof about the efficiency of the concept

We´ve designed 3 main new objects: Vocabulary and Classification and Classification Instance. Vocabulary defines new classification perspective  and then creates the root and the tree structure.




Example structure

Website Catalog 2015 Website Catalog 2016
  • cat11
    • cat 11A
    • cat 11B
  • cat12
  • cat13
  • cat 21
    • cat 21A
    • cat 21B
  • cat 22
  • cat 23

How to improve the usage of the Vocabulary by iDempiere

The application can be used in any possible way,  because it was designed for common usage. Common usage means: Simply create a new vocabulary, select the table you want, define classification entries and organise them into the tree.

Price Schema – to create a new price list schema, you just have to add a new line, enter sequence and select between Product Category, Vocabulary and the tree.

New Module tree for DMS – We are working on a DMS plugin (with Deepak from Logilite) – Yesterday we had a review about our concept and – in context of massive content classification –  we´ve found out that it could be applied with a high potential. Of course we need to some other requirement Analysis as well. It´s quite plausible that we don’t need to implement other new features here.

Mass Update Classifications –  hundreds or thousands of products can be classified and later searched by only a few clicks.


Select Classification Tree – As Vocabulary included hundreds of records we have made an another improvement – with custom field type – available here. To the users:  if you are searching a product then first select vocabulary named “Product Catalog 2015”,  then select the value and the exact category you want.


When will it be available for the community?

The project is on its good way to publish it to the public, but it needs time and work.  By sponsorship/supported development we are able to make it available as a plugin or to apply further development. If you have got any questions about the commercial availability of the project, feel free to check my website www.cloudempiere.com