Hi, I'm having a big issue about how to configure a Drupal site, I'm getting crazy..
My goal is something like this: A person works in 2-3 cities, he needs to be booked by his clients by an authomatic system.
For example, he works: City A: Monday to Wednesday, 8am to 10pm City B: Friday, 9am to 11pm City C: Sunday to Wednesday , 7am to 12pm
(every time it can change, not a regular schedule)
every appointment can last for 1/2/3/4/5/.. hours (not just 1.30 or 1.42).
So he has to be able to provide his availability (by city and time) Users have to be able to book/signup for a 1/2/3/4/5/.. hours, one user can't book at the same time of another one.
I looked at some modules like Booking Time Slots http://drupal.org/project/booking_timeslots but it looks like not working, as well as Public Bookings http://drupal.org/project/publicbookings
I tried signup module but still don't know how let it work as I need to..
do you have any idea?
Thanks
That's very interesting. I think you could do it yourself without having to rely on prebuilt modules for the effect.
I would do something like: - create a new content type centered on the hours of the days, each node would be an hour. Other fields would be date, city, a single on/off checkbox for the availability, another checkbox for the booking, maybe a computed field to archive the user that will book that hour... Your client would have to create one by one the nodes corresponding to the hours and the days when he's available and assign to each a city. You might want to explore modules like Node Clone to ease this task. - create a view that presents this nodes by week, for instance using a grid where columns would be days and rows the hours. You could create also a view prioritized by city... - create an action to unpublish the hour that has been selected by the user, effectively booking it.
Other approaches are certainly possible. I am curious to see what Drupal gurus answer to that.
HTH.
Roberto
Francesco Baldini wrote:
Hi, I'm having a big issue about how to configure a Drupal site, I'm getting crazy..
My goal is something like this: A person works in 2-3 cities, he needs to be booked by his clients by an authomatic system.
For example, he works: City A: Monday to Wednesday, 8am to 10pm City B: Friday, 9am to 11pm City C: Sunday to Wednesday , 7am to 12pm
(every time it can change, not a regular schedule)
every appointment can last for 1/2/3/4/5/.. hours (not just 1.30 or 1.42).
So he has to be able to provide his availability (by city and time) Users have to be able to book/signup for a 1/2/3/4/5/.. hours, one user can't book at the same time of another one.
I looked at some modules like Booking Time Slots http://drupal.org/project/booking_timeslots but it looks like not working, as well as Public Bookings http://drupal.org/project/publicbookings
I tried signup module but still don't know how let it work as I need to..
do you have any idea?
Thanks
-- [ Drupal support list | http://lists.drupal.org/ ]
On Ven, 10 Aprile 2009 2:48 am, Roberto Gorjão wrote:
I would do something like:
- create a new content type centered on the hours of the days, each node
would be an hour. Other fields would be date, city, a single on/off checkbox for the availability, another checkbox for the booking, maybe a computed field to archive the user that will book that hour... Your client would have to create one by one the nodes corresponding to the hours and the days when he's available and assign to each a city. You might want to explore modules like Node Clone to ease this task.
- create a view that presents this nodes by week, for instance using a
grid where columns would be days and rows the hours. You could create also a view prioritized by city...
- create an action to unpublish the hour that has been selected by the
user, effectively booking it.
I already thought about this approach but it should be too long: Mon to Fri 8am to 10pm, he should create 14 nodes for 5 days, 70 nodes.. and sometimes he stays 2-3 weeks in the same city
Other approaches are certainly possible. I am curious to see what Drupal gurus answer to that.
I hope someone do it :)
thanks anyway..
Francesco Baldini wrote:
On Ven, 10 Aprile 2009 2:48 am, Roberto Gorjão wrote:
I would do something like:
- create a new content type centered on the hours of the days, each node
would be an hour. Other fields would be date, city, a single on/off checkbox for the availability, another checkbox for the booking, maybe a computed field to archive the user that will book that hour... Your client would have to create one by one the nodes corresponding to the hours and the days when he's available and assign to each a city. You might want to explore modules like Node Clone to ease this task.
- create a view that presents this nodes by week, for instance using a
grid where columns would be days and rows the hours. You could create also a view prioritized by city...
- create an action to unpublish the hour that has been selected by the
user, effectively booking it.
I already thought about this approach but it should be too long: Mon to Fri 8am to 10pm, he should create 14 nodes for 5 days, 70 nodes.. and sometimes he stays 2-3 weeks in the same city
You could try to automate the nodes creation, either by a php script activated by cron... or by an exterior piece of software like... I don't know... iMacro on Firefox? This module is still not ready for production -- http://drupal.org/project/date_repeat_nodegen -- but maybe you can work out something from it.
Having the hour nodes created, it would be fairly easy to present them in lists and provide some JavaScript functions in order to permit the attribution of a city value to a group of nodes at the same time. As your client's presence in the different cities is not a predictable pattern, I see no way of doing it other than manually. You can only make it easier. At least, that's the way I see it.
Roberto
On Ven, 10 Aprile 2009 2:48 am, Roberto Gorjão wrote:
That's very interesting. I think you could do it yourself without having to rely on prebuilt modules for the effect.
Just to let you know, I solved by using Booking Time Slots (newer version) module http://drupal.org/project/booking_timeslots
Quoting Francesco Baldini fb@codicelibero.net:
Hi, I'm having a big issue about how to configure a Drupal site, I'm getting crazy..
My goal is something like this: A person works in 2-3 cities, he needs to be booked by his clients by an authomatic system.
For example, he works: City A: Monday to Wednesday, 8am to 10pm City B: Friday, 9am to 11pm City C: Sunday to Wednesday , 7am to 12pm
(every time it can change, not a regular schedule)
every appointment can last for 1/2/3/4/5/.. hours (not just 1.30 or 1.42).
So he has to be able to provide his availability (by city and time) Users have to be able to book/signup for a 1/2/3/4/5/.. hours, one user can't book at the same time of another one.
I looked at some modules like Booking Time Slots http://drupal.org/project/booking_timeslots but it looks like not working, as well as Public Bookings http://drupal.org/project/publicbookings
I tried signup module but still don't know how let it work as I need to..
do you have any idea?
I found: http://drupal.org/project/mrbs http://drupal.org/project/openresort http://drupal.org/project/library http://drupal.org/project/airplane_reservation
I don't know if they will help.
There is also http://drupal.org/project/bookings which is touted to be an API and a discussion group for it can be found at http://groups.drupal.org/booking-systems.
Good luck, -- Earnie -- http://r-feed.com/ -- http://for-my-kids.com/ -- http://www.4offer.biz/ -- http://give-me-an-offer.com/
On Ven, 10 Aprile 2009 2:40 pm, Earnie Boyd wrote:
I found: http://drupal.org/project/mrbs http://drupal.org/project/openresort http://drupal.org/project/library http://drupal.org/project/airplane_reservation
I don't know if they will help.
I already found these modules but nothing is useful at my work..
There is also http://drupal.org/project/bookings which is touted to be an API and a discussion group for it can be found at http://groups.drupal.org/booking-systems.
in heavy development..
thanks anyways