Hi Hans, On Nov 26, 2011, at 12:32 AM, Hans Bakker wrote:
> Hi All, > > We have the need to be able to add pre-approved tags to products, content and > workeffort. > My guess is that you are implementing a backend workflow to approve products/contents/workefforts before they are allowed to be sold/published/used in production. in my opinion the three entities should be treated separately: * products: my preference is to use ProductCategory (with a new special productCategoryTypeId), the products in the category are the pre-approved ones; the advantages of this approach are: you can configure the system to have a different pre-approval for each catalog, or each product store, or simply one per product; the ProductCategoryMember.comments field could be used to store comments from the approver etc... * content: use the existing data model (ContentApproval etc...) * workeffort: use workeffort statuses (or WorkEffortReview etc...) Kind regards, Jacopo > We have a similar function already in the system with keywords. However this > is not pre-approved and less formal. I think we still can use this function > as long as we can distinguish the tags and the keywords. > > There fore I would like to propose to add a field to the keyword entities: > 'keywordType' with initially the type 'Tag' and empty or 'keyword' for the > current function. > > The keywordType itself and the tags can be defined in the entity Enumeration. > > Your opinions please? > > Regards, > Hans
