On Nov 29, 2011, at 7:39 AM, Hans Bakker wrote: >> >> 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. > > Then i explained myself badly. The approval of the tags is important, not the > approval of the products content or workeffort. Tags are intended to be used > for grouping and selection only, like keywords but more organized and be able > to improve searching combining the 2 possibilities.
Ah I see now, I actually misunderstood your initial mail: so in this context "pre-approval" means a "pre-defined" list of tags that can be selected, for example from a drop down field. If my understanding is right then yes, I think that what you proposed is a good solution: adding a new enumeration type (or entity like KeywordType) and then a new field to the various *Keyword entities you want to extend. If the field is null or equals to "KEYWORD" (or similar) then the system treats the record as it currently does; if the field is set to the new type then your new logic is used. Kind regards, Jacopo
