Per-meal timing adjustments

[smoyte]

• Allow shift times, prep time, and total time to be adjusted per meal
• Use the updated times in reservations and notifications
• New model for MealLocations
  • Comprised of two resources: prep area & optional serving area
• Meal form location should change to simple dropdown with available MealLocations
• Migration to create MealLocations and then to convert existing meals to new MealLocations
• Prep area gets reserved from start of head cook shift to end of clean shift
• Serving area (if included) gets reserved from meal_time - serving_prep_time to clean shift time + clean time

Originally created by Tom Smyth at 2016-09-07 13:03, migrated from redmine-#5067

[smoyte]

• Description updated (diff)

By Tom Smyth at 2016-09-07 17:04

[smoyte]

• Description updated (diff)
  • Priority changed from 3 to 2
  • Estimate set to 8.00 h

By Tom Smyth at 2016-09-08 06:02

[smoyte]

• Category set to Public Release

By Tom Smyth at 2017-01-26 06:30

[smoyte]

• Subject changed from Meal prep and cleanup timing to Per-meal timing adjustments
  • Description updated (diff)
  • Category deleted ( ~~ Public Release~~ )
  • Priority changed from 2 to 4

By Tom Smyth at 2017-04-01 05:34

[willn]

It would be pretty excellent to display the current prep start time and when the reservation ends, to aid in resolving scheduling conflicts. Something like this mockup design. Of course this implies dynamically updating these times when the date/time selector is updated.

[smoyte]

@willn the prep time and reservation end times can, or may one day be able to, vary on a per-location basis. We just got a request about this the other day in fact—someone wanted to have the kitchen booked for longer than the dining room. How would we handle that?

[willn]

The spirit of what I'm proposing is visibility - to make it easy for the user to understand what is about to happen.

I've had numerous occasions where I was trying to create a meal, but it prevented me from doing so complaining that there was a conflicting reservation. I wasn't sure what the start and end time of the reservations would be. I could look at existing reservations on the calendar and guess... but it was hard to diagnose / debug / work-around. I usually modify existing reservations by chopping away the conflicting time, but each time I do so, I'm guessing as to how much I need to trim. I then try to create the meal again, and trim, and try, until it works out. If / when the times were to vary by location, then this cycle would be even more of a guessing game.

I could see a few different approaches that could be taken here:

1. simple: list the beginning of the first start time, and the end of the end times
2. precise: list all of the durations (start & end) of each of the rooms being reserved

If that feature request of supporting per-location reservation times is built, I could see the displayed reservation times dynamically changing based on the selected criteria.