Thanks Jacopo. I understood that, and it makes perfect sense.
Some background info about me might help explain my confusion...
I worked for 10 years as a scheduler for contract security officers. Each
officer was assigned a work schedule. When they were not working their work
schedule, they were considered to be "available." I even produced a report for
the supervisors that showed when officers were available and how many hours
they had worked already. That was a valuable tool that could be used should
someone report in sick, or quit their job. An available (not working their work
schedule) officer could be called in to fill the vacant shift.
Like I said to David, it's just a matter of me changing my perspective of the
meaning of available.
-Adrian
--- On Thu, 9/18/08, Jacopo Cappellato <[EMAIL PROTECTED]> wrote:
> From: Jacopo Cappellato <[EMAIL PROTECTED]>
> Subject: Re: Discussion: Recurring Events
> To: dev@ofbiz.apache.org
> Date: Thursday, September 18, 2008, 2:08 AM
> Hi Adrian,
>
> >>
> >> I understand the approach you're describing -
> someone is available
> >> for work so their work schedule is flagged as
> available. The
> >> perspective I'm accustomed to is an employee
> is available for work
> >> when they are not already working. They are
> available for work when
> >> they are "off."
> >
>
> If an employee has a contract to work 8 hours a day from
> 9am to 6pm
> (with 1 hour of break from 12 to 1pm) then you cannot
> (well... at
> least you shouldn't) assign a task to him outside this
> time frame; he/
> she is *not* available for work 24 hours per day; that is
> why we need
> to set the boundaries of availability and then schedule
> tasks/
> assignment inside this frame.
>
> Jacopo
