By felixsmile on
Hi!
In my university, we sometimes distribute some tasks or little jobs, and I would like to add this function to our Drupal site.
I thought about using the sign up module, but it has no option to restrict the number of candidates (usually 1, first come, first serve). Is there any possibility?
Thanks in advance,
Felix.
Comments
there is an RSVP module as
there is an RSVP module as well that may be of benefit.
sounds more like issue tracking, to me
seems like instead of signup + nodes, you really want some kind if issue tracking:
http://drupal.org/project/project_issue
http://drupal.org/project/casetracker
enjoy,
-derek
___________________
3281d Consulting
Thanks
Thank you for your replies. The problem with RSVP is that you need events for it to work, and, furthermore, I don't want to invite many people.
I had thought about using the subscription module, so that every interested user signs up for that category, when something is available, he goes on the site and, if interested, he takes the job. Then, however, others should not be enabled to take it anymore, do you see the problem?
Casetracker seems to be a really good project, but I'm not sure how I could use it in my case.
If you have any ideas, I would be grateful, thank you already,
Felix.
No one?
Any help would be highly appreciated.
i'm telling you -- you want issues or cases
it sounds like you're trying to track work, and ensure that only 1 person is assigned to work on any given task as a time. right? that's *exactly* the functionality provided by both of the modules i linked to.
if you don't think that's what you need, then you either a) don't understand what those modules actually do or b) aren't being clear about what you're trying to accomplish...
either way, just asking "anyone? please help me" isn't much help. do a little more research, use your imagination (lots of problem solving involves changing how you think about a problem to realize there are equivalent solutions that just don't happen to be what you were expecting), or explain why the help you've already been given isn't going to work for you. just saying "but I'm not sure how I could use it in my case" doesn't clarify why you think it won't work. for all i know, you just don't understand what it does. :(
sorry, i don't mean to be hostile, it's just frustrating when i go out of my way to provide help and you basically reply "that's no help at all... can't *anyone* help me for *real*?"... you're saying "greatly appreciated" but not actually showing it. ;)
*shrug*
good luck,
-derek
___________________
3281d Consulting
Sorry
Hey Derek,
Sorry, I'm sorry, I didn't mean to be rude or to offend you.
You are right, these two came very close to what I need, and I had not been clear in what I wanted. In some previous posts, I had been too explicit, so this time I tried to be a bit more concise, I guess, it was too much. I'll try to be now.
When you gave me the links, I feared that the projects had to be assigned (by an administrator), and what I wanted was a "first come, first serve" system, with no administrator needed to interfere.
Now, I installed casetracker, and set up a little project (which, if I get the module right, will be the "container" for all my cases, as I only have one type of case). It really looks nearly like what I need (of course after some little CCK adjustments), however, there is still the first problem.
When a user arrives, he should be allowed, if no one is yet assigned to the case, to take it, with just one click if possible, the people using the site will not be IT professionals. This, if I'm not wrong, presupposes some rights to modify the case. But, what if someone comes after that guy and just assigns the already assigned task to himself (as he would have the adequate rights, too)? I guess closing the issue doesn't resolve the problem either. Deleting the issue after having assigned it to a user doesn't seem really good either, because sometimes, a user might not be able to take up the job and might want to put it back again into the "public domain".
I hope I have been clearer this time, but I really think you got my problem.
Although my questions do look a bit helpless, I'm not a complete noob and I can see that you have put an effort in replying seriously, reading my question, and if I have not given you adequate credit previously, I'm sorry and would like to make up for it now. Thank you.
Have a nice day,
Felix.
"locking" assignment -- sounds like a small feature request
i bet if you explained your needs/use-case clearly in an issue submitted to the casetracker issue queue, you could request a feature about "locking" a case's assignment like this (once assigned, only an admin can re-assign, or the current assignee can unassign themselves). i can certainly see the usefulness of such a feature in general. so, if the module does 98% of what you need, you can just ask about the other 2% and see what happens.
better yet, take a stab at implementing the feature yourself (if possible) or offer to pay someone to work on it. i know Morbus maintains casetracker, and he's very good, so i doubt it'd be that hard for him if you were willing to pay. he might even like the idea enough to just do it on his own, you never know. ;)
good luck,
-derek
p.s. no worries about the post, and thanks for the apologies.
___________________
3281d Consulting
Thank you, I posted it
Thank you again, I posted the request here http://drupal.org/node/108711 and if Morbus has no time to look at it, I'll do the job with comments: the first to comment will be the one to get the job.
Have a nice day, good luck to you, too,
Felix.