posted 20 years ago
Hello all,
I'm doing the design for my project, and I think I've got a good enough understanding of most of the issues (many thanks for all the info in this saloon) but there is one thing that eludes me: do the CSRs have to be able to unbook contractors?
The specification says enough about searching for and booking contractors but nothing about how a booking terminates. From the spec all I get is that the CSR find a contractor for the client and book it. When and how does that booking end and the contractor become available for another booking? Or is this not needed for this project?
My first reading was that the CSR does the booking and then I have to assume when the job is done either the client or the contractor calls in to say its all done so that the contractor's record can be made available for another client. This means a Service layer would have to have an unbook method, something I've not seen mentioned by anyone. If I stick strictly to the spec this is perhaps the only interpretation other than don't worry about ending bookings.
Another possibility is keeping track of the start date and length of the booking and then having the system update itself, but this would require an auxiliary data file of some sort and seems completely out of the scope of the project to me.
After doing a good bit of reading here, I couldn't find any references to this problem and so am wondering how others have handled this. Does anyone have any thoughts on this? This is one final piece I need to figure out so I can get down to coding.
Thanks for any help and regards,
Jay