Adilas Key Contributors:

Steve Berkenkotter - Main owner and business partner - original ideas, concepts, and training - sales, relationships, dreamer, visionary, custom code, coordinator, builder of the first industry specific skin, and the list goes on. Huge player in the adilas story and timeline. One of the original owners in Moring Star Automotive - where the system came from. There are three known Steve's in the system notes. Most of them are this Steve (99 out of 100 times). He won't admit it, but adilas was his brainchild.

David Berkenkotter - Steve's brother and business partner in Morning Star Automotive. David was a system user and helped us create the adilas quick search. He liked using that feature, the quick search, but it only existed on one page originally. He wanted us to put it on every page. That ended up being in the header. He was also one of the original partners in adilas. Power user in the system. Sadly, he passed away due to cancer.

Shari Olin - Commonly known as "Shari O.". She worked in the accounting department back in the Morning Star days. She has been somewhat of a mother hen to help all of us crazy chickens keep going. She helps with customer support, training, payroll, bill collection, and tons of backend office functions. Major power user. Just being silly, but she can have the mouth of a sailor but the heart of an angel. Part of the adilas admin team and a great friend.

Craig Leitner - Also part of the original Morning Star team. Craig was the automotive floorplan and bank guy. He is a power user in the system and does a lot of bank reconciliation and other tasks. He currently works with Steve and asks as the adilas controller (money flow guy).

Cory Warden - Originally an adilas rep and consultant. Cory become part of the team after being a rep for quite some time. She helps with customer care, client support, project management, and keeping the team on track. She also does all of the news and updates and other training material. Cory does tons of oversight type services for our clients. Power user and part of the admin team.

Sean Carlton - Sean was a manager at a Cannabis dispensary in Colorado that used adilas for years and years until they sold. Steve recruited Sean to help with sales, deployment, and training. Sean brings lots of usage experience. Often, he is one of the helpers if we need to send someone onsite to help with a deployment or training session. Power user.

Brandon Moore - I'm one of the guys that writes most of the developer's notebook entries. Originally, I was hired by Morning Star, the automotive dealership, to help with data entry, accounting, and website stuff. I ended up being one of the main adilas developers and architects. I build content, write code, help other developers and team members, and help with training. Helped start the project back in 2001 under the Morning Star name.

Chris Dunsey - One of the first adilas interns (developers). Helped with a number of projects. Ended up being somewhat of a consultant later on.

Shawn Curtis - Kinda a funny story. He was taking a developer's class at Bridgerland. He knew my brother Russell. He asked to join our developer class and became one of the first interns along with Chris Dunsey. Shawn ended up helping with payroll and other projects. Some of the photo galleries in the system came from Shawn's help. He also worked on the media/content (file upload) pieces. Later on, he did more payroll work and acted as a buddy to Brandon and did some consulting work. We worked together for years and years.

Russell Moore - Russell is my younger brother. Originally, he was added to the group because of his graphic skills. He ended up being a great backend developer and project manager. He has also acted as a trainer and mentor for Brandon along the way. Much of the current system came from projects and efforts that Russell was involved with. He has also been Brandon's AI tutor in recent years. Great help to the system. Huge contribution.

Chris Johnnie - He is an entrepreneur who teamed up with Russell to help create a company called "Adilas For Business" or "AFB". Eventually, both Russell and Chris sold their pieces back to adilas. They were honestly the first ones to really try to run as a white label of adilas. This was back in 2015 and 2016. Chris really helped to push the product to the next level along with Russell's help.

Danny Shuford - Longtime friend of Steve's. Danny helped with some website design, sales, and videos for adilas. He even got into creating custom PDF labels for clients. Light development work.

Marisa Shaw - She is Danny's daughter. Danny brought her to an adilas training event in Denver, CO. Marisa was the star student. She ended up helping with some graphics, flyers, marketing material, teaching, instruction, and planning. Power user. Very helpful.

Shannon Scoffield - Shannon is Brandon and Russell's sister. Her maiden name is Shannon Moore. Huge help and virtual assistant to Brandon. She has helped with training, project management, and content creation. Most of the major content sessions were or have been with Brandon and Shannon working together. When they, Brandon and Shannon, were traveling, Shannon was one of the primary adilas instructors. If she was teaching Brandon was taking notes. If Brandon was teaching, Shannon was taking notes. Power user.

Cheryl Moore - Cheryl is my mom. What an asset. She owns a small business and has owed a few different ones. When we were doing training sessions, she came to every one of them. She asked wonderful questions and was a great supporter. Sometime, I would use her as a test subject - can my mom do this? If yes, we are good. If not, we may need to keep tweaking it. Thanks mom!

Wayne Moore - Wayne is my dad. He was my hiking buddy and more than willing to talk about ideas and concepts on our walks and hikes. He helped out with video stuff and was a great coordinator for making other connections. He worked at Bridgerland (technical college) and helped us get setup with classrooms, computer labs, and other great connections. Huge cheerleader! There is another Wayne, Wayne Andersen, he is a backend developer, systems guy, and database guy.

Wayne Andersen - This Wayne lives in Portugal and helps with all of the backend security, server, and code testing. Major skills, writes code, helps push all of us to new technologies, partially retired but loves to play with tech stuff. If you search for Wayne and it deals with concepts and coordination stuff, that's my dad, Wayne Moore. If you search for Wayne and it sounds like a master backend guy, that's Wayne Andersen.

Alan Williams - One of the lead developer's at adilas.biz. Alan joined us in 2015 and quickly came up through the ranks. Trainer, CTO, team lead, master developer, prototyper, and system architect. Alan has helped with many projects and features over the years. He also helped Brandon with some of the prep work for the adilas lite (fracture) plans and project. Sometimes called "Dr. Alan" by the other developers. Example: This might be a project for Dr. Alan.

Bryan Dayton - Bryan has been one of the most versatile guys on our team. Originally, he joined a development class out of curiosity. He and Brandon live in the same town and know each other from church. Bryan has done more custom code or small system projects than almost any other developer. He also joined the team in 2015. He helps with sales, custom projects, pushing on projects that he thinks will yield a return. Lots of work on the adilas lite and fracture project. Very hard working and versatile.

Dustin Siegel - Developer who helped with numerous cannabis and cultivation type projects. He worked directly under Steve to help with that business vertical. Many of the original pages that Steve built were taken over and remade by Dustin.

Eric Tauer - Developer and custom code guy. Originally, Eric knew Steve and lived in Salida, CO. As a note, adilas is Salida spelled backwards. Eric has a background in database work and data warehousing. Eric has done tons of custom systems for clients. Often, Eric would pioneer certain features or logic, as custom code, and then we would bring those features into the main adilas application.

Garrett Kirschbaum - Adilas intern and then full developer back in 2015. Stressful time of building and expansion. He and others helped run the adilas shop with Brandon's help. Garrett was a great developer and helped us standardize a number of tools and features. He was the first developer to work on sub inventory, back in the day. He also did other projects and helped with some developer management stuff.

Charles or "Chuck" Swann - Charles was an instructor at Bridgerland for web development. He builds custom websites, does amazing mock-ups, prototypes, and is a CSS master (styling a website using code). Chuck worked with Russell to help with redesign work, projects, and vision. Chuck worked fulltime for a number of years and now works and coordinates work done by a small hand-picked design and development team. Anything that needs some design loving gets passed over the Chuck and his small team.

Steve McNew - Friend of Steve Berkenkotter's. This Steve helped prep some whitepaper documents to help with getting adilas standardized and some internal audit type stuff. Mostly white papers and putting things down on paper. He ended up getting hired by the local school district and wasn't able to finish the process, but he got it started. He asked some great questions, and we had some good conversations.

Abby Elkins - Abby is Brandon's daughter. Her maiden name was Abby Moore. Abby, when she was little (10-12 years old) helped with some of the original concept artwork for adilas. Later on, she helped with content for the presentation gallery and then the adilas lite plans (fracture). Currently, she is working graphic artwork for different adilas pages. She's now in her mid 20's and has some awesome art and content skills.

Aspen Moore - Aspen is Abby's younger sister and Brandon's daughter. Aspen helped Brandon with some planning and counseling (mental help). Aspen also did some general business consulting with her dad Brandon.

John Maestas - Developer, backend server guys, and designer. John came to us through Dustin. John was uses as a jack of all trades on the backend and frontend. He did numerous projects, documentation, payroll, and page redesign projects. John was also very help to Brandon in working on the notes and comments on the SWOT analysis document. Many other projects as well. Good vision of the future.

Kiva Berkenkotter - Steve's wife. She helped Steve with various projects and planning sessions. At one point, she was in charge of paying commissions and collecting monthly reoccurring payments. Huge supporter to Steve!

Heather Moore - Heather is Brandon's wife. What a trooper. Cheerleader, support, ideas, and consulting. Huge asset to Brandon (me). Thanks Heather!

Jonathan Wells - Designer and mock-up guy. He helped to map out the system and created a number of deep mock-ups for adilas lite (fracture) projects. Great job catching the vision and putting those pieces into a visual representation. We still refer to his work when talking about fracture (future project for adilas).

Jonathan Johnson - Business consultant from Epic Enterprises. Met with Brandon and Steve in end of 2019 into 2020. Really helped us see some needs and opportunities. Later, helped Brandon with some other consulting when trying to define the fracture plan.

Calvin Chipman - Windows software developer. Calvin also did a bunch of web-based work, database stuff, label printing, and API socket stuff. Calvin was the first developer to use the adilas API's to create a native mobile app for a client. He also built a number of special developer tools used by some of our team to speed things up. He's the tool guy!

Cody Apedaile - Bryan Dayton's cousin, Cody helped with a bunch of JavaScript code and changes. He also spent some time working on the UML diagram for the adilas database. We didn't get things finished, but he was working on a new build your own interface (custom to you) for adilas. We ran out of funding. We want to get back to that project at some point.

