Work session with Bryan going over projects. We talked about date-picker stuff and then moved onto scheduling. I was pitching a small proposal to add in a temp roster for the horizontal time view. This would be a JSON formatted setting that would allow you to pre-load in certain people to your horizontal time view. It's not real availability, but it was a step in the right direction. I did a bunch of drawing and brainstorming with Byran. Most of it was on the fly. He recorded a few notes.

We then switched and got into deeper availability and the layered calendar options that we are planning on building. This flow would allow us to prep or overlay a schedule or virtual availability schedule over the main calendar (elements of time). We went over ideas for flow, logic, and what it might look like. We determined that there were 3 main steps. For a single assignment, we would need who it was that was being assigned? The who could also be the what. For example: are we setting the availability for a person, place, or thing? That's step one. Step two would deal with a date or a date/time range. These first two steps would always be required. The third step would ask if we need to reoccur or duplicate those new availability settings. We would need to select that option, only if needed. If used, we would copy or duplicate the existing settings in bulk.

We got into tons of details and ideas. Lots of drawing and brainstorming. Bryan and I were even playing in Microsoft Excel and doing some fake table layout and data input stuff for the new layer tables. We would like to think of the new overlay functionality for the calendar as layers or availability layers. This will end up being part of our "any" scheduler. Behind the scenes, we will have the real elements of time (that already exists). The front or overlay layers will be for things like employee scheduling, non availability, holidays, web availability (options for online booking), etc. Fun stuff.