Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
|||||||||
|
|||||||||
|
Notes:
|
We had a meeting with Chuck and he was showing some new progress with the campground stuff. We are code naming it camp-adilas just for fun. That was Marisa's idea. We had Danny Shuford, Marisa Shaw, Chuck, Steve, Alan, and myself on the meeting. Steve and I were lightly distracted, due to a server issue. We had two servers down and we were part in the meeting and part trying to make sure that things were being taken care of. Interesting. Anyways, here are some notes from our meeting. - Visual services and access to add-on services when selling and booking a campground site - Color coded helpers to help with states, statuses, and color coding helpers - Be able to show available, occupied, and services available to each site - Marisa was talking about a synced reservation and a non-synced reservation. This deals with who is booking the site. Is it grandma and grandpa who put their card down to reserve 4 different sites for their family (synced or all together) or is it just a single family booking a site (non-synced or self pay). She was saying that we need to be able to do both and allow those groups to expand, contract, and break apart if needed. All of this deals with billing and reservations. - It is really important to be able to show just the open sites for a specific date range. - The sites themselves need different status levels. For example: pending, confirmed, checked in, checked out, reserved, etc. - They talked about a "do not move" lock on certain site. This deals with a state or status that keeps the person locked in for some reason. It could be VIP treatment, special needs, special group considerations, or some other circumstance. - We need to be able to add notes to any site and/or reservation. - Block a site through a date range. Also being able to block the same site with a possible extension date range (not for sure, but a maybe or possible extended stay). - Lots of needs for discounts and campaign tracking. This is already built in, but we wanted to note it anyways. - Waiting lists would be nice. Able to sort and move people around on the waiting list as needed. They even talked about different queue type options. - Lots of color coding and legends - Being able to move reservations from the waiting list to some other available site - Lots of talk about treating the waiting list like a queue of sort sort. The queue would be, by default, first come first server, but it would also have ways of tweaking it based off of needs, special circumstances, and/or add-on services (being able to manually move things around if needed). - Currently, the campgrounds are doing tons of little hand-written notes and post-it notes to keep track of things. That gets crazy as things get busier. - Danny was talking about using the priority fields on the elements of time to help sort certain reservations and/or waiting list persons. Just an idea. - My biggest take away from the meeting was Marisa's comment - "I can sell this!" - Chuck is making the system sellable due to the ideas of the intuitive graphical user interface and what the possibilities could be. That was my favorite comment. Good stuff. We need to make this thing sellable. - Sent an email to both Chuck and Russell to have them look into some of the stuff that we have been doing with Jonathan Wells, the designer from Rexburg, ID area. Here is the link: https://data0.adilas.biz/top_secret/developers_notebook_home.cfm?sort=ASC&q=meeting%20with%20jonathan |