Dave Forbis - Dave was the official "high tech gofer". He did a bunch of things. Graphics, project management, brainstorming, planning, sales, and helped with managing developers for the adilas shop. He was another great student. He came to a number of training courses and brought so much to the courses. He was also a big support to Brandon during some rough times.

Josh - There are three Josh's. Josh Wheeler, Brandon's friend and developer. Josh Sagert, developer and adilas user (worked tons on the discount engine), and Josh White, Steve's friend from California. Josh White has brought us a number of bigger leads and bigger players, like franchises, and other higher-end clients. Anything recent is Josh White, from California. He helps with networking, sales, and dreaming of new things.

Suzi Distelberg - Sales, training, and deployment. She also worked with some custom projects and doing step-by-step user guides. She has helped with all kinds of projects and even gone onsite for setups and training. Great asset!

Kelly Whyman - Kelly is Dustin's wife. Kelly was single handedly the best independent sales rep that adilas had. She did training, consulting, and sponsored a number of custom projects. Kelly helped Steve and Brandon with reports, functionality, and other things. She got so good at things, state contracts snagged her up to work at state and multi-state level stuff.

Molly Hennessy - Molly was another independent sales rep and consultant. She had numerous clients and got into doing SOP's (standard operating procedures) and other high-end documentation and training. Molly was an entrepreneur and even started creating some of her own product and services. If you search adilas on google, some of the other results are from Molly. Super creative and a great consultant.

Hamid Karbasi - Developer - He has worked with Brandon doing small websites, training, and small tasks. He currently is a manager at a retail store and brings some managerial type skills to the table. Willing to talk about concepts and how they apply to retail and other environments. He is also lightly helping with some planning for fracture.

Gene Spaulding - Friend, entrepreneur, and businessman. Gene is an old college friend. We had a number of friends in common. He has been a small mentor to me over the years. Way back, before adilas, he helped me get my first business loan for a project that I was working on.

Sharik Peck - Friend, entrepreneur, public speaker, physical therapist, and businessman. Good influence and mentor in ways. Sharik and I used to exercise together back in the day. Many of fun walk, run, and weightlifting session. Learning some conference and training skills from him and his wife. They have done really well pushing their product lines and doing some marketing. Trying to get some ideas.

Bridgerland Technical College - Use to be Bridgerland Applied Technology College. Not a person, but a huge help. This is a local technical college in the Logan, UT, area. Brandon's dad, Wayne, worked there. Tons of assets. They provided classrooms, training options, computers, and even an small incubation spot (starter office space) for the adilas shop during the startup phase. Huge asset!

McCorvey's Pro Shop - Also known as Bowling World. Client that had multiple locations. The started out with around 30 and grew up to the 90+ location level, all using adilas. Long time client.

Emerald Fields - They were the first client that wanted their own fully dedicated box and server. They had multiple locations and requested some custom code, reports, and features.

Beaver Mountain Ski School - Client that we helped them track their ski school (snow sport) lessons. Students, instructors, classes, and schedules. Custom interface dealing with elements of time and flex grid.

Bear 100 - This was the first event or annual event client that we did. They used the system for about a week each year. They had 350+ runners and their families that would be on the site for multiple days straight. It was a 100 mile running race with 13 aid stations and a small social portal for the family and friends to watch their runners. This one was special as it had custom input options to upload CSV files to populate the database vs normal HTML form field entries. Records were sent in batches from remote places to adilas for storage and race progress.

High Valley Bike Shuttle - Online ecommerce and scheduling client. They also have a cafe and small retail store. Fun online scheduling and bulk flex grid projects.

Herbo - Mike Roundtree, owner of Herbo, was the first company to do a small white label of adilas. Mike has been a great asset to Steve and the two of them have worked on projects, plans, and dreams. Herbo also has a custom payment solution that they are trying to market and get rolling. Mike has been a great supporter for years. He is also a certified CPA and that credential helps us and him. We would like to get other CPA's on board as well. Thanks Mike!

Nxtlinq AI - AI assistant. These guys really pushed us to get an AI agent inside of adilas. Tons of development took place and lots of prep stuff. We wanted to do a 3-part plan for integrating AI. 1. Teach it how to navigate using the AI quick search (check - done), 2. Teach it all things adilas. and 3. Teach it how to be clear up at the consultant type level. We only got the first phase done. Lots of other plans and such, but we ran out of funding.

Grok AI - Steve loves using Grok. He has built a number of image generation options inside of adilas. He is also working with Grok to feed it data to help with analytics and AI insight. This is not finished yet, but we may end up using Grok as an AI assistant inside of adilas. We have simple and emerging connections available right now but need to really polish things up before going live with the AI assistant options.

ChatGPT AI - We have started using ChatGPT to help with code, explanations, explore resources, planning, and help with training and flow for people and other AI bots. Currently, Brandon, Steve, Bryan, Alan, Josh, Russell, Chuck, and Wayne are using AI in either ChatGPT chat sessions or some other form of AI. We have some using Copilot, Gemini, Claude, etc. AI is actually helping in many ways. ChatGPT is a big one for use. Anyways, they are earning their place in the adilas key contributors list.

There are so many more that I can't list. Developers, users, power users, reps, consultants, trainers, clients, accountants, friends, family, and even critics. They have all helped out the idea farming process and progression. Good stuff! We couldn't have done this alone. It takes a community to do what we are doing.

Small to do list stuff. Emails and tech support. Small check for the bear 100 on a CSV export. They were wondering about a special format. Looking over code and reporting back to them.

Recording notes from 9/26/24 and 9/27/24. Up early checking on the progress of the Bear 100 mile race. Wanted to make sure that the new finish line code worked correctly (live).

New code for the Bear 100 CSV exports. Had to do both the DNS (did not start) and the DNF (did not finish) exports. They used to be very similar. They now have different fields and logic. Small change to the bulk start page. More work on the new CSV (comma separated values) export format. Tons of monitoring the site and fielding a few phone calls, texts, and emails. The new code was being used today on the Bear 100 tracking and runner portal site. Just for fun, here is a link to the news and update that goes along with how adilas helps the Bear 100 mile running event. It has been fun.

Bear 100 - final adjustments to bear 100 runner list. Removed 4 runners, add 3 new ones, and updated a few details. Got the final list from the race director.

Emails and checking on some funding. Working on the Bear 100 and doing some testing and reading through logic flow.

Multiple sessions throughout the day working on the new Bear 100 mile race changes. Going through internal and external pages to show the new dates of the event and the new inbound CSV uploads (new format). Quite a bit of time spent conditioning the pages to handle the new import format and style. Light testing. Uploaded 350+ new runners. Prep work to help the new pages go live tomorrow morning.

Bear 100 data team meeting. We had multiple people on the call with us. Good turnout. We spent some time and explained some of the new changes and how that will benefit all of the people involved. The Bear 100 has worked with the local Ham radio club and has built a small runner logging tool (small piece of software). It will help speed things up, help standardize the input on site and pass adilas good data. One of the new benefits is incremental pushes vs full or whole pushes every time of the runner data.

Switched gears and went internal to adilas and the custom interface pages inside of adilas. We spent some time going over the radio homepage interface. I explained all of the buttons and features. Some of the folks have been with us for years and some were new. Good overview and review. I thought that it was a good meeting.

Touching base with Abby. She has been sick. We will meet up again on Thursday. Pretty quick meeting today.

Jumped over to more work on the Bear 100 mile race and the new import and export formats that are needed for the 2024 race. The race is this coming weekend. Pushed up a new scratch file and sent out a few emails to key data team players.

New changes for the Bear 100 mile race code and runner logging stuff. Looking over emails and new files and samples. They provided tons of new samples, documentation, etc. Almost too much (45 minutes - just reading through things).

Started looking into the test csv upload file for external attempts (non-destructive playground or scratch file). Started making some changes.

To do list stuff. Reaching out to director from the Bear 100. Emails. Checking on bills. Quick phone calls to a number of our guys to touch base. Recording notes from 9/18/24 to 9/20/24. Paying bills.

Phone call with Alan. We went over a bunch of topics. We started out talking about mins and maxes (inventory controls). We then moved into a number of other topics. Here are some quick thoughts:

- Life, motivation, and feeling appreciated.

- Upcoming Adobe ColdFusion Summit - Coding conference coming up in the end of September and first of October

- Talking about percentage ownership of adilas and what are goals are

- I've got a new project coming up for the Bear 100 (new CSV uploads and exports). As a fun throwback... Alan and a guy by the name of Nick helped me the first year we did the Bear 100 code for helping to track their runners and such. That was back in 2015. Crazy!

- The value of a buddy to help you get through the mud and the muck. Sometimes changing the focus from the task at hand to helping out a buddy or having a buddy along helps you get through the rough stuff.

- Alan was saying that he feels like we are developing a "Frankenstein type application". Our plan is to make a whole cohesive application but we tend to do sprints, change out an arm or a leg, and then the rest of the application stays as is - Just for fun, imagine an arm made out of metal, a leg out of wood, etc. Sort of this mismatched or hobbled together end product. We have good intentions. We get hamstrung by fires, funding, and talent. It's a constant battle. What you end up with is - a Frankenstein type application. Kinda funny and kinda sad. It is what it is.

- It would really be nice if we could onboard or help people get going easier. That is one of Alan's goals, going forward. It may take a minute to get there, but it is important and hopefully in the near future (next couple of years or sooner).

- We spent some time talking about the cost of chasing clients and client acquisition costs. That scope or value has gone up for us in the past few months. We have to be careful there. It, meaning costs, can get out of control pretty quickly.

- Alan would like to build some standard templates to help people upload things - items, part categories, customers, vendors, expense types, employees, etc. That would help with the onboarding process and put the power more in the users hands vs waiting on us and/or us holding their hands to do actions like that.

- We are going to touch base next week and see where things are at. That will be good for both of us.

