I really like this image on the structure of HCMS. Does there exist a similar architecture image but then about products, product tags, etc?
Hey Thijs,
Does this help?
Product tags and product properties (M5219 and M4991)
Product tags are used to tag products. An example for a tag is “used product” or “TV” or “Camera”.
Product properties (Product answer product properties) are used to store product specific features. For example, “Storage : 2GB”, “Screensize 34 inch”.
A product property is actually an answer to a question for a specific product. Questions and answers are a generic Novulo component. In this case, “Storage” is a question. The product specific answer is “2GB”. For a question, one can prepare answer scales to simplify answering. For example, an answer scale for the question “storage” could be a list of possible answers: 16GB, 32GB, 64GB etc…
Tags can be linked to groups of questions. For example, for the tag “TV” one can link a group of TV specific questions like screen size, connections, Wifi yes/no, brand, warranty etc.
When a product is linked to a tag that is also linked to a group of questions, then these questions can be answered for the product, resulting in product properties (Product answer product properties)
In my opinion the current data model is confusing, mainly because of inconsistent naming of the concepts, features and diverging labels in the components. Therefore, I would like to suggest the following renaming:
This already clarifies a lot, thanks @j.batzke
