Posted by heinzmilitar on June 9, 2008 at 5:37am
I've created a new module...am still waiting for Drupal.org to accept it...
Nodepoint is the same with userpoint module, but this module allows nodes to have points...
The pratical use of this is when a user gets a service on a certain node his userpoint will be deducted based on the nodepoints of the node...
let me know your toughts pinoys... Im working on new customized modules for BMF (Cebu-based)...
Next i will create its nodepoint services (XMLRPC or JSON servers). Any body got an idea on this?
Comments
what is the difference/s
what is the difference/s between nodepoints and fivestar voting?
collectivetech.org
Technology for organizations. Open Source. Consultancy. Training.
collectivetech.org
Technology for organizations. Open Source. Consultancy. Training.
Difference
The difference between nodepoints and fivestar rating, well, nodepoints does not used voting api module, this is independent to voting api. While fivestar module and other modules such as vote up/down package module, latest and greatest module are using voting api module. This module is great...
the Difference....
Voting api only is there for variable data points (voted by users)....while the node points are there to provide credit-like functionailty to the node...what is that node worth for.... a static credit/point for the node....
Five star voting is just there to provide points from the votes of you and other users... While nodepoints is hard-coded by the admin to provide credit/points to someone who visits or get a functionality from that node... so...hard-coded value of a node....independent from votes....
good luck..
.. keep us posted...
Thanks in advance Guys!
Yea its still under evaluation and by the way i changed it to NODEWORTH MODULE..... so we can distiguish it from the voting API and userpoints...
yes, names of modules here
yes, names of modules here in drupal can really be confusing, making names of modules correspond to what they actually do is a good step.
collectivetech.org
Technology for organizations. Open Source. Consultancy. Training.
collectivetech.org
Technology for organizations. Open Source. Consultancy. Training.
subscribing... :)
subscribing... :)
Suggesting for name
Maybe, you can named it as "NODEVALUE". I hope nodevalue does not exisit in Drupal.org. :)
Nice!
subscribing
did anybody get anywhere with this?
I want a similar module, I'm willing to write it, or help to write it.
Many of the above can be
Many of the above can be accomplished via Rules. You can create a field using cck for these node's and in rules that would allow a site admin do set the balue and then have rules check for the event desired and apply those changes to the acting user. At least it would be a good interim solution.
It's a good idea, but it's
It's a good idea, but it's going to lack a few of the features I want.
Ideally I'd want some of the more advanced features of userpoints, but for nodes. Points expiry & points evaporate would be important. Ability to see where points came from would be a bonus. Adding userpoints to the author of the node when the node is awarded nodepoints. Basically I want something exactly like userpoints, but for nodes rather than users.
I'm torn between adding a feature to userpoints so that it'll cope with nodes & creating a new module.
I can see both Points Expiry
I can see both Points Expiry and evaporate working using rules as well. the thing is you would need to create a rule that is robust enough to handle those sort of things. It is something i could write up and test and make available, but wont be able to do it for a while do to trying to find some funding at the moment.
It's for a site with over
It's for a site with over 25,000 existing nodes, I'd want those to be scored too.
Ideally a different amount of points need to be added based on the userpoints (or proportion of site max userpoints) of the user performing the action. So nodes authored by users with high userpoints would start with a higher score, comments & votes from users with higher userpoints would add more nodepoints, etc. nodepoints would expire and/or evaporate over time. I think I want quite a lot more than could be done with rules.
I've got a lot of plans for the module, but I've not started work on it yet.
I've done some searching, a few people have asked for a similar feature over the years, but I can't find any solutions. The original poster seems to have got the closest to what I want.