Helping Steve with his VPN connections for accessing the servers. Lots of Bear 100 stuff. That race goes off tomorrow morning. here is link to the news and updates about the race. The actual public runner portal page is located here: https://data0.adilas.biz/bear100

Did some work for High Valley Bike Shuttles and adding some special code to browse right to a specific page with a sub tab (sub section) opened up. Normally, the sub sections have been harder to control. We added in some options to virtually control the pages and the sub tabs within the main pages. That was kinda fun.

Meeting with Bryan. I showed him some of the changes to the online scheduling stuff. He helped build the original functionality for reoccurring and special events. We then switched gears and did some planning on dealing with huge record sets and bigger reports and big data exports. Basically, we have the data in the database, but it takes too long to show the whole thing (all of the records) in the browser. Imagine asking for 20,000 records at once. The database servers that up like a snack. However, the browsers struggle because that is a big bite to chew and virtually it is like putting an elephant through a straw. It's painful.

We did lots of drawing, looking at code, samples, existing pages that do mini versions of this, etc. Good planning session. Bryan has already been playing with some code and doing some research. That is awesome. We will continue to keep playing until we feel like we have a good plan and a good mini version of what we are wanting before trying to tie it into live reports.

The discussion turned towards two major options. One is AJAX or asynchronous downloading of the data. We have to respond quickly and then show progress while pulling in the other (thousands) records. The other major option is to offload it, meaning the search and building the export, by using a queue of sorts. Basically, we push the search criteria to the queue, get a total record count, and then start building that behind the scenes. If the user wants to check, we can show progress of how many records have been added as compared with the total record count. We then notify the user when it is done. That way they don't have to wait, and they can be doing something else instead of just waiting and hoping that it will not timeout.

Bryan and I made a plan for doing some local testing on a report with 70,000 ish records and then moving it over to live once we've knocked it around a bit. We went over a few other details, but Bryan is going to start playing with some scratch files. Making progress.

Phone call with Eric going over what it would take to import customer loyalty points from an outside system or source. We went over some details and ideas. Eric is pretty busy, so I will have to build this out. He is going to send me over a file, and we'll go from there. Most likely, we will need to run this import over and over again for the same client. Reason - they are still using their existing system but as they switch, we need to keep the data up to date. We also anticipate that other clients will need the same capabilities.

Back working on some ecommerce changes and helping out High Valley Bike Shuttles with their page request and navigation options. Custom code for where they want to point people on their ecommerce site. They use a lot of our online schedling pieces, out in ecommerce land. 

Working on some JavaScript stuff to help with a link builder inside the mini scan cart settings. Didn't have much time today.

Verifying runners for the Bear 100. Going over the official start list and comparing it to what we had uploaded previously. Making some changes and then sent out emails to the race director and others.