rebooking

[Petr Hejl]

Hi ranchers,
I would like to ask you how you are dealing with booking.
When the record is already booked do you allow rebooking or not?
Do you have special method for "unbook"?

Thanks P.

[Mihai Radulescu]

Hi Petr,

I have both:
1.a release - just release a booked record, afer this the record has no owner(with the user confirmation ? or not I still think on)
2.a book over - with the user confirmation.

Regards M.

[Daniel Massie]

My view was that it was outwith the scope of the project. This functionality was not specified in my assignment thus isn't required.

[Petr Hejl]

May be it is out of scope to unbook. But you have to deal at least with situation when booking the booked record. Is it allowed or not?

[Mihai Radulescu]

Hi,

I must agree that the "rebook"(nike or adidas) are not explicit specified in my docs, but I think this was with purpose.

I include this "adds" in my project because during test I notice that this kind of functionality can be useful and increase the UI usability. You can image a lot of useful situation for rebook and release record.

Regards M
[ August 09, 2006: Message edited by: Mihai Radulescu ]

[Daniel Massie]

Originally posted by Petr Hejl:
May be it is out of scope to unbook. But you have to deal at least with situation when booking the booked record. Is it allowed or not?

No, I stated as an assumption that once a booking was made, it obviously couldn't be double booked. I handle this in exactly the same manner as I handle the 48h rule in URLyBird.

[Mihai Radulescu]

Hi Daniel,

No, I stated as an assumption that once a booking was made, it obviously couldn't be double booked.

The CRS can make mistakes and the user also, is your task (like designer) to assure that the errors are signaled and to provide a way to correct it.

Regards M.

[Daniel Massie]

Originally posted by Mihai Radulescu:
The CRS can make mistakes and the user also, is your task (like designer) to assure that the errors are signaled and to provide a way to correct it.

I said that I handled this in the same way as the 48h rule, which means that there is no way for it to be double booked. So there is no error to be signalled, and no need to correct anything.