On with the Bear 100 data and software team. Discussing the new app that they made with smaller csv and incremental sending and exporting of data. I was patched in via phone for the audio and using google meet for the video (screen sharing). We talked about plans and timelines. The Bear 100 is in about 1 month. We are planning on moving forward with the new app.

Meeting with Eric. He had me look up what he is doing on my phone. Trying to make it look like a native phone app. He is trying to use as much existing logic and code, just changing the flow a bit. He was showing me some flow and going over questions such as: logging, history, permissions, hardcoded pieces, etc. Talking about uploading images or media/content. I showed him some code from the bear 100 runner portal web app.

Light prep for a Bear 100 radio folk meeting. Going over pages that they sent me with requests, requirements, and flow ideas. We then got on a GoToMeeting session with about 10 of the radio (HAM radio) folks. Good meeting. A guy by the name of Guy was leading the meeting. I took a bunch of notes. Bascially, the aid station workers were asking for limited access to the data. Previously, the only ones who had real access were what they called the data team. We may end up exposing a super small interface to allow the data team to check things (mini API socket or packet distribution). See attached for some notes.

Diverse day. Just got back from a multi-day Adobe ColdFusion conference. Lots of catch-up, phone calls, meetings, and small code changes. Here is a rough overview.

- Spent a little over an hour with Cory, on a Zoom meeting. We were going over to do list items and prorities. We went over a number of smaller needs and upcoming/current projects. General project management type stuff.

- Phone calls with Eric, Steve, and Shari O. - These were all separate calls with differnet topics.

- Added users, permissions, and sent out emails to help get Eric setup with system admin options on the data 11 server.

- Going over emails. While doing emails, got a few small code change requests. Made the changes and pushed up the new code. Some of it was internal and some of it was a request from the Bear 100 data team. Created a public facing test CSV file uploader page, specific to the Bear 100 and their runner data files. No database activity is done from this page. It only looks at the uploaded CSV files and spits back parsed data (it runs through the backend logic but no database changes are made - inserts or updates).

- Paying bills and recording receipts from Bryan and I's trip to the ColdFusion conference.

Checking on the Bear 100 mile race. It was still in full swing. Making a few small changes to some of the pages. Now that it had some real data, we added some counters, links, and other light changes. Normally this would be billable to normal adilas but I had already made the check out for this week.

Checking on some Bear 100 runner counts. It looked like there was a problem. It ended up being that some of the data team (HAM radio folks) changed some records after the race started. Here is what happened. There were a number of people who didn't show up on time to start the race. They were marked as DNS (did not start). Later, at some time, they showed up and wanted to still run. They allowed them to start running with the original group start time. I had already seen the counts, so I had a specific number in my mind. When I checked some of the reports the numbers were different. We got it all figured out.

Phone call with Eric going over the pros and cons of sub/child inventory and parent inventory. We talked for quite a while about the needs, wants, and ins and outs of both options. I put in a plug for the ICC or internal cost correction project that would help allow us to use parent inventory (when needed and there are specific instances where that is better). Anyways, we had a good chat. It comes down to what is best for the situation and for the users. As an analogy, not everyone likes class V (class 5) rapids. Sometimes that's a little too hardcore.

Recording notes from the day. I've been bouncing all over the place today. Part of the gig.

Checking on the Bear 100 race as a moderator/watcher. Recording notes from last few days (9/27 - 9/28).

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.

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.

Multiple different sessions working on Bear 100 stuff. Built them a new page to test the CSV uploads. It uploads the page and then runs through the logic without actually inserting or updating the database. Kinda like a mini dry run. It shows errors and good data. Basically, you can run the test over and over again until everything passes. That should be a cool feature for them.

Met with the Bear 100 data team over GoToMeeting. They wanted to see all of the new features that we had added. New features, both to the public runner portal and new features to the backend radio admin app. Small dog and pony show (showing them around and doing a light review). They, the radio folks (Bear 100 data team) only use the system for a couple of days each year. They need a small review.

We played with the new test CSV file page and they gave me some feedback. We changed some code, while they were on the meeting and pushed it up.

After the meeting, I got a list of runners from the race director. Uploaded all of the runners into the system for the 2023 race.

Working with Bryan on sub inventory reports. We took an existing report and worked backwards to figure out a better join and better query. We needed some grouped data, but it had to come from a specific table with specific criteria. We ended up changing out the SQL and the left join options. Deep database query stuff. By the time we were done, I think it looked pretty good.

After meeting with Bryan, I got an email from the Bear 100 data team. They would like to meet before the race this weekend. I sent them off an invite to an after-hours meeting on Wednesday. They have a request for me to help build a test page for their CSV files. They have some new CSV formats and they want a place to try them out before they go live or do any real database interactions. Sounds fun.

Zoom meeting with Cory. My main two projects this week are the new shopping cart and the Bear 100. We also talked about the public API and 3rd party solutions using either the public API or a special 3rd party API socket channel. We spent some time talking about the discount engine and figuring out a plan to launch the new code while still leaving the old code somewhat in place. We may have to go backwards and retrofit the old code to handle the new custom date ranges. We'll get it all figured out.

We looked at some sub inventory reports and sub reports based off of sub id numbers and other sub reports based off of the RFID tag number. Shari O. had a few questions at the end of the meeting. She was mostly just listening in to say on top of what is going on and happening. Cory got to show her a little bit of the new shopping cart. It seems like we are mostly on top of things right now. No huge out of control fires. I left the meeting and Cory and Shari O. were still talking about emails and clients. Good stuff.

Meeting with Cory. We talked about discounts on special line items and unlimited special parts. We briefly discussed the new discount engine and plans for getting that fully up and running. The other three things that are coming down the pipeline are helping Bryan with some reports, the mini scan cart, and the Bear 100 is coming up at the end of the week. We also looked on data 20 at some possible duplicate invoices. We talked about some possible solutions to prevent that. You have to work pretty hard to make that happen. It happens in real life, but we can duplicate it while doing any testing. Almost like an Internet glitch that happens every once in a while.

After the meeting, emails and touching base with Bryan on pushing code. Recording some quick notes.

Emails and recording notes. Small sort order change on the Bear 100 DNF pages. Ended up recording notes for 9/1/23, 9/2/23, and 9/4/23. It just keeps going. I guess that is both good and bad... :)

Emails with Steve and then working on Bear 100 mile race pages. Simplified the aid station titles on the DNF pages. Had to do some light gymnastics to take a cryptic message and make it read in plain English (easier to read). Added in a sort order on the aid station results. Pushed up new code.

Working on the Bear 100 public runner portal. Finished up the DNF page and pushed up new code. Changed the sort on the full race view to show the winners first vs a bib number sort. Also changed the sort order on the aid stations based on the out times instead of the in times. Sent an update email to the client.

Emails and reviewing a video from Bryan on saving credit card info for Authorize.net (multi-token stuff). Small tweak for the race director for the Bear 100 mile race. He wanted a sort order changed for one of the pages. Made the change and pushed up the code. Getting started with normal Monday morning stuff.

Back on the Bear 100 custom code stuff. Trying to get things done and updated before this year's race. Tweaked the new leader board code, added links, and some conditional logic. Also made changes to the full race view, the runner details, and quite a bit of work on the new leader board page. Pushed up new code.

Merged and pushed up some code for Dustin. Emails to the race director for the Bear 100. Looking at notes on Otter.ai from our earlier meeting with Pete. Phone call with Steve to go over the meeting.

Finished up some test code for the Bear 100 leader board. Did a bunch of testing and then moved some of the test code over to the main index page. Pushed up code and did some testing online with live data. Still need to work on a few other pages, but the data is starting to flow. See the Bear 100 race/webpage.

Mostly working on logic for the Bear 100 and the leader board. I did get interrupted a number of times this afternoon. Only recording 2 hours of this session for the Bear 100 project. All other time will go to the new email servers.

Back to the Bear 100 - Currently, all code for the leader board is on a test file (scratch) to check dumps, variables, queries, and dynamics. Almost done with the logic portion. Still need to run a few more tests and then move code over into the real page.

Other work was stuff like emailing back and forth with Wayne and Shari O. on email server questions. Tech support call to Newtek to get info to pass on to Wayne about the email servers. On hold for over half an hour. Got a request from Bryan to jump on and help him out with the API sockets and customer payment profiles project for the new Authorize.net project. Busy afternoon!

Working on the new leader board code. This is a reverse loop seeing who is the furthest ahead and who has passed the most aid stations and/or finished the race first. This is similar but different to the finish line logic. This one has to trace back through all 12 aid stations to see who is where and in what order (leader board).

Back on the Bear 100 code for the leader board. Building test logic to reverse the values to show the leaders along the way.

Phone call with Eric to go over database triggers and then some emails. Back on the Bear 100 changes that were requested. Working on a leader board page and a DNF (did not finish) page. Spent a bunch of time chasing down a possible error in the code. It ended up being a debugging thing. Once I turned the debugging off, the error went away. that was frustrating. The error was dealing with the relative size of the header and footer. It appeared that the title and filter buttons weren't there and thus I was looking for the error. I ended up finding them, but way off the page to the right side. The debugging code was not responsive and had a bigger forced width. Thus the page was adjusting to that width, even though I was trying to view it on a smaller screen.

Online meeting with Chuck. He was helping me with some CSS stuff and some Bootstrap stuff for the Bear 100 mobile app. We did some training and Chuck helped me make a few changes. He's a good frontend guy and has skills that I don't have. Good session. Pushed up new code to the repository when we finished.

Prep work and making a few new pages for the Bear 100 mobile app. I had made a few placeholder pages the other day. Spent some time today filling them in and mocking up what they will look like. Working on the DNF page (did not finish) and the leader board (who is winning) pages. Pushed up code to bit bucket when finished. Not quite ready to be pushed up live yet.

