We're very keen at Plusnet to create a ranking structure that is focussed around valuable posts IE kudos/accepted solutions. I can see from the standard Rankings set up that logins/posts/time logged in are the basics - how do I include kudos/accepted solutions in there?
Also, what are your suggestions in terms of an engaging ranking structure? I'm keen to keep the initial levels relatively easy to attain to keep people coming back before making it a little more difficult to rank up as we get half way and beyond?
All help appreciated!
Yes, it is possible to include kudos and solutions into the ranking formulas, as well as other user activity metrics. Please refer to the TKB article here: Include user metrics in your ranking formulas
I hope this helps!
As far as scaling the structure goes, you're on the right track in the thinking that it should be easy at first and get progressively harder as a user continues up the curve. Remember that Solutions are harder to obtain than Kudos and should also be weighed accordingly.
Make your best guess about what the scaling factor is for each criteria and then monitor it closely to see if users are outpacing it or getting stuck because the gaps are too wide.
You're certainly on the right track @PlusnetLiam.
Here's an example of a ranking formula for a senior user.
(((posts - deleted_posts) + net_idea_threads) >= 100) && (registrationAge >= 125000) && ((net_kudos_weight_received + (net_accepted_solutions*10)) >= 50)
It means that the user would have to have made 100 posts, have been a member for around 3 months, and have received at least 50 points. You get one point for each kudos earned and 10 for each accepted solution.
For the structure, you're absolutely right that you want to have a few relatively easy ranks early on to engage users and provide some early reward. Then you want to make it progressively harder to move up through the ranks. You also might want to look at recognising and rewarding particular kinds of users - for example, users that only browse rather than post, or users that specialise in certain types of contributions such as ideas or knowledge base articles.
You also want to ensure that you have some headroom at the top of your ranking structure so that you can add additional ranks in coming years if need be. You don't want your superusers to hit a ceiling too early and then have nothing to motivate them to keep going.
And have you thought of a theme for the names of your ranks? Perhaps something that is unique to your community and will be instantly recognisable and understandable by the vast majority of your members?
Hope that's helpful.
Further to this I'm trying to create some rank formulas and wondered if you could verify whether the below is correct:
To obtain rank X you must have 20000 posts, 500 accepted solutions and 1000 Kudos recieved.
((posts – deleted_posts) >= 20000) && ((net_accepted_solutions*10) >=500) && ((net_kudos_weight received) >=1000)
Is this formula correct?
Thanks for your reply, I've been using this but I can't see any net_links within there. Also I've multiplied it by 10 as @JasonHill mentioned "You get one point for each kudos earned and 10 for each accepted solution."
Ah so would I have to have it as:
((posts – deleted_posts) >= 20000) && ((net_accepted_solutions) >=5000) && ((net_kudos_weight received) >=1000)
Would 5000 net accepted solutions would actually be 500?
To me, your rank formula seems to be based on metrics.
The definition for the net_accepted solutions is: Net Accepted Solutions: The number of messages written and accepted by anyone in the community, minus the number of solutions that were revoked. This is the net change in the total number of accepted solutions in a given time period or for a given author/role.
If your criteria are 500 accepted solutions, then the formula should be
It looks like @JasonHill is using a system of points where he value more the accepted solution (time 10).