Meeting with Cory to go over projects. Cory was asking all kinds of questions from her little list and from email chains that have been going back and forth between herself and our clients. We then moved on to some new projects and getting numbers, estimates, and quotes. One of them, a client wants a bunch of data out of the system. As we talked about it, they are wanting huge one-to-many relationships exported into a CSV file (comma separated values). We spent some time and talked about relationships and where CSV files work great and where JSON (JavaScript Object Notation) files work much better, especially if you have multiple deeper or more complex relationships.

We spent some time talking about the client facing scheduling and where we are heading. We have determined that we will end up with three different types (for now). The three types will be listed below. The main variables that we are watching for and tracking are: What is the date or date/time combo (when)? What product are they wanting (in case there are multiple options - what)? And how many people are participating (quantity, seats, participants)? Those are are three main variables we are watching - when, what, how many.

Plans for different types of online bookings:

1. Daily/weekly reoccurring with multiple participants. This deals with known and pre-set dates and times. We already have the rough schedule and just need to see who will be participating in each preset event. This is a normal one-to-many relationship with time being the one and the participants being the many. For example: like a shuttle service or ongoing event - pretend that we are going to offer a shuttle from point A to point B twice a day. We can hold 35 people per trip. This is a perfect example of the daily/weekly reoccurring with multiple participants. Think of selling seats or counts per event.

2. The next one is very similar but instead of being a daily/weekly reoccurring event, it is more of a special event or unique event. This will still allow for the same one-to-many relationships, but the dates are not as constant. That factor, the frequency of the date/times makes each event be unique. For example: Say you had one trip to a certain destination with multiple people going on the special trip or something like that. Because we have already plowed the path for the reoccurring one-to-many (listed above), this one should be pretty easy. Think of booking seats or counts for a special event (non-reoccurring or reoccurring but with special date/times).

3. The third option for scheduling time will be the one-to-one relationship. This is more of an open calendar and setting up what time slots are available. For example: Say a person wanting to schedule an appointment or get a haircut. The company or users would setup a basic template of allowed time slots and then allow for those time slots to be filled. The one-to-one relationship comes with one element of time holding info for a single client or customer. Basically, the quantity is assumed at one. This type of online scheduling could be used for campgrounds, doctor's offices, hair or nail salons, consulting services, etc.

After we discussed these options, in some detail, we talked about settings, next steps, and plans. Good meeting.