working on the Bear 100 mobile app. Added in some new code that Chuck sent to me for the top runners. Working on layout, logic, and making the page dynamic. Chuck's code was static (hardcoded - prep stuff). I was adding real data to it. See attached for a couple of screenshots. Sent an email to the race director to show him progress.

Working on the Bear 100 list of changes. Adding a new leader board page, tool tips, new nav links, and some CSS changes. Looked up some documents on using Bootstrap (not very good at that yet). Added counts to the aid station button on the public runner portal.

Reviewing notes for the Bear 100 changes that have been requested. Reading some notes from the Bear 100 race director. Quick phone call to touch base and go over the email. Cody did a great job summarizing things and listing out priorities. That is awesome!

Met with Chuck over a GoToMeeting session. We were going over changes and requests from the Bear 100 folks. We worked on new tooltips, runner counts, and a new leader board. Due to time, we had to put in some fake data, but we will go back and reformat things and populate it with real data. Good meeting.

Working through a number of notes from a client meeting. Work session on the requests for the custom code on the Bear 100 mobile app and the internal code. Spent most of the session getting back into the project. Read my notebook notes, looked around, tried a few things, and sent a text message to Chuck to see if he could help me out.

2/15/23 Edit pages:

- top_secret/secure/statement_home.cfm

- top_secret/secure/add_edit_statement.cfm - step 2 - select statement date range (2 of them)

- top_secret/secure/add_edit_statement.cfm - step 3 - set the dates (4 of them)

- top_secret/secure/bulk_receipt_verify.cfm - top form and looping over the results

- top_secret/secure/bulk_deposit_verify.cfm - top form and looping over the results

1/26 check and pushed final pages with Brandon.  Basic project complete.

1/23/23 checked and pushed 600 pages with Brandon.

1/18/23 checked and pushed 300 pages with Brandon.

1/13/23 updated more datepicker code on pages.

12/21/22 updated more datepicker code on pages (see below). Will connect with Dustin on testing:

12/6/22 Consolidated the Time code that Brandon and Charles did, and met with Brandon to check the code.  Two news and update pages have already been created for this project "Elements of Time Homepage Will Have a New Look" and  "New Look for Working With Time". Next we plan to have Wayne point the data 5 server to the branch (project-2260combine) so that the code can be tested on data 5. 12/5/22 met with Brandon on what we wanted to do with time:

    Date picker:

