We are hoping to use the Communites API groups functionality to 'tag' pages with particular groups in order to return user specific lists of relevant pages.
However, we would like the groups to be administered via the root page, but I am unsure as to how to avoid the group data being duplicated in the Epi DB, as I would like to get it straight from the Communites service. Do we need to simply catch the publish event on the root page and save the group items added in a list using the IGroupService (and deal with deletions etc), or is there a way to do that more directly?
I figured once they are saved away, I can then use a seleciton factory to query the IGroupService directly (possibly with some sort of caching) to allow the assignment of groups to a page.
We are hoping to use the Communites API groups functionality to 'tag' pages with particular groups in order to return user specific lists of relevant pages.
However, we would like the groups to be administered via the root page, but I am unsure as to how to avoid the group data being duplicated in the Epi DB, as I would like to get it straight from the Communites service. Do we need to simply catch the publish event on the root page and save the group items added in a list using the IGroupService (and deal with deletions etc), or is there a way to do that more directly?
I figured once they are saved away, I can then use a seleciton factory to query the IGroupService directly (possibly with some sort of caching) to allow the assignment of groups to a page.
Am I barking up the wrong tree?
any pointers much appreciated.
thanks