... handling organic groups this way shall be made optional, of course.

Motivation:
For my client, I have to cater for the following situation: early while planning a lecturing schedule, it is only known which institution is responsible for the lectures (and how many lecturers each institution has), but not exactly which lecturer will do which lecture.

So, allow for parallel planning of "resource usage" as often as there are members in the group, but not more.

Comments

raphaelhuefner’s picture

raphaelhuefner commented

I would like to make this "resource pool" thing into something which is attached via a hook like proposed in #750598: hook(s) for field- and node-handlers in order to not bloat the resource_conflict module too much.

deviantintegral’s picture

deviantintegral commented

Again, this seems like a pretty useful addition, but best handled as a separate module.

ohthehugemanatee’s picture

ohthehugemanatee commented
Status: Active » Closed (won't fix)