1. We want:
2. 1. put in 1/1/2 (characters)
3. 2. get 1999 when we put in 99 (not 2099)
4. 3. truncate correctly: 1999 goes to 1999 not 19
5. 4. if I supply a date in the past on the first click I want to go to that first (not how it is currently functioning going to todays date).
6. 5. create documentation in help file and in Adilas docs (update).
7. 6. update to all datetime instances. Check for date validation and go backwards (if I am validating a date I am putting a date in). (search for 'datepicker', '_date', 'date_', '
8. from_date', 'to_date', -form fields are what we are mostly looking for)
9. 7. on the times be able to put in a one digit (1 PM not 1:00 PM)
10. 8. put the datepicker on the content server.
11. 9. roll it out in small batches (10 or so pages instead of all at once)
12. 10. leave Bear100 code alone.
13. 11. communicate with Cory and John.

12/2/22 Spoke with Cory and John about the project.  John said there is a bug with the new picker that needs to be resolved. He said there is some information in the Adilas Docs that may be helpful (Adilas Docs>hamburger link>Adilas Core>components (top links)>date picker (left side dropdown, 'here' link - If you need more information on flatpickr for some reason you can find the documention for the plug-in here ).

Next, all of the datepickers in the system need to be updated to the new datepicker.  Brandon sent an email regarding what needs to be done to update all of the datepickers as follows:

 I found a page that shows some simple date picker stuff. Here is the page: top_secret/secure/add_bulk_flex_grid.cfm – if you search for “picker” it will take you to the different options that are needed. Here is a quick rundown.

• 1st include is set right before the include for basic_css.cfm it looks like this:

 

 

• Then any new date field will need the date-picker class. For example:

 

        on input fields --- the key is the class=”date-picker” part or css class stuff

 

• The last include is set right before the ending body tag. It looks like this:

 

Anyways, there are 3 basic parts… the top include, the new class on form fields, and the bottom include. This is true for any page that is a full page (no black box options). If it does have black box options, it is slightly different. Anyways, just wanted to get you some information. I don’t have a list of files right now, but we want to spread it (the new date picker) across the whole site. If you want, we can meet and build a list or if you want to poke around and fix things, that would be great as well.

The only page that I know we don’t want the new date pickers on is some of the bear 100 custom files. They get dates entered in via special formats and the date picker screws things up. Everything else needs to be updated (to my knowledge).

Going back and recording quick summary notes for a couple weeks back. I got behind during some bigger project pushes for the Bear 100 mile race and the online client facing scheduling projects. The date range that was missing was from 9/21/22 to 10/7/22.

Finished recording notes from the week of the Bear 100 mile race. Crazy week for me.

Went into Smithfield to meet with Cody Draper from the Bear 100. We met at his house and went over pros and cons from the 2022 race that happened about a week ago. He seems pretty happy with how things went. This is his first year taking over as the new race director. We took some notes and chatted for a bit. He is looking to push the system forward. We did some consulting and will be modifying things before next year's race. Good stuff!

Chuck and I talking about automation and tech for the Bear 100. Making it cost effective and still high tech. Looking at mock-ups for the time homepage. See attached for a first round mock-up of the time homepage.

I joined late. Steve was already on and Sean had already been on and left. When I got on, Steve and I were chatting about the Bear 100 mile race and some thoughts and ideas. Steve had the idea to put some kind of stats or leader board dashboard on the public runner portal pages. A quick 10,000' overview. For example: (pretend that the letters are numbers and that it looks cool) x signed up, y did not start, z started. We then could show where everybody is at... x at this aid station, y at this aid station, this many finishers, etc. Basically, a quick dashboard type overview and add some eye candy (stats and counts). Show the tip of the iceberg and then let them drill down as they get the data.

This led us into a conversation about transitioning into graphical homepages with quick snapshots, quick numbers, counts, maxes, mins, averages, and other quick aggregate values. We would love to add this in for our fracture project or fracture concepts. Do this on every page. Alan did some small graphs on the main invoice homepage. We want this spread throughout the entire site. All of the key player groups - (customers, invoices, quotes, items, stock/units, elements of time, balance sheet items, deposits, expenses, PO's, vendors, users, etc.).

Clean-up and comparing data from a spreadsheet to what we had on the live database system. Back and forth comparing all dates, times, and values. Ended up only changing 4 records. I was wishing that I had a better tool or that the race director had flagged the ones to look at. Lots of back and forth and comparing things.

I got a spreadsheet from the race director to edit and update a few finish times for the Bear 100. Manually updating records and documenting with notes.

I had to join late. Steve and Sean were talking about sales, live events, networking, and different angels. They were also talking about the use of videos and stacking the model. Imagine the base of a pyramid - how to set it up, then how to use it, and at the top (ish) what we have. Let them drill-down as deep as they want to go. All of this deals with client acquisition costs and what it takes to keep and maintain a customer or a client.

Next, we jumped into speaking about client facing scheduling and where that is going. We are making tons of progress there. After that, we talked about the Bear 100 mile race and seeking some ROI (return on investment) from some of those special or custom interfaces. We talked about seeing what is next and talking with the race direction. Trying to get ideas and keep making it better and better. All part of the process.

Checking stats, uploading photos and comments into the Bear 100 runner portal page.

We flipped a bunch of aid station numbers around this year. We also dropped a full aid station. I spent a bunch of time on Saturday morning tweaking the code and making sure that the public runner portal was showing the correct information. Going line by line and doing some super deep debugging. Eventually, after checking out the underlying code, I ended up changing where the finish line aid station buttons pointed in order to fix the problem. I had to make sure that the report pointing to the finish line was fully closed vs just the start of the last leg from Ranger Dip (aid 12) to the finish line (aid 13 or finish). It got pretty deep.

Bear 100 files. Updating the runner counts and working on the still out running pages. Emails out to the radio admin team. Working on the manual update for a single record. The actual race had already started and I was still working on some of the backend admin pages. Somewhat behind. I had all of the start and first few aid station stuff done, but cutting it kinda close. Finished up around 10 am ish.

Working on the backend of the Bear 100 radio admin pages. Going over the import CSV code and working on the main custom backend homepage for the Bear 100 radio admin folks. Also working on other backend pages that go along with their custom interface and special pages.

Working on some new verbage to help with a news and update for the Bear 100. Click here to see the final news and update that Cory and Marisa made.

Pushing on the events page. Got it up and live and ready for the Bear 100 race.

Talking with Sean and showing him some stuff with the Bear 100. Looking into Chuck's event code for the events page. Demo and showing Steve and Sean the new events stuff. Small brainstorming on sales ideas and trying to do more special events and such.

Tons of changes on the Bear 100 files. Updating dates and aid stations. Testing JavaScript to help with the photo and image uploader. Finished up the code and pushed it up live. I also spent a few minutes and touched base with Bryan on the client facing scheduling and where we are headed with that project. It should be online here in the next couple of days. Good stuff.

Working on code changes for the Bear 100 mile race. Took out an aid station, changed some aid station names, and had to rechange all of the aid station numbering. Doesn't sound very tough, but it was quite a bit of work. Going page by page and making the changes.

Bear 100 pages and making new pages more dynamic to help with future years and changes that are needed. Changing from hardcoded values to more dynamic variables. Cascading changes.

Good meeting with the Bear 100 radio admin team. These guys and gals will be the data team that helps run the event behind the scenes for the live runner tracking portion of the race. We had six people on the meeting and we spent some time going over the custom Bear 100 runner interface and special custom pages. Small demo, training, and navigating through the different pages of the site. Open Q&A session. Good meeting.

As a fun side note, this is year 7 for the Bear 100 using adilas to help them track the backend runner data. This includes runner details, contact info, aid station times, running legs (between aid stations), and finishing results. The site also has a social side or what we call the public runner portal. From there the runners, their crews, and their families can watch the event, track their runner, add photos, and upload comments and encouragement. Good stuff!

Chuck has been feeling under the weather for the last couple of days. We spent most of our time going over the new code on the working with time (elements of time) page. It is looking good. He had a number of to do list items and we were going through them. Making some decisions and helping him test some of the data driven code options. As a side note, some of the pages are getting really big with the new display code mixed in with the older classic theme. This page is over 8,000+ lines of code just for the working with time page. That's getting pretty big, for just one page.

Light talk about the Bear 100 page and using the mobile ready version this year for the public facing race stuff. We need to get the events page up and going.

Phone call with the new race director for the Bear 100 Mile Race. His name is Cody Draper. We went over aid station changes, when I need runner data and bib numbers, and how the invoicing will work. The plan is to invoice him after the race at $4/runner that starts the race. He's excited.

Use this time id for work done to help promote and do the custom code work for the Bear 100 Mile Race for 2022 and 2023.

Steve and Sean were talking about different race events and reaching out to that vertical to show them what we could do for them. They were talking about some of the custom stuff we have done for the Bear 100.

Wayne and John joined us and Steve was asking about some of the big projects that we have in front of us, in order to be able to cluster and push out bigger and more powerful servers or groups of servers (clustering). We did some planning and brainstorming. I was taking some other notes on the side.

Here are some of my notes:

1. Storing files and images locally on the data boxes

- move things to the content server

- there are 12 photo galleries

- logs, watermarks, alternate images

- ecommerce stuff

- csv files, pdf's, and other custom projects

- waivers, signatures, timeshare docs

2. Database stuff to get all of the pieces in the correct engine format - two big tables that need to be changed up

3. Saved or possible stored sessions - being able to mix session across servers

4. Database and datasource project

- Trying to get to the cluster level

- Eventually... 1 server for code (could be clustered), 1 server for database (could be clustered), and a 3rd server for files, content, images, and other media

///////////

After all of that, Alan and the scrum team jumped on and did a quick standup meeting. I took some other notes there as well (project 1865 inside of adilas). Towards the end of the meeting, Alan was helping the guys with some training and on merging code, pull requests, and bit bucket stuff.

Wayne and I went over some new tweaks to the Bear 100 pages and stuff. Working through some small bugs.

Chuck and I met up and went over some projects and sales ideas. He reported on some of what he is doing and where things are going with his current projects and some others that are still being kicked around. We talked about the Bear 100 site and helping to promote our services to other races and events. He is going to bring this up this Friday in the sales meeting. Trying to push things forward.

Paying bills, emails, and doing an update for the Bear 100 runner portal. I got an email that the public Bear 100 runner portal was showing an error. I went in and looked, and it was dealing with some of the major application changes that had happened over the past week. I had to go in and pull up some old code and refashion a new include file to help with some missing global variables. Got it all done and pushed up new files to the web. Sent an email to the race director to let him know about the changes.

Recording notes and getting caught up from the morning meetings. Marisa and Audrey requested some photos from the Bear 100 for some social media. I went through a bunch of pictures and got them a small sample. See attached for some images of a past race. Adilas.biz has been tracking and running the Bear 100 mile race since 2015 (currently 2021).

Back on the recipe/build to elements of time tie-in project for production and scheduling. Looking into PO line item rounding.

Steve, Cory, and I talking about projects including hardware integrations. We spent some time talking about the Paypod project and possible options there. I gave the two of them (Steve and Cory) a small demo on the Bear 100 mobile ready app vs the older Bear 100 runner portal (non mobile ready or older code). I showed them how to compare the two based on the different URL's or web paths.

Steve wanted me to book some more time to work on his projects for a clients. We looked at the calendar and add a few more hours. Danny and John joined and had some questions about the auto deploy from the master code branch and how to monitor that per server.

The deeper we go, we keep seeing more and more need for more modern code and technology such as AJAX, jQuery, JavaScript, and other things that make virtual one-pager type interfaces work. We currently have lots of pages and sections that do a linear progression from page to page, with action pages, and form submittal and validation. That works great, but more and more requests and requirements are going to be needing the smaller more agile code options that are available. We have a number of developers who can do that, but often they are on other projects. There is a growing need to update our developers and keep them learning and playing with new code and tech. Maintenance - the ball keeps moving, this is not a static game. We need to keep moving as well.

Working on the last page of the Bear 100 mobile ready app. It is the aid station search results. There are 13 aid stations along the 100 mile race. This page dynamically pulls in the results and shows the results as a report as the runners come through the different stations. Finished things up and launched the new sites.

Just for fun - here are links to the three different folders. The main one will be the plain "bear100" folder. The other two may be used to show the difference between the old site and the new site. Once again, just for fun...

Main Bear 100 Runner Portal Site - https://data0.adilas.biz/bear100/

Old site since 2015-2021 - https://data0.adilas.biz/bear100Old/

New site as of 10/15/21 - https://data0.adilas.biz/bear100New/

At least for the first little bit, we will be updating all three folders so that we can compare apples to apples (same data, just a different look and feel, and how mobile friendly the site is).

Emails and then back working on the Bear 100 mobile first site. Building out the final page to show the aid station search results page.

Emails, wrapping up projects, and general to do list stuff. One of the emails was back to Chuck who is providing us with mock-ups for some of the existing pages inside of adilas. See attached for a proposed mock-up for the parts homepage.

Spent the remainder of the time working on the Bear 100 mobile app and mobile first website. Working on the pagination for the photo gallery and the aid station results. Getting close (ish) to being finished with that project. Good stuff.

Checking on an error message from a client. It ended up being funky characters that they were copying and pasting from some outside source that they were trying to use instead of retyping the information. Basically, the copied data needed to be cleaned up or sanitized. The database couldn't handle some of the funky characters or character patterns.

I registered for an online Adobe ColdFusion conference in December of this year. I also sent the guys some emails with information so that they could sign-up as well.

Working on the photo gallery loops for the Bear 100 mobile app and website. Pretty deep and crazy loop with tons of custom logic. Finally got it figured out.

Got a new presentation gallery (sales gallery) link from Chuck. Here is the new link: https://news.adilas.biz/sales-gallery/adilas-advert-index.html

Working on a special loop for the Bear 100 photo gallery in the mobile ready site. Playing with the Mod and modulus operator functions to help find good division results. The loop was pretty tough. We do tons of loops, all the time. For this loop, you have four columns that needed to be populated (left to right), numbering goes vertically in the columns (up and down), you also have a show per page count, pagination (next page of x number of pages), and other dynamic filters. You also have to reorder the sort based on the number to show. It got pretty tricky. I had to start in a scratch file before I could code it live because it was so tricky.

Email to the race director with the Bear 100 mile race. Light sales pitch and trying to sell some of our other services.

Emails and small bug fix for the content server. Making sure that the SSL (secure socket layers) certificates were being used correctly.

"Be a part of the solution" - This is more for me... Sometimes it is easy to find fault or point fingers. I want to try to be a part of the solution and thus need to act as such.

Working on the Bear 100 pagination and photo gallery pages.

Working on more of the Bear 100 mobile version for the public runner portal. Working on the runner photo gallery pages. We also had to deal with an SSL (secure socket layer) issue. Some of our certificates weren't letting people access the sites. Nothing was wrong with the certificates, it totally had to do with time zones and where or who was trying to access them. We had clients in one state that couldn't get in, while others in a different state were doing just fine. We are not sure what happened, but something was going on. We ended up reissuing two of the certificates. That seemed to fix it.

Emails and working on the Bear 100 mobile site. Trying to get the pagination all working and styled out. Also adding in filters to the runner comments (subs of time).

Meeting with Chuck. He and I were working on the Bear 100 pagination and styling those pieces. We talked about some other styling projects that are in the works and coming down the pipeline. We chatted about the WordPress stats and how the new website is doing. We also talked about the Adobe XD mock-ups for the payee/user add/edit permissions and user profile pages.

Danny was on the meeting this morning and asking about a possible mini training session per month. He was calling it a monthly deep dive, where we could pick a topic or section and do some training on that. We could let our clients know, our internal team know, and then go from there. Great idea. He was also talking about an idea for a feedback form and page for monitoring what our users and clients are wanting and needed.

Dustin, Sean, and Kelly were chiming in. Working on emails and other small to do list things. I unpacked a new events banner from Marisa. It looks great. It has a QR code and a web address on it. It also has the adilas logo and some other graphics including Adi (the blue dog avatar) on the banner. It will be used when we help with other events, such as the Bear 100 and other races, events, or whatever.

Bryan and I got together to go over a custom project that he is working on. He wants me to help review some code and we also talked about getting Chuck involved to do some design work. I showed Bryan the new design for the Bear 100 (click here to view) and how it is very mobile responsive and mobile first designed. We talked about how to handle custom projects and how to get Cory involved and how to charge and bill for those pieces that don't flow through the main adilas project path.

Shannon and I were working on adilas core concepts. We started out and did a small review of the Bear 100 from last week and what we are learning and hoping to do in the future. Kinda fun. We then started in on the primary adilas core concepts. The first one is dealing with capturing and recording the story (digital storytelling). That may seem super simple, but that is a huge part of what we are doing. Our goal, is to go over these core concepts and make a small standalone document for each of the main core concepts. There are 12 main core concepts that we are pitching and hoping will get traction and weight. They are:

Adilas Core Concepts

Why & how does it work? Virtual world building...

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Needs, & Goals
5. Decisions & Choices
6. Consequences (Cause & Effects)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Objects & Data Over Time

We decided that we may end up doing a preface or lead in before we just jump into the core concepts. In doing so, we were looking at some existing verbage and seeing if we could use it. The existing verbage is already in story and paragraph type form. Just seeing what we can come up with. See attached for what we are working on. Also, I added some sub notes and comments to cover some of the other verbage that we are looking at. All of this verbage is from our older website and some PDF flyers.

Bear 100 mobile app work. Working on the general show comments and runner support page. Working on some of the custom pagination (next page of x number of pages).

Filling out a tax form that I needed. Back on the Bear 100 mobile app. Working on the full race page, last known aid station logic, and finish line results page. As a side note, the actual Bear 100 race started this morning at 6 am. I was trying really hard to finish up the mobile version so that we could get it up and launched. We still have a few pages that aren't done quite yet. In the meantime, the Bear 100 was using the older pages that have existed since the 2015 race. Bummer, but we are trying!

More work on the full race view for the Bear 100 mobile first app. Also worked on some drill-down links from the runner details (profile) page.

Back on the Bear 100 mobile full race page and full race view.

Working on the Bear 100 mobile runner profile page. Working on different legs of the race output on mobile.

Chuck and I on a quick GoToMeeting to go over some minor display issues with the new mobile Bear 100 pages.

Shannon joined the meeting and we chatted for a few minutes. I told Shannon that I was working on the Bear 100 mobile first app. We decided to skip our normal meeting so that I could keep working. Thanks Shannon!

John was reporting on the size of the different database. That was awesome to see. Shari O. joined and needed some small updates and help to setup some new credit card processing accounts. We got her all setup and good to go.

Working on the Bear 100 large photo gallery page. Text messages, emails, and other to do list stuff. Pushing up code for Bryan and then back on the Bear 100 mobile first stuff. Working on aid station stuff.

Working on code for uploading photos for the Bear 100 mini app. Ran into some small coding issues with the modals, loaders, and general page flow. Working through things.

Working with John and Chuck. The two of them were talking about creating new adilas data tables and other options. Chuck and I talked about the Bear 100 mobile first site and tweaks and changes that we needed. Chuck helped me with some of the layout pieces. Good little catch-up meeting. Here were a few other things that we covered.

- Talking about special events, possible pricing, and info about sponsoring or running a special event

- Forms for contacting us and info about wanting to sponsor things

- Strategy for mock-ups and wire-ups - Chuck and I going back and forth about what works and what is still needed

- Also, just talking about payables and getting things paid

Small demo for Sean and John on the Bear 100 (old code and new code). Emails and pushing up files and doing some merging.

Working on the Bear 100 photo uploader for the mobile app site. There were a number of changes from the bigger desktop version of the site. Working on the Bear 100 photo gallery page for displaying the photos and images. Other emails and what not.

Meeting with the Bear 100 folks. There were nine people on the meeting/call. We had the race director, radio folks, data team, and two of us from adilas (Chuck and I). Good meeting. We gave them a quick demo of the new mobile friendly design and then got into the backend. We went through each of the main buttons and sections. I was driving and did a bunch of explaining and drawing to illustrate flow, logic, and backend code. We had some question and answer stuff, good participation, and great back and forth feedback. Towards the end, the race director got on and thanked everybody.

At the end, we did a bigger demo of the new mobile friendly runner portal and talking about upcoming changes and updates. That was kinda fun. After the meeting, Chuck and I went over a bunch of things and did some planning and scheming. Good meeting!

Working on the new wire-up job for the Bear 100 public runner portal. Also did some back and forth (texts and emails) with Chuck on some feedback on his design for the special events landing page. Most of the session was taking the mock-up HTML files and converting them into Adobe ColdFusion pages with dynamic code that is tied to real databases in the background. We call this a wire-up job, going from a static looking mock-up to a dynamic data driven page.

Recording some notes from this morning and then back on the new Bear 100 code and his mobile first code that I got from Chuck. I also got some new screenshots from Chuck to help with a special events page. See attached for a couple of screenshots.

I joined the meeting but not a lot was going on, so I bailed out to work on the Bear 100 new stuff that I got from Chuck.

Working on Bear 100 stuff. Changing event dates, they needed an aid station swapped out, and prepping files for the public runner portal. Uploaded a number of files to start pushing up new changes.

Got some new files from Chuck for the Bear 100. Getting into the new branch and moving some files around. Made some back-ups of the older files. We are planning a pretty big facelift and mobile friendly version to be pushed up.

Chuck and I touched base on the new Bear 100 mobile app (public facing runner portal for the Bear 100 mile race). Chuck is already doing frontend code and going from Adobe XD mock-ups to HTML pages with the pieces and colors and styles built into the pages. I will be his backend wire-up guy for this project. Our plans are for Chuck to hardcode things and add a series of comments and notes so that I can follow along from the backend.

Sent an email to Steve with some numbers, ideas, and options.

Working with Shannon. We spent the first little bit going over some highlights of what is going on in different areas. We talked about the presentation gallery, the new facelift for the Bear 100 mobile app, and some other happenings.

We had a conversation about the "stone soup" analogy - bring what you've got and through it in the pot, we are making stone soup. The meaning here, is that, if we are playing stone soup, you can't be as picky as say a high end restaurant. We are looking for progress and refining things as we go. If we had all of the talent and funding in the world, we would play completely differently. Currently, we have to play the stone soup game (more of a community effort or just in time type project) vs other well funded traditional methods and approaches.

Shannon and I talked about changing directions. We were going to be working on refining the adilas core concepts for the presentation gallery (verbage and copy), but they already finished the presentation gallery, so maybe we will jump over there and read through things and try to help there. We would really like that to go live and to be able to be used for teaching, training, and helping new clients and prospects get the idea of where we are headed.

See attached for list of adilas core concepts that we were working on. It's not finished, but a great start. We may try to get back to that later on. For now, we are moving on to the next little fire.

Chuck and I jumped on a GoToMeeting session to go over the mock-ups for the Bear 100 mobile app. We already have a customer or public facing runner portal, but it is old school web and is not fully optimized for mobile display. Anyways, Chuck is redoing things and building a fully mobile first mock-up. We went over the pages, screens, and flow for the new mini app. It is looking great!

After Chuck and I finished, I was going back and forth with Eric about some of his special expense types (texting back and forth). Working on the default money types project as well. A couple small texts back and forth with Chuck about other ideas and changes that we could incorporate.

Revamp the Bear 100 runner portal - make it mobile friendly.

Currently this is the public runner portal - https://data0.adilas.biz/bear100/

The runner portal allows users and persons watching their runners to monitor progress, add comments and notes, and upload photos. They can also see the whole race, check on aid stations, and view other comments and photos for other runners. We just want to make it look great and fun.

Here is a link to some screenshots of the old Bear 100 runner portal page - Web link - time_web_gallery.cfm?corp=748&id=8179

As a side note, Chuck may end up using this new race/event face lift as a springboard so that we could maybe do more events and races. Just trying to carve out a niche or specialty product.

Chuck and John were talking about the adilas WordPress site and specs and server stats. They are going to be increasing that box's capacity to help speed things up. They, John, Chuck, and Wayne will end up working together to get the presentation gallery up and live on the adilas servers. Currently, for testing, the presentation gallery is up on Chuck's server until we push it live.

I got Chuck a new time id (project id) for the Bear 100 mile race - public and customer facing - runner portal. We are going to do a small revamp of that site that pulls data from adilas as the runners run the race and check-in at all 13 aid stations. As we were talking, I went in and grabbed a bunch of screenshots of what the old public facing runner portal looked like. It is kinda a social hub for the race. See attached for some screenshots. I'm interested to see what Chuck comes up with for a mobile friendly face lift for that site

Also, dealing with Bear 100 runner portal - we allow friends and family to upload photos. We talked a little bit about uploading photos through mobile and on phones. We are not sure if that is different or the same as normal web.

We then switched to Chuck's current project of the add/edit payee/users layout with a new way to show all of the permissions.

I was going to be meeting with Shannon, but that didn't happen.  So, I spent the time recording notes from this mornings meetings. Chuck gave me a text and asked if I could help him out for a bit. We met over the GoToMeeting session and went over a few things. He has been revamping the add/edit payee/user pages. It gets into permissions and Russell had a design to help that section of code be more user friendly. Anyways, Chuck has been translating Russell's dream into physical pages and changes. It started getting past just a face lift, so Chuck was checking in to see what we wanted him to do. We decided that he will finish up the face lift and then we'll need to pass that project on to a backend developer. No problem, and I appreciate him checking in on that project.

Chuck and I also touched base on possibly re-doing the Bear 100 runner portal page (customer or public facing pages for the Bear 100 mile race that adilas helps track). We talked about a mobile first type interface and making that project look better. We also went over the next steps to get the presentation gallery up and live on the adilas servers. Chuck has that site and gallery on one of his servers right now, but we need to flip that so that it will be on the adilas side of things. He has done a great job on that. Good stuff.

Went out to Cinnamon Creek Campground to give them an adilas demo and show them what we could do for them using adilas and elements of time - scheduling and sub scheduling for their amenities and smaller events and stations. They have a different site that allows members of their church to schedule the main campground, but they are really struggling with changes (the main site doesn't allow them to change very easy) and it also doesn't track the sub events and sub scheduling things very well.

We were talking about getting the main scheduling from the other site and then entering things in bulk into adilas to allow both sites to have the correct info. Once the information gets into adilas, we could show it on calendars, horizontal time views, filter, search, and edit things. It would become real-time access and could be easily shared with other volunteers (missionary couples) who help run and facilitate the campground.

Here were some of my notes:

Cinnamon Creek

- Real-time access

- One sheet wonder

- One sheet for amenities

-- Including what camp they are in

- Public and secure access

- Show special requests

- Show late reservations

- Able to quickly update and repost

- Contact info

- Real campground number (aka Lehi 6 or Manti 7 or whatever)

- Able to keep track of notes or contact logs

- Simple formats to display the data based on time slots, calendars, etc.

- Look into a custom import tool (csv files)

-- Get data from church website and be able to enter or select the data really easily – copy and paste

- Full master schedule

-- Also mini sub schedules

- Simple training for those who will be playing the scheduling game

- Everybody having edit rights – track the history

- Plans for internal communication – changes or tweaks

- Trying to make it more simple and automate what we can – keep it simple

- Less printing or just in time printing vs weeks and weeks out

Some other notes, on the back of a post-it note... Main element of time, subs for the amenities, show group name, single and bulk entry like the Bear 100 race event, easy to remove, simple interface with some mappings, use group name as title, sub titles will be the extras (amenities).

Working on some custom code to help export the Bear 100 mile race finish standings via CSV (comma separated values) file. I could have done it by hand, but I figured we would need it again later, so I built a small export tool.

Working on a new tool to help exports final race results for the Bear 100 mile race. Working on a new tool that exports the final results.

Danny and Sean were on the meeting and wanted to get a report on the Bear 100 mile race from over the weekend. Fun report and they did great. They have used adilas software for 6 years now to run and track all of their runners, legs, and aid station timing. Over 900+ runner support comments were added by family and friends from the runners. Lots of good stuff.

Eventually Eric, Cory, and Steve joined the morning meeting as well. After everybody else left, Steve and I dis some light talks and sharing of some ideas on funding and management. We also pitched a couple of options dealing with adilas shares.

As a side note, we haven't done this yet, but in some ways, we are seeing more need to lean more heavily on the PO and invoice line items table. This could (potentially) allow for multiple locations, multiple dates, and other things on a per PO or per invoice level. This needs to be expanded more and detailed out. Currently, we control all dates and locations from the main PO or main invoice. Those values are cascaded down to the PO and invoice line items. We have seen needs where the line items may need more control over locations and dates, but we have not made that jump at this point.

Custom code work for the Bear 100 mile race. The race started this morning at 6 am. The new code was for calculating the finish based on new logic this year. Code was tested and pushed up.

I got an email from one of the race directors with some bib number and data changes. It took about 45 minutes to delete runners, change bib numbers, and alter contact info. Quite a few changes. After that, I spent the rest of the time working on the scenarios for the new bulk start page for the Bear 100 mile race. That event is this weekend. They use adilas for about 36 hours pretty heavily and then don't touch it again until the next year. Kinda interesting.

https://data0.adilas.biz/bear100/ - click to view the public runner portal for family and friends of the racers

Recording notes, emails, and more code work on the Bear 100 mile race event stuff.

Working more on the bulk start tool for the Bear 100 mile race. We added in a bib number filter and some other fields to help with the process.

Eric got on the call much earlier, but we were still on the Bear 100 meeting. After we got finished, we chatted about the customer loyalty points stuff and decided to postpone the launch until Monday evening. Busy week, this week. Anyways, we chatted and talked strategy. We also talked about pros and cons of outside 3rd parties. That is a mixed bag but part of the game.

Great meeting with the Bear 100 radio folks. We went over some of the event features and made a small little to do list. Most of the requests were dealing with the bulk start tools and the full race view report.

Working on code to help calculate total times in seconds, minutes, hours, and days. This is going to be used for the Bear 100 mile race, but we will also use this to help with other time based reports.

Working on Bear 100 functions and time calculations. The new tools will use total time vs a physical ranking system. We have to do this to allow for a rolling start this year.

Alan checked in and we chatted for half an hour. I showed him what I was working on and he reported on a number of projects. One of the projects that he is working on is a master list or master catalog of vendors per corporation group (enterprise or aggregate level). He showed me some planning that he is doing on an object manager and using both application (server level) and session scope (user level) settings and objects. Pretty cool and we talked about getters and setters, managing our own memory usage, and controlling updates and changes. Good stuff. We also talked about unit testing and other projects that are heating up and coming soon.

After Alan left, I went back to doing more custom work for the Bear 100 race event.

Chuck let me know that he wouldn't be on the meeting today. He is dealing with some moving stuff.

I spent the time working on new tweaks for the Bear 100 race. Custom code for the rolling start and new finish line queries.

Sean checked in and we briefly talked about all of the different "lands" inside of adilas. Merchant processing land, ecommerce land, API socket land, invoice land, sub inventory land, etc. Lots and lots of completely different environments - like lands or virtual worlds.

Back working on more Bear 100 tweaks and custom code changes. They have a need for a rolling start this year, with the virus stuff.

Emails and checking out Chuck's new changes and small video on the adilas docs (SOP's - standard operating procedures) for adilas. This includes meetings, code conventions, style guides, etc. The current adilas docs can be found here:

http://adilasdocs.swanhaven.co/adilas-docs-home.html

Also worked on some prep stuff for the Bear 100 mile race. They use adilas and will be running their event this coming weekend.

Speaking to a client's level and verbage, calling things what they call it. That is a huge key for getting in the door. For example, instead of saying ecommerce, you could say client portal or customer interface. They are the same thing, but the terminology changes and thus the ideas and/or direction that it could go. It is all angles and speaking their language.

Danny, Sean, Steve, and Eric all checked in this morning. Towards the end of the meeting, Steve was having me show Sean around on some of the custom interfaced and functionality that we have done. We looked at the Bear 100 runner site, special events, GPS tracking, time tracking, event tracking, etc. Lots of fun discussions where we could go and how we could help these different clients.

As a side note... some of what we pitch is vision and potential... what if's and ideas and solutions. That's fun.

Emails and coordinating meetings and action items with the Bear 100 folks. Research on PDF's and merge options.

Meet with Cory and Steve at 2 pm - Going over a project review of flex attributes and where it is heading. We also talked about the use of templates at different levels. If we could setup templates (at different levels) we could really speed things up. Once again, standardizing data inputs and data outputs. Some of the topics were dealing with master catalogs or lists that could help standardize the data that is available. Make it simple, make it standard, and then use it over and over again. The old build once, use many concept.

Some of this stuff, master lists and master catalogs, enterprise or aggregate level systems, are really important as soon as you have multiple locations or multiple systems. If not, it might be cool, but not as required or as needed. Our model keeps going out into more of the medium sized businesses vs the just the mom and pops. We are seeing a pull for this sized businesses and what they are needing. Interesting.

We have a company that uses adilas for a 100 mile running race every year. Making a few tweaks to their custom pages to handle the new race this year. Due to Covid-19, we have to handle a rolling start vs a mass or group start. The Bear 100 starts in Logan, UT and end up in Fish Haven, ID (by Bear Lake). 100 miles of mountain running. 13 aid stations spread throughout the course. We track the runners, their times, their check in/outs, the length of the legs between stations, and the length of the stay per aid station. We also have a runner support section that allows family members and friends to watch their runners, upload photos, and chime in with comments of encouragement. This 100 mile race only last for 36 hours, but they use the system pretty heavily during that time. We charge $3/runner for this event. Kinda fun.

Prepping and changing files for the new race. Combing data for a new runner upload.

Recording notes, emails, and looking into a tech support question from the radio guys for the Bear 100 running race. Lots of little things.

I was supposed to be checking on the cross corp invoice to PO stuff. I couldn't get into it. Too big of a barrier to fully switch over to deep coding mode. Too many other little things. When I finished my little stuff, I only had about half an hour. That wasn't enough time to get in and do anything of use. So, I ended up doing more little things. It was easier.

Finished up the new runner counts and stats page. Also built out some links back and forth between the full race view and the runner stats and counts pages. Along with that, we built a new page that highlights runners that are part of certain statuses - like still out running per aid station. The new page has some special formatting to help the users do and find what they are looking for in an easy way. Long day already. Glad to get this part done.

Working on the runner stats and counts. Pushed up the first version to help the radio folks (people who run the data portion of the Bear 100 mile race). It isn't all done, but it is at least workable. Super early morning. Went to bed last night at 1 am and back at it again at 4 am. Pretty tired.

Working on the new code changes for the Bear 100. Adding stats and totals to the full race view. The new totals show up at the bottom of each column in the full race report. Late night.

Helping with the Bear 100. Went into town to help with the pre-race meeting and picking up drop bags. The Bear 100 guys use adilas to track all of their runners through the different aid stations.

Officially release the data 16 server to Mrs. Shari O. She does all of the new system setups. Went into the server and made a few small changes to some settings and such. Emails out to developers about the new serves data 15 and data 16.

Back working on some stats and runner counts for the Bear 100. This year's race will start tomorrow at 6 am. Trying to get a few last minute tweaks to help it be even smoother this year. Good stuff.

I got a call from Shari O. and we jumped on a tech support call together. A client was having a small issue with payables and being able to pay multiple expenses with a single check. We went through it and everything seemed to be fine. We voided out the testing expenses, made notes, and Shari O. will call the client back and help them know what to do. We didn't solve any issues, everything worked through the times we tried it and actually ran some test data through.

Working on some Bear 100 stats and logic. I had to go clear out to paper and scribble some ideas down and filter it down from there.

Once the morning meeting started up, Steve and I were talking about the new servers and getting the developers over and pushing on those new servers. We also talked about getting some of the new graphics and training material out to our users and reps. I spent most of the rest of the session updating data 15 and data 16 servers with some new files.

Working on help files for the Bear 100 and also working through runner count logic and who is still out running vs who is did not finish and who has finished. Checking lots of records to figure out rolling counts and stats.

Just Dustin and I on the morning meeting. I had a couple of phone calls and emails, but pretty quite today. I spent most of my time working on some runner stats and Bear 100 mile race totals and stats. Some of the Bear 100 data team wanted more counts per aid station. This weekend will be the Bear 100 mile race. They have used adilas since 2015 for their race tracking. They have 13 aid stations over the 100 mile course. We catch the runner data out in the field and in the mountains and then use HAM radios and CSV files to pump the data into adilas for a somewhat of a live tracking while the race occurs. Family members can add notes and comments and upload photos while watching the progress of their runner. Kinda fun and fully custom but a creative use of elements of time.

Steve was talking about getting a designer to help us with the Bear 100. He would like to take it out to Google maps, GPS, mobile friendly, and even allow for people to use our site to do sign-ups and other pieces. We could have the site tied out to ecommerce and allow for tons of other options. That could be fun.

Eric came into the meeting and had a couple of questions about customizing the invoice and quote process. We talked about parent inventory, sub inventory, parent attributes, flex grid tie-ins, and even black box custom tables. We also talked about adding in some blank or generic flex fields in the quote line items and the invoice line items. They want some custom fields per line item. Steve was saying, don't tell me what you want... show me. That way we know what tool to use and where to put it into play. Steve was also talking about maybe going up steam and setting those moving variables up higher on the customer level. In a way, the over arching question was I want to extend the existing options and functions per invoice and quote line item. We then have to help, how do we figure that out and what solution could we use to solve that problem? Good stuff.

This doesn't play in quite yet, but at some point we would love to get into real in-line database extensions. That is somewhat of the bigger brother to the flex grid tie-ins. Being able to add and subtract data points and data fields per section. As a side note, we have tons of companies that virtually commandeer (take over - like a pirate ship) any field that they can to get the job and/or task at hand done or finished. Kinda interesting.

Steve wants to get more information, from the source. He would like to get a real world scenario and then make a plan from there. Not just a quick band-aid, he wants to help develop the solution. What are the processes, what are the needs, what already exists, and what else is still needed? It keeps getting deeper and deeper (4 and 5 levels deep).

There was an analogy of a "part changer" - think of mechanic that just swaps out part after part in order to fix something. We really need the mechanic that gets in there and looks at the problem and then makes a decision. From Steve - It's not how fast you go, it's how well you go fast - older Porche commercial.

///////////////////////////////////

Switching gears, we started talking with Wayne about servers.

We were talking about virtual machines, physical servers, load balancing, and the difference between hardware problems and software problems. We were talking about clusters and getting redundancy and depth of options. If we stay with Newtek, we need to build in some of our own pieces. If we go more with AWS, we get to just use some the existing pieces. There is a trade off - AWS has more options but it also a deeper pool. Newtek is not as deep, but in some ways easier. We were also talking about rollover, fail safe modes, mirrors, etc.

We spent quite a bit of time talking about the Adobe ColdFusion engine and how we could potentially configure cluster type environment. When you get out of a single machine environment, what do you do with the database. On a single machine (server or dedicated box), it is simple. On a cluster, you have to keep things moved and/or separated. We would love to break some of the system down into their own databases. The idea here is making each database corporation specific vs server (whole box) specific. We have talked about this for years (since 2012 ish) and have called it world building and other project names. We really want to do this, but we also know that we have tons of code changes that are needed. We could separate out the shared tables in the existing database schema but we would have to do it table by table. As a side note, we have already done this very process for invoices, invoice payments, po/invoice line items, customer queues, sub inventory, etc.

One solution would be to create a corporation specific datasource (pointer to a specific database) and then help that get migrated and pushed around. We also talked about loading in objects per user that has all of their corporation specific settings and values. Eventually, we will still need to break out the payee/users so that we have a master list and then allow them to be merged and virtually bridged to any corporation and even any system. We still have all kinds of exceptions, such as be in corp x but pretend like you are in corp y (look and feel and settings). It gets kinda crazy.

The subject started to switch to more and more object oriented programming, storing values in session objects, and other objects that are server based. We also talked about database server clustering and moving all databases (per corporation) to a dedicated database cluster that only served up data and content. Lots of possible configurations and options. Both Alan and Wayne were talking about cross-schema queries and all kinds of advanced things. As another side to this equation, we are seeing more and more of a need for aggregated totals, auto processing, daily task management, etc. All of these things play into the mix. We are seeing certain tables that are great as shared tables and other tables that really need to be independent and corporation specific.

As we move forward, even towards a fracture type model, we will need to separate databases, logic, move more towards object oriented programming, API socket calls, etc. Just for fun, Wayne and Alan were talking about different levels and using bigger teams - backend guys, database guys, middleware guys, frontend and UI (user interface) guys, etc. We aren't that big.

Steve's idea... Alan, Steve, Dustin, and Brandon are all going to be at a convention. Let's use that time to do some planning and take it to the next level. That's a great idea.

Prepping and uploading 333 new runners for the Bear 100. They will be using the adilas system this weekend for a 36 hour, 100 mile race across Northern Utah and Idaho.

Downloading runner lists for the Bear 100. Prepped and combed the data to make sure I had good data. I will be importing new data tomorrow into adilas.

Met up with the Bear 100 folks. There were 4 of them on the meeting. We went over a number of custom buttons and interface pieces. They had a small to list for me. I have attached my notes. Mostly, they just need ways of seeing things quicker (stats at a glance). Should be easy enough.

Emails, small bug fixes with Calvin, installing new software updates, Bear 100 stuff, and server resets.

Bear 100 mile race meeting. They use adilas for tracking all of their runners and aid stations.

Went into town and had a meeting with the race committee. We went over a big to do list. Adilas will be tracking the runners again this coming fall. They, the Bear 100 folks, are also looking to redo their website and make it more mobile friendly. Another thing that may be coming down the pipeline is a trial version of 10 satellite GPS units and tracking the runners through the full course. That will be fun and exciting.

Went into Logan to participate in a Bear 100 meeting. The meeting was at Bridgerland (Btech) to go over a changing of the guard (key players) for the Bear 100 mile race for 2019. They use adilas to help track runners and aid stations. Most of the meeting was dealing with other parts of the race vs just adilas stuff. The only thing that they wanted was to head more towards mobile or full app stuff.

The first part of the meeting was spent chasing some big queries. Then we rolled into a discussion about cross corp barcodes and buying and selling sub inventory and being able to use a set barcode for that item. Basically, one systems sub inventory would then be allowed to be sold from another corporation based off of a barcode that was set by the original corporation.

I was thinking that it will end up being tied into this new adilas community funded project. See the link below.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=22&id=1348

After the meeting, I kept working on some code for the Bear 100. I spent some time working on emails and light tech support. I also reviewed a label demo video that Calvin Chipman did for Kelly Whyman and Steve Mitchell. This was the first demo that I had seen with Calvin's new wizard style label builder for the upcoming adilas label builder. Compared with the old prototype, this looks awesome. I put up a small screen shot of the video. The real video is awesome, but I don't have permission to push that up yet.

The video had and brought up some great questions dealing with the adilas label builder... things like: permissions on labels, history on labels, simple mapping interface, right clicks vs buttons, checkboxes vs scrolling drop-downs, visual indicators, auto save, prompts when closing, AWS (amazon web services) and putting the Windows software on a Windows box and then allow the user to login and use the program from there. Tons of good stuff.

Adding tons and tons of photos to the Bear 100 mile race gallery. I shot over 400 photos over the weekend. I've only posted about 130 so far. I'll do more later.

https://data0.adilas.biz/bear100/bear_100_photos.cfm

Josh gave Steve and I a quick demo on his GPS stuff and how he is able to track multiple drivers based on elements of time. He is using the time sub GPS/RFID tag tracking fields that already exist. Pretty cool. And, he has developed this fairly quickly based off of existing adilas pieces, Google maps, and some of his own custom JavaScript. I also showed Josh what Calvin had done on his GPS stuff back in September of 2015. Here is a link to the Calvin stuff (done back in 2015).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=1061

Started working on a news and updates page for the Bear 100 mile race. The race is tomorrow and I wanted some of the adilas users to pop in and see what was going on. Just for fun.

Making a number of new tweaks to the Bear 100 runner portal (social media piece for the 100 mile race). Added two new fun reports. One is for the runner support comments (family and friends who chime in for their runner) and a new general photo gallery (trying to have the people push up more photos). I also added in a sort order to the internal image/scan report. It can now go newest photos/scans first or oldest first. Here is the link to the Bear 100 runner portal. It is outside of the secured environment and is viewable by the public.

https://data0.adilas.biz/bear100/index.cfm

Spent some time updating the custom pages for the Bear 100 mile race. Changed race dates, added new sorting options, and worked on some JavaScript for the public runner portal section where friends and family post comments, encouragement, and photos. Kind of a mini social media section for the runners. Trying to make the experience more straightforward. Uploaded and tested some of the new pieces.

On the morning meeting with the guys. Steve, Josh, and Dustin were tracking down some of the new Metrc API stuff (killing plants and disposing of product). Alan came on and gave us a demo of what he is working on for the new invoice homepage. It will have some graphics, charts, and limited data being returned. Mostly some sums, historical data, and say the last 10 to 25 real transactions (for example, the last 10 invoices, the last 10 PO's, the last 10 expense/receipts, etc.). Great demo.

I was working on a runner upload for the Bear 100 mile runners. They will be using adilas this weekend to track their 100 mile race. Alan went back to working on his charts and graphs and Steve, Dustin, and Josh were working on syncing data between different systems.

We ended up having a really good conversation about dates, times, spans, buffers, logic stacking, data threads, and helping to do clean-ups. A lot of the conversation was dealing with how to sync up multiple servers (even potentially servers owned by different companies and/or systems) and how dates and times are pulled. Very interesting how things come back to time and how you sometimes have to either buffer and/or take spans into account. Time feels very solid and static, the problem becomes just like a line in the sand... if the record is on one side or the other, no problem. The problem comes in when it spans and/or plays through a given area (like a line in the sand). That gets tricky and the computer code or query has to be either flexible or somehow incorporate the span and/or buffer. Interesting how it kinda gets into adding in flexibility into a rigid or super tight system.

It reminds me of how we have seen this over and over again, how the system needs to flex and allow for bubbles and/or areas (virtual pods) where things can flex and then it comes back together at a future point and/or checkpoint. Here is an older entry with tons of good info (10/14/2014).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2894