Greetings All!
I am working on an application to govern the schedule of a team of individuals who ‘float’ within an organization to different positions. For example, there are 20 bean counters, if one bean counter needs time off, they need to schedule a ‘float’ bean counter to replace them. To do this, said bean counter should be able to check to see if a ‘float’ bean counter is available via some calendar mechanism, if available, schedule them as a replacement bean counter. To me this sounds like the resource reservation database replacing a ‘resource’ with a position. I realize there are inherent problems with calling a person a resource, etc. But this comes close to a canned solution. Has anyone done this before? Surely… ( and stop calling me shirly.)
Thank you for your time.
ys