VotingAPI

flk: 15:58 < fago> another thing, what have you planned for the thesholds? when does your module apply the votes? <<< you could make use of the voting api for this
flk: it has 3 different strategies of applying votes

agaric: flk: I'll look at voting_api in this context
flk: :)

fago: flk: yeah, I also thought about this. perhaps it would be useful for storing votes...

fago: have a look at the votingapi, it might suit very well for you
fago: http://drupal.org/project/votingapi
fago: so you could use it to store votes - or don't but just apply the vote.

agaric: back to voting_api... I need a place for term ID == content_id ...
fago: start with the normal variant, without ajax. As it has to work nevertheless. You could add the AJAX later..
agaric: bingo

flk: take it a step at a time
fago: What do you mean with content id? node id?

agaric: in voting_api's tables, it has a content_id which can be anything
agaric: (including fish, according to the project page!)
fago: mmmh, fish :)
agaric: :-D
fago: perhaps, you create your own table for these ids, that specifiy, which id is what.
agaric: .. so I'm trying to see how my needs match up. I briefly thought about moving terms between vocabularies and ran away in fright for the moment
fago: so it would containt the associated terms and the operation for what it has been voted

agaric: fago: ahh, I get it, so I can make a table that says term ID should be moved/merged/whatever to another term ID

agaric: and just use voting_api to count the votes related to that table?
fago: agaric: exactly
fago: yep

agaric: Brilliant! I'm sure if I could have found the API definition before the table structure, all would have been clear...

agaric: http://cvs.drupal.org/viewcvs/drupal/contributions/modules/votingapi/API.txt?rev=1.4&view=markup
agaric: any other modules that will do most of my work for me ;-)