On Fri, Apr 24, 2009 at 9:37 AM, Vidar Ramdal <[email protected]> wrote: > There's one thing: It might be useful to let a tag (or a set of tags) > only be available for a certain branch of the resource tree. > Especially if a repository is hosting content for several independent > websites, you'd want each website to have its own tags tree. > Do you handle that in CQ5 - if so, how?
You can configure the tag editing field, where you assign tags to a page, to only allow the use of a certain tag namespace (eg. /etc/tags/mysitenamespace). We found it overkill to put such specific constraints (they'll change from one customer to the other) directly into the content model. Regards, Alex -- Alexander Klimetschek [email protected]
