Re: [MRBS-general] mrbs date/time passed

[Dave C. <ca...@sf...>]

I followed these instructions (with guidance from others including
Daniel Faulkner) to restrict booking too far in advance as well as the
current day and in the past).

 http://www.edugeek.net/forums/scripts/347-mrbs-stop-booking-x-days-advance-code-mod.html

It seems these are generally useful (as long as the implementation is
flexible), and would be a useful addition to the common code.
Cheers- Dave

> Hi Felix,
>
> it depends.
>
> For example, you may use MRBS to allocate tennis courts. In that case if
> someone came late, had no booking and just started playing on a free
> court, he should very well be able to enter that booking in arrears -
> and possible be invoiced for the court time later on. You would not
> allow booking deletions in arrears in that case - perhaps - or find some
> other limitations, but those are very much case dependant.
>
> In several of my MRBS installations we have proprietary rules - booking
> at least 1h in advance, deletion of bookings at least 4 days in advance
> or 1h in advance with penalty payment etc...
>
> So if it makes sense for you, fine - it is not too hard to restrict
> bookings to (start_time>=time()). It may not be generally reasonable
> though.
>
> Best regards
>
> Anselm
>
-- 
http://www.sfu.ca/biology/qk  http://www.sfu.ca/biology/staff/carmean/