I really love this module. I'm planning on using it for an upcoming project, but I've encountered a bit of a problem. The project I'm working on is a user-generated-content site. We want all of the users on the website to be able to tag content other users have created, your module provides this functionality perfectly. This data will be used to create navigation, search and 'related content' blocks. The problem occurs when you have to judge which tags are more relavent than others. Because our users aren't specifically trusted—anyone can create an account—we need a way of deciding which tags are actually relavent to the content, and how strong that relevancy is.

A solution to that problem would be using Voting API to let users +1/-1 tags. This would allow: the phasing out of certain tags via a threshold and serve as a guide as to which tags are most relavent.

Is anyone aware of weither this functionality is planned or available in another contributed module?

Thanks!

Comments

chaps2’s picture

chaps2 commented

You've hit the nail on the head. Community tagging is all about getting as many of your users involved in tagging content, and yet the more people you have tagging, the less confidence you have that their tags will be appropriate - e.g. relevant, polite, non-spam, spelt correctly etc. Which is where tag "moderation" plays it's part, and why much of 6.x-2.x-dev development has focussed on this via Unitag integration, Rules integration, and node term/community tag synchronisation. Docs to follow...

What you suggest is a form of "peer moderation" and is a commonly used and effective form of moderation particularly on large sites. I've been planning to look into this. If it doesn't look too tricky I will add it to 2.x-dev.

calte’s picture

calte commented

Are you going to integrate with Voting API to do this? I think thats the best solution from my perspective.
Will you be waiting for a D7 release of Unitag before launching 7.x-2.x?

Thanks for your quick reply. If you need assistance theming this portion of the module I'm a graphic designer and would be willing to help out anyway I can.

chaps2’s picture

chaps2 commented

For inspiration I usually turn to the website of a well known online bookseller. Their implementation isn't so much of a classic vote +1/-1 although the UI initially suggests that with a agree/disagree prompt. What happens when you agree with a tag is that you effectively add the tag yourself. Which makes a lot of sense. To disagree with a tag on the other hand is not the same as un-tagging it. You can't disagree with your own tag - you must untag it first. Again this makes a lot of sense!

So one could argue that CT already does the +1/agree side of things, it just needs an extra bit of UI to present the "tag with existing tag" in a different way. The -1 or disagree op is new ground however. The simplest implementation would involve a new sub-module which would maintain a new "anti-tags" table to store all the -1's. In terms of close integration with the main CT module including it's views handlers this would be the best approach. The Voting API could be used but integration would come at a higher cost and it introduces another dependency for what I'd like to see as a key feature of community tags.

That's not to say CT shouldn't integrate with Voting API - it could actually be used as a backend for community tags! I just wouldn't want to depend on it.

So I'm curious as to why you want/need Voting API integration and ideally what sort of level of integration you're after?

Regarding 7.x-2.x and Unitag - I won't be waiting for a D7 version of Unitag - the Unitag integration is implemented as a sub-module which can be converted as and when Unitag D7 is released.

And finally, thanks for your offer of help with theming. Any ideas or suggestions would be very welcome, or you might want to wait until we have a working +1/-1 UI to theme up!

MGParisi’s picture

MGParisi commented

I want Unitag, where is it at in the D7 release?

Subscribe:)