Re: [MRBS-general] next trial

[Campbell M. <cam...@gm...>]

Well, I'm planning to implement the following policies (a) max n per day and
(b) max n per week.   I suppose I could easily add (c) max n in the future.
These will be global, ie across all areas.   The trouble with these policies
is that every organisation has slightly different requirements.   For
example some will just have certain areas or rooms where the policy applies,
some will define the day as starting at say 1000, some will only want to
apply restrictions during peak times, etc. etc.    But the three basic
policies above would be a useful starting point and enable people to modify
them.

 

I'm not quite sure though what you mean by saying you just want it to apply
to the user in the "namebooker" field though?   Have you made some
modifications to the system?   Normally the booking is for the logged in
user.  There is an interesting question though, which is what should happen
when an admin modifies an ordinary user's booking?    Should the standard
restrictions for the ordinary user apply?  Or should there be no
restrictions, because an admin is logged in?   I think the latter makes more
sense, but I'd welcome input.

 

Campbell

 

 

 

From: Schreibmaier Joachim [mailto:Joa...@hi...] 
Sent: 12 April 2012 19:02
To: mrb...@li...
Subject: [MRBS-general] next trial

 

Hello,

 

unfortunatley I have a few problems with the booking component. I want to
implement the mrbs in a tennis court booking system. Therefore there are a
few restrictions necessary. One major point is that when it's a normal
registered user (not a admin) it should only be possible to make one booking
in the future. This restriction shell not take effect on the login user name
but on the player name which is filled in in the field "namebooker". Is this
possible?

 

It would be great to get any response because we wan't to go online in the
next 2 weeks.

 

Best Regards,

 

Joachim