Re: [MRBS-general] Back to Back Bookings
Brought to you by:
jberanek
Menu
▾
▴
Re: [MRBS-general] Back to Back Bookings
|
From: Khushalani, J. <jnk...@un...> - 2007-06-25 16:58:50
|
Hello Phil, Thank you very much for replying.... But I need some help.... Do we step back by an hour in the sql query or somewhere else? I do desire 30 mins gap between the same create_by id.... but that is = for a start... How do I compare the create_by of previous and current booking.... I'm not sure how to go about it... Can you help me with a snippet of code or something? =20 Please guide... =20 =20 Thank You, Julie Khushalani Graduate Student - Computer Science Enrollment Services - Cato Hall University of North Carolina at Charlotte Email: jnk...@un... <mailto:jnk...@un...>=20 ________________________________ From: Khushalani, Julie Sent: Thu 6/21/2007 2:00 PM To: Phil Greer; MRBS Subject: RE: [MRBS-general] Back to Back Bookings Hey Phil,=20 Well it did make some sense to me... but can you elaborate a li'l = more..... I want the gap to be 30 mins. Also I don't mind if its back to back by different users... but I do not want the same person to book consecutively.... Do we have to add something in this function where it checks for = conflicting bookings? =20 =20 Thank You, Julie Khushalani Graduate Student - Computer Science Enrollment Services - Cato Hall University of North Carolina at Charlotte Email: jnk...@un... <mailto:jnk...@un...>=20 ________________________________ From: Phil Greer [mailto:pg...@pi...] Sent: Thu 6/21/2007 1:53 PM To: General purpose list (support/developers/users) Cc: Khushalani, Julie Subject: Re: [MRBS-general] Back to Back Bookings how much time do you want between bookings? 1 hour or 1/2 hour?=20 either way you would probably put the check in mrbsCheckFree() in = mrbs_sql.inc. it would be very similar to the ckeck it does already, but you would = want to bump $starttime back an hour and specifically get the create_by = from the entry (if an entry exists). then compare the current create_by = with the one from the prior create_by and report an error. (see = getWritable() in mrbs_auth.inc) this requires editing passing the current create_by to the mrbsCheckFree = function in edit_entry_handler.php and making sure mrbsCheckfree accepts = the new create_by in mrbe_sql.inc.=20 *NOTE* this check would be in addition to the one that is there already. Mind you this would only stop one account from booking back to back, but = if he/she got someone he/she was working with to trade bookings, well = that is something else..... -Phil Greer On Jun 21, 2007, at 1:15 PM, Khushalani, Julie wrote: Hello, I wanted to know if anybody can help me solve this issue... We have recently implemented MRBS in our Library. I wanted to know if there is a way to stop back to back bookings.... According to our policy users can book a room for max 3 hours.... But I want to avoid the possibility of students booking the whole day = in 3 hr slots... Is there a way to stop back to back bookings????????????????/ Please help urgently.... =20 =09 Thank You, Julie Khushalani Graduate Student - Computer Science Enrollment Services - Cato Hall University of North Carolina at Charlotte Email: jnk...@un... <mailto:jnk...@un...>=20 = -------------------------------------------------------------------------= This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. = http://sourceforge.net/powerbar/db2/_____________________________________= __________ mrbs-general mailing list mrb...@li... https://lists.sourceforge.net/lists/listinfo/mrbs-general |