Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I cannot seem to deduct from the current description just what this module provides...
- a way to vote on users themselves?
- a rating of which users are the most active voters?
I am confused (havent tested it, need to understand the main purpose before that interest is triggered...)
Please add an example of its use to the current description on the module's main page.
Comments
Comment #1
colanOkay, I cleaned up the description somewhat. Does it make more sense now?
Thanks for the feedback!
Comment #2
Leeteq commentedThanks, a bit clearer now, but I still find myself wondering just which scenario(s?) it is meant for.
Below are my first associations examplified:
Ref. your description:
"uservote_set_user_rating($user, $vote)
Rate a user."
According to what, exactly?
- is the current version limited to one "rating aspect" per user?
Example aspects (what the rating may be for):
- That you like this user?
- For what he/she did HERE on this site or have done according to a specific project mentioned in node number nnn?
- That you like that users' posts (content) in general, or his efforts (regardless of whether or not everything posted is accurate, at least that user shows an effort, and that is worth something by itself..?)
- etc.
These are examples on the associations I get once I start trying to figure out what I would like such a module to handle.
Then to my point:
The above mentioned choices is a matter of implementation (API), yes, ok, but it leads to a more important question:
- if this module is completely neutral on exactly which aspect the rating should reflect, then I will immediately want to use it for several such purposes. How does it store the data? This calls immediately for a way of storing several values per user... - so that the admin can use the API provide several such ratings per user, storing one value for each?
If this version of the module is not supporting that yet, then I have to return to the initial question: is the current version limited to one "rating aspect" per user?
I think I would very quickly need to be able to store several ratings per user, each tied to its own "aspect" that could perhaps be stored as text in the database table, configurable in the GUI.
Then I could use the admin page to add new aspects that had their own keyword which I could use the API to call. Ratings for each user would then be stored in pairs (rating, aspect), and with a separate table storing an indefinete number of "aspects". (hmm, I could not think of a better word than aspect for this...)
Comment #3
johnchalekson commentedhow does one implement this module into a user profile?
i have installed it but i see no where to adjust the settings.
do i place something in my user_profile.tpl ?
Comment #4
colanI just finished working on the documentation. There's now a link from the project page. Hopefully, that'll answer many questions. Please let me know if more clarification is required.
Yes, currently only one axis (or "rating aspect") is supported. This will soon change as I plan on adding support for multiple axes. The storing of the data is handled by the Voting API. It already supports multiple axes, so this shouldn't be too much work.
Please create issues for feature requests. For now, I'm marking this issue as fixed. Please set it back to active if necessary.
DanielTheViking: Your plan sounds like it would definitely add some utility to the module. I probably won't get around to this stuff, but fell free to contribute at some point. I've still got some work to do on this thing though.
Comment #5
(not verified) commented