+1 on tag groups. Honestly, I tell people when I teach them about tag groups that I think Jive ran out of time, since the way they are administered is so crappy (let's be brutally honest here). Tag groups could be an incredibly powerful feature, but you have to complete a steeplechase course to use them fully.

We've also had suggestions for being able to nest tag groups as well as apply more than one at a time. I'd also like to see tag groups tied in with a tag cloud, so instead of seeing a simple, unsortable list (oh, another pet peeve is that the lists of content can't be sorted), you could see a tag cloud, too.

I've just received another vote in favour of enhancing the tag filtering to facilitate "allowing AND’s between terms, or even full Boolean". According to Andrew Frangleton, one of our power users, "this way would improve the filtering characteristics".

My users frequently complain that they have no idea who can see their content.   We have a finely tunable permissions system, but there is no way for Joe User to know who else can see his content in a particular space.

I, admittedly, have no idea how to approach this.  Our system has thousands of internal users - Each in LDAP, Each in one or more various LDAP groups.  95% of those users don't even know what LDAP is, and the concept of "Groups", even in clearspace, doesn't stand out at all (that word is tied completely to the admin console.).. This is generally fine - they don't need to know about groups, but we definitely do have private spaces, and the members of those spaces don't know who can see that space, and who can see documents inside that space.  I can't imagine what interface feature would allow that.

We've taken the approach of insisting that users assume everything is readable by the entire community, unless they are informed otherwise.  But even if we say to Financing that they have a special private space where they talk about sensitive things like budgets, they are given no indication of this when posting a reply to a discussion.

Changing the focus slightly, since we're talking about confusing aspects and not feature requests - It's also quite confusing for a young space admin, when looking at the permissions for a space, because inherited permissions that are not 'anyone' or 'registered users' do not display unless you change them on that space.  I think it would be wise to have all inherited permissions display on the space permissions page.  (oops, feature request snuck in. )

Vinh-

Is there an equivalent for Jive SBS 3.0.X for this discussion? My usage of tag groups is more end user focused than employee focused.

When I saw Tag Groups I thought great!!!! Here's a way for us to suggest users what Tags to use. We can group tags together by topic. As they post they can pick one or more from each Tag group based on their root post.

Then those who visit the site looking for someone can go to their community and then filter by using the Tag Group Widget versus the Tag Cloud Widget. Communities with Tag Groups assigned have the Tag Group widget forced at the top of the both the Documents and Discussions widgets within a community. Using Tag Group as a navigation/search tool is completely useless in our instance. Let me explain our situation so you understand why.

We have essentially 3 Tag Groups:

1. Products/Models

2. Service Providers related to those Products/Models

3. List of Topics related to those Products/Models

As Tag Groups work now from a navigation/search tool perspective, sorting by tag group does nothing for the user as most posts have tags from two or more separate tag groups. If they have one from each of the three, then the all three lists will be the same. Only posts without tags or tags that aren't in the tag groups within that community would be excluded from the results.

I want users to be able to click on the first tag group and only see the various models in that community. The models they would click would be added in the header (similar to the tag cloud) so the user could see which tags they've chosen so far. Dynamically the results would resort. The user could then chose another product or switch to another tag group. When they switch tag groups they can then choose a service provider from the list. Again the tag is added to the header of the widget (as a bread crumb) and the results dynamically re-sort. Lastly, the user chooses the Topic Tag Group and chooses a tag that most resembles their issue. They now see their results that are tailored to their situation and they didn't need to guess what search terms to use. I find this better than the tag cloud widget as the user is focused to a pre defined list and they aren't overwhelmed with the tags being all combined.

Mark

I agree with Mark's post. If Tag Groups worked the way described there it would be a lot more convenient.  Tag Groups seem to work well when you have a large set of documents but not all of them are tagged by each of the Tag Groups. In the case noted above, when each item is tagged as a Product, Service, and Topic then the use of Tag groups is rather confusing. Perhaps, in part, because the tag cloud appears below the fold and to the right, rather than right underneath the tag group labels at the top/center of the screen.

One of the complaints we hear a lot is that users get lost in navigation once they are browsing a community and decide to see a user profile. There is no way back into the community except using the browser back button. This is not a problem for technology savvy users but it frustrates a lot of important people......

If you use Google Analytics there is no way to report Document usage because the URL scheme for documents /docs/DOC-ID does not relate to the community when we filter the usage report based on URL /community/research/*

This would be of a big help.....