Adilas.biz Developer's Notebook Homepage

[reset this page] . [historical web outline - entries by month] . [adilas community funded projects] . [contact adilas.biz support - email form] . [help]

Search The Adilas.biz Developer's Notebook
Time Period:	Daily (enter the day you want to see) Monthly Custom Date Range to
Template Filter:
Color Code:
General Text Filter:	(use a plus "+" sign to separate search terms. ex: jack+jill+hill)
Sort Value:

Adilas.biz Developer's Notebook Report - 1/1/2017 to 1/31/2017 - (114)
Photos	Time Id	Color	Title/Caption	Start Date	Notes
	Shop 2127		Adilas Time	1/2/2017	GoToMeeting session with Nick, Alan, and Steve. We worked on some debugging of some pages that deal with multi-corp bank reconciliation stuff. Apparently, only some of the servers had been updated. Lots of testing and back and forth stuff. We then had a developer and project manager from a different company come on and help us with their API socket connections for Nick and Alan. They were part of the state API stuff that Steve has been working on. After we got things working, we did a small session with Alan to get his system up and using sub inventory. Both Nick and Alan were doing awesome. Good session.

	Shop 4602		Virtual Post-It Note	1/2/2017	-On 3rd party API's we need to add the 3rd party validation back in...see the "old" web/webapi/full circle collection.cfm -More requests for pre-calculated data and aggravate functions for stats. Average ticket value, most popular, totals, sums, maxes, min, ect. People love that we catch so much data, the problem is try to calculate tons of data on the fly, we may need the water bags and feeders.

	Shop 2131		Calvin Time	1/2/2017	Quick phone call with Calvin. We talked about some updates to the tools that he has developed. Touching base and passing along updates.

	Shop 2135		Shawn Time	1/2/2017	On a GoToMeeting session with Shawn. We spent the session looking over Shawn's progress on the project to split up the customer queue table into corp-specific tables. We have been having problems with that database table. We coded some logic and pagination stuff and did some light testing. Shawn was tired, he has been up all night working on new code, tax table updates, and what not. Good session.

	Shop 2173		Full circle API	1/2/2017	On a GoToMeeting session with Bryan. We went over the existing Full Circle API sockets. We also quoted out building in two new sockets for them. We did some drawing and brainstorming to make sure we were both on the same page. We also talked a little bit about adding in some security for the 3rd party API sockets to help them be a little bit tighter.

	Shop 2175		General	1/2/2017	Emails, tech support, and recording bills. Phone calls with developers and helping them with questions. Calls to Russell, Calvin, and Bryan.

	Shop 2128		Adilas Time	1/3/2017	On a GoToMeeting session with Alan and Steve. Working with Alan on some state API testing. He is working on the data mapping part of it and getting some JSON objects ready to send out through the API. We ended up breaking into individual work sessions. I did some tech support stuff and started tracking down a bug in the recalc and update cart line item method. Trying to figure out when and how to reset the original list price after a price change and/or a tax category change. Comparing old and new files and their logic to map things out. Dealing with deep logic and detail stuff.

	Shop 2132		Calvin Time	1/3/2017

	Shop 2108		Russell time	1/3/2017	On a Zoom session with Russell. He had a tick list of items that needed to be worked on. We got a couple of the items done. One was, we added the HTML editor to the parts and general items web settings (stuff for ecommerce). We then built in some helper values to help with JavaScript conflicts between the new AFB snow owl theme and the pages that show sub inventory. We fixed and tested all of those pieces and pushed up new code. At the end, we worked on some sample code to allow the custom links to open in new windows if a special tag was added. Russell will work on that code and when it is ready, we'll merge it in. We only got one done, but the concept was there.

	Shop 2177		ICS csv files	1/3/2017	On a GoToMeeting session with Bryan. We were going over some light debugging on a custom project for a company. The project ran every night and built a .csv file and then FTPed the information over to a remote server. We had to add some code to help filter records (data to push) and then do a file clean-up process after the fact (delete the older files that had already been pushed). The project was for a company called ICS and the code was located in the web/tasks folder. We also took the live file and built in some laser focused access points to test things without hurting the main flow of the live file. The whole session was building and breaking things and then making them stronger. We had to do some research, testing, and then tweaking things to match. Kind of an advanced debugging session of sorts.

	Shop 2129		Adilas Time	1/4/2017	On a GoToMeeting session with Steve. We chatted and talked until about 11:15. At that time, Alan came on and stayed working with Steve until about 12:45. I was mostly working on the update cart method and trying to figure out discounts and price changes (original vs. new and/or updated and/or discounted prices). Earlier this morning, while Steve and I were on the call, we talked a lot about portions and percentages of revenue. We talked a lot about a stepped (goal based) percentage. For example: Say you wanted to make x thousands on a reoccurring basis, say we offered you a certain percentage based off of deposits and actual revenue. Say we did this until we grew enough to get you to that number. At that point, we could re-negociate the percentage. Ideally, as the growth and goals happen, we could possibly even lower the percentage as long as the needs were still being met. For example: Say you wanted to get to $5,000 reoccurring. Based on your percentage of 1, 2.5, 3, 5, whatever, how much would we have to make to reach that goal? Say you were at 5% for a number of months. Once we reach that goal of $5,000 per month, we may reallocate part of the percentage to help lift and float other members and/or support other parts of the inner circle. This assumes that growth is still moving forward, but instead of getting 5% the next month above and beyond your goal, you would get a lower percentage but still be able to get the $5,000 that you were looking for. If you want to up that number, we could relook at percentages and base growth off of that based on the goals. Basically, a growth based model that has some flexibility based on end goals and needs. Long story made short, instead of saying 5% for life, it would be 5% until we got to a certain level. If things keep growing, we might lower that percent and reallocate the additional percentages to other players and adilas family members. Basically get people to a comfort level and then help raise the other members. Everybody has a threshold and/or magic number of sorts. We also talked about the word "dependables" and how that would play into the mix. We could virtually hand pick the dependables and then help them work towards their magic number (what they need to be comfortable). We could then help them get to that number and use growth and goal based models to get there. Basically, let them decide the numbers and values and then build a plan to get there. That gives us a goal and a place to work toward. See attached for a small spreadsheet that does some simple calculations and projections based off of percentages.

	Shop 2133		General	1/4/2017	Working on the update cart bug for changing prices, discounts, and original list prices. Tested and pushed some new code up to the servers. This bug wasn't that big of a fix, but I had a hard time locating it and making the changes to make things stick. Hopefully, it is fixed now.

	Shop 2174		Shawn Time	1/4/2017	Meeting with Shawn on a GoToMeeting session. We touched base and mostly worked on our own projects. I was working on Beaver Mountain stuff and Shawn was checking into custom payroll jobs and requests. We decided to meet tomorrow morning.

	Shop 2179		Quotes with Dave	1/4/2017	On a phone call with Dave. We did talked about some different quotes that were needed. 1. What would it cost to take customer discounts out to ecommerce? I quoted him 5 hours or $500. This project has been started but needs to be finished and wrapped up. 2. What would it cost to do web coupons and/or preset campaigns or promotion codes? This would include discounts with dollars off, percentages off, free products, discounts based on a category, or based on selected items. We could do date ranges, expiration dates, no dates, etc. We would need settings to help with discounts and dollars off that are based on per item or per cart (total purchase)? Going back, see element of time # 979 inside of the adilas.biz - adilas community funded projects for a rough idea. That project is set at $20,000. I'll bet we could get that going and make some great progress for around $4,000. Also, by way of a note, Brandon has already built a similar process with his LearnToFreeride.com product. It has a full promotion code options with a full web-based system for tracking, showing, and setting up the promotion codes. We might have to borrow some code from the LTF project.

	Shop 2181		FTP queries	1/4/2017	Phone call with Bryan. We went over some database fields and how to map them to get the correct results.

	Shop 2182		Beaver Mountain Changes	1/4/2017	Working on some changes for Beaver Mountain. I added a daily student search to the printable lesson schedule report. I also went into the flex grid and allowed for the main tie-in id numbers to be changed. This allows for a piece of flex grid to be easily switched between id numbers of the same application types. For example: This allows for a piece of flex grid to be switched between one element of time to another. This is also true for invoices to invoices, customers to customers, expenses to other expenses, etc. For Beaver Mountain, this means being able to take a student (info held in the flex grid tie-ins) and reassign that student to a new and/or different lesson. This will help add more functionality to the flex grid application. Pushed up files and tested.

	Shop 2180		Shawn Time	1/5/2017	On a GoToMeeting session with Shawn. We were working on our own projects and doing some clean-up stuff. I was recording notes and finishing up notes from past appointments. Pretty casual session.

	Shop 2130		Adilas Time	1/5/2017	On a GoToMeeting session with Steve, Alan, and Nick. We started out the day talking about an upcoming meeting with the server guys and trying to schedule a group meeting to talk about world building (database stuff and code stuff on our end) and backend technologies such as servers and data center stuff. We then broke into individual work sessions. I was working on the Beaver Mountain horizontal time view page for scheduling ski school lessons. That page is pretty deep and pulls data from multiple places and shows it all in a nice horizontal time view. Later on, Steve and I had a meeting to talk about plans and ideas. Here are some of the ideas from the meeting. - fast track to help people get to their magic number - kinda like a reverse snowball to build people. Normal snowballs go toward solving debt, a reverse snowball would be building up dependables - keep putting more tools in the shed - offer different services including basic web sites - if is easier to sell a full package vs. every possible module or special service - as more and more technology comes to pass, we could roll more and more features together - skate where the puck will be or is going to be - working towards an unlimited model - what do you want and need - it is all included - model of a base starting point and then charge for storage, processing, and bandwidth - fee based usage - get some percentage things in place with our inner adilas family members - as more and more clients use our services, we could even drop our prices. - we need to head to more mobile - Steve and I were playing with some numbers and projects - that is fun to play with some of the numbers - maybe look more into this and keep pushing and forecasting - make it more of a plan/possibilities - the footprint - what impact are you on the company's earnings - there are tons of other possible services such as storage, migration, cold storage, custom code, consulting, training, setup, ecommerce, usage, bandwidth, etc. - allow clients to virtually manage and/or drive their own systems - what do they want, what do they want to call it, how much, how many, how long, how much data, what other needs and/or wiring? - keep building on a generic model. we can then add skins, templates, and themes to help customize for different verticals - gps tracking and other 3rd party options. white labeling and other options. - keep building - piece by piece - slow and steady wins the race - sometimes it comes back to permissions, settings, and relationships - there may end up being more and more API socket connections - plan for that and help sew things together. - remember training and helping others see the vision of what is going on and the potential that is out there - keep building towards full world building pieces and concepts - mini conversions, sub inventory, sub part categories, qr codes, etc. Technology keeps going, we need to keep playing and trying to advance the ball. - Try to take things more and more to the dynamic level. Settings, permissions, database stuff, and underlying backend structure. - other project coming down the pipe line - tiered pricing matrix stuff, sub inventory options for ecommerce, more balance sheet stuff (watchers and feeders), more stuff with elements of time (rentals, reservations, gps, rfid tag, sub payroll, sub "any" assignments).

	Shop 2134		Calvin Time	1/5/2017

	Shop 2109		Russell time	1/5/2017	On a Zoom session with Russell and Dave Forbis. We started out doing some quotes and rough ball park figures for new and improved features. Some of the topics were: campaigns, promotion codes, coupons, auto apply discounts for ecommerce, in-line dollars off discounts, smart cart logic, pushing sub inventory out to the ecommerce pages. We went through a number of ideas, options, and possibilities. Dave really helps to bring a positive reality to the projects, their scope, and what it will really cost to get those things done. He is also very good at suggesting possible side options and/or stepping stones to reach the full dream or vision. Russell is all about coving costs and making sure that we are not overextending ourselves. He does a good job managing the projects and has a good way of managing expectations and budgets. After that, Russell and I merged some new code together and pushed up some new changes. The new changes were on the snow owl theme and being able to open up custom links in a new browser tab or new window. Russell is getting better and better at the code side of things.

	Shop 2178		Black Box Project/ Metrc and Leaf Data	1/5/2017	Phone call with Nick to touch base. I got a small update from him on the projects that he is working on.

	Shop 2148		Brandon out of the office All day	1/6/2017	Great day. Spent it up on the mountain.

	Shop 2140		Adilas Time	1/9/2017	On a GoToMeeting session with Alan, Steve, and Eric. We started out going over current projects and what the priorities were. I gave a small list and then we talked about it. For the record, here is a small list of things that I saw as needed: - Fix the forgot and reset password section. The old code only deals with a single server. We now have multiple servers that need to play as one. - Planning out the next phases and projects. - Changes to the Beaver Mountain site. They need some new code and logic to help automate things on the horizontal view of time (custom interface page for Beaver). - Circle back around and work on the dollars off for in-line discounts. - Scan and finish up the year end stuff. We talked about this and I will be sending it to Craig. - Sub inventory updates and changes. We had some complaints that the sub attributes were being displayed in a horizontal view and you couldn't see everything all at once. We need to build some of those pieces into a vertical display. - We need to go through the adilas API and update documentation and do some fine tooth combing and testing. - Work on the adilas user guide. - On sub inventory, we need to preset the checkbox for items marked as subs only on the mini add/edit PO line items page. This will help save a click or two. - On invoice line items, we need to add a way to look-up possible subs incase something was miss recorded in the cart. The users want a "subs" button similar to what we just released in the view cart page. The cart stuff allows us to convert parent inventory to child inventory. The invoice stuff would just help with updates and recording the right RFID tags and other sub info. After the morning meeting, Steve and Alan started working on testing state API's and such. I started in on some of the sub inventory tweaks and changes. We all did our own thing and interacted as needed. We had a client get on and work with Alan and Steve. We then had another developer get on and work with me on a possible custom cart and item based flex grid issue. We tested as much as possible and saw that it worked according to what we tested. The rest of the time was spent answering questions, working on our own projects, and pushing the ball forward.

	Shop 2144		Calvin Time	1/9/2017

	Shop 2185		tax and customer facing flow	1/9/2017	Helping Bryan with some direction on how to code a custom invoice that is able to hide a single line item and show its value under the taxes section. This is for the C4Ever cash management guys.

	Shop 2136		Shawn Time	1/9/2017	On a GoToMeeting session with Shawn. We were looking and doing some planning on new overtime, normal time, and double time payroll calculations. We went through and recorded part of the session and then built up a small little text file to help with the project planning and quoting process. Steve was on the line as well and chimed in here and there. Also, as a side note, we have had three different developers in the last month or two come to us with questions about time cards, time clocks, and new overtime options and functionality. Interesting.

	Shop 2188		css format	1/9/2017	On a GoToMeeting session with Bryan. We were going over some custom code and pulling the page back into a normal or standard adilas CSS format. It had been tweaked a bit and wasn't able to follow suite. We then worked on some other small project questions and such.

	Shop 2141		Adilas Time	1/10/2017	On a GoToMeeting session with Steve. I was working on changes to sub inventory and he was doing phone calls and what not. Most of what I was working on was a new vertical display for the sub attributes (they used to be horizontal or across the page). I also spent some time and worked on the my cart favorite buttons. Steve had a guy who asked if we could tie in the barcode logic for the my cart favorite buttons. We did and that is awesome. Here is how it works: If your main item is a normal parent item, it will work as before. If it is set to subs only and it can only find one open package, it will play at the sub level. This could be viewing the sub package details page, adding a single sub to the cart, show the subs in the advanced add to cart page, or passing in custom values to the direct add to cart page or the advanced add to cart page. Super cool and makes the my cart favorite buttons play better with subs. The main key is the main item status being set to subs only. That is the main key. I also fixed the advanced add to cart page and pushed all files up to the live servers. Light testing and merging into the master branch.

	Shop 4958		Virtual Post-It Note	1/10/2017	-The goal is to be able to empower the individuals. -On personal settings we may need new CSS. -We may need to do a new permission to override and help with personal settings from a corp admin level. -We need to change the button functionality to sell subs sand use the bar code login to sell an open sub if marked as subs only. -Fix add Quote API problem and/or bug INYO NV

	Shop 2145		Calvin Time	1/10/2017

	Shop 2110		Russell time	1/10/2017	Working with Russell over a Zoom session. He showed me some of the new features he is working on for the blog and the project manager. It is still in the baby state but I can see things coming. Dave Forbis came by and he and I chatted with Russell and talked a bit. After that, Russell and I started to roll into our next joint project. We want to add some user specific personal look and feel options. This will allow a corporation (business entity or world) to have its own look and feel and yet allow users within that world to have their own look and feel. This was a request from Steve to Russell. The new branch is: BWM-23. We got the new database changes scripted and started to cascade the new settings and changes. See attached for a small action plan.

	Shop 2186		General	1/10/2017	Started going over some of the adilas API sockets for quotes. They have been released but not yet checked or tested. I was in there making tweaks and doing some light testing. This is still on our to do list. As a note, one of the problems was that some of our internal responses reply with HTML. That get tricky if you are sending it back across via JSON. Anyways, just wanted to make a note of that.

	Shop 2189		Cart payment method	1/10/2017	On a GoToMeeting session with Bryan. We were going over the cart checkout process and how to virtually override the normal process and go right from a payment page to the submit cart page. We had to tweak out some of the session variables to make things happen. We also did some more CSS clean-up for a project that he is working on.

	Shop 2142		Adilas Time	1/11/2017	On a GoToMeeting session with Nick and Steve. Working on some prep stuff for a meeting with Newtek (our server guys). Drawing out a small plan for what we currently have in the way of our world building concepts. We had a meeting with Newtek from 10 am to 11:15 am. See other notes for details (element to time 2183). After the meeting, I spent some time and updated some notes and uploaded some images and such. Trying to stay semi-caught up.

	Shop 2183		Meeting with Newtek	1/11/2017	On a GoToMeeting session with Newtek. They had Adam and Andrew on the line. We had Steve, myself, and Bryan on the line. We started out and talked about back-up plans, disaster recovery, and storage options. We then let them talk a little bit about a cloud based VPS type system. We took some notes (see attached) and went over some ideas. After that, we did a small walk through demo and tried to show them what we have and a small vision of where we are going - world building concepts. We used the GoToMeeting tools and did a lot of drawing and pitching of our ideas. We used a bunch of the graphics that we have already made and then drew on top of those graphics to illustrate different points. They are going to look deeper into our account and get back with us on some suggestions. Good meeting overall. I think it helped them get an idea of what we have going on. That, in and of itself, will really help. They most likely will need more of that as it is somewhat hard to wrap your head around from only one meeting. That is ok, we'll just keep going and hopefully it will sink in deeper and deeper. We are excited to get some professional help from the actual data center people. That will be good.

	Shop 2191		Being able to switch out headers and footers	1/11/2017	On a GoToMeeting session with Bryan. We looked into ways of adding conditional logic around includes for headers and footers. We already have done this on other projects. We went through some of the old code and took notes and ideas from it. We then talked about other black box access points and how best to code things to help with the custom flow that Bryan needs for his projects. Lots of drawing to show flow and then looking at code for examples of what has already been done.

	Shop 4959		Virtual Post-It Note	1/11/2017	-On the beaver horizontal report . . . we had a bug show up if the start/end dates were different. Say 1/8/17 10am to 1/9/17 12am - if took the time diff and tried to find position. -Allow for companies to get their data. -Maybe even full database and SQL code. -Push up videos to the content server. -Having people push on thinks that are huge. -Negative variable (-16) slots backwards. We may need to check for that.

	Shop 2146		Calvin Time	1/11/2017

	Shop 2187		Phone call with Steve	1/11/2017	On the phone with Steve talking about our meeting with the server guys and also touching base on some upcoming projects.

	Shop 2143		Adilas Time	1/12/2017

	Shop 2192		printing invoices	1/12/2017

	Shop 4961		Virtual Post-It Note	1/12/2017	Hours (9-12) GoToMeeting - customer history and my cart favs Steve, Nick, and Eric stuff. (12-12:30) Bryan - phone call projects and printing with Javascript (1-1:30)conference call with Bryan and Alan (1:30-3:45) Zoom - Russell, personal look and feel settings and then switching to data uploads.

	Shop 4962		Virtual Post-It Note	1/12/2017	Hours (9-12) GoToMeeting - customer history and my cart favs Steve, Nick, and Eric stuff. (12-12:30) Bryan - phone call projects and printing with Javascript (1-1:30)conference call with Bryan and Alan (1:30-3:45) Zoom - Russell, personal look and feel settings and then switching to data uploads.

	Shop 2147		Calvin Time	1/12/2017

	Shop 2111		Russell time	1/12/2017

	Shop 2184		Prep for an outing with my son	1/12/2017

	Shop 2149		Brandon out of the office All day	1/13/2017

	Shop 4963		Virtual Post-It Note	1/13/2017	(1-4 pm) At Beaver working on changes to stuff at Beaver Mountain. Flex grid permissions, horizontal view, custom verbage, passing dates for adding new lessons, testing and pushing live.

	Shop 2197		Working with Russell and Steve on a data migration project	1/14/2017	On an all day GoToMeeting session with Russell and Steve going over the process of doing a data migration process from Excel to live data. We recorded a big portion of it. We didn't know how long it would be and we ran into multiple little hiccups and snags but finally got about 3/4 of the way done with everything. Small lunch period but other than that we were on the meeting all day long. As a note, when cleaning up this entry.... Expand on the upload and migration process. Also, when I get a chance, maybe upload the tick list doc and the movie to media/content.

	Shop 2152		Adilas Time	1/16/2017	On a GoToMeeting session with Alan and Steve. We helped Steve make some progress on a session cart counter app. This is where it takes a known package (sub inventory stuff) and counts the values in the cart as well as the known physical quantity. It than helps the user know if they have exceeded a package capacity even before it submits the values to the invoice line items table. Kinda a quantity pre-check type feature. I spent some time working on emails, recording expenses, and trying to catch-up. I then worked on the big customer/patient data migration project for a client in California. Working through the rest of the custom logic and starting to roll into the testing phase. I had to answer some random questions here and there and just keep making progress. As the meeting went on, we were all working on our own little projects. I ended up talking to a couple of developers during the session as well. On the phone with Russell and Bryan and then Steve for a little bit.

	Shop 2195		Expo quote & C4Ever	1/16/2017	On a GoToMeeting session with Bryan. We looked over his notes on the Expo payment solution project. We talked lightly about that and then touched base on a couple of other projects and issues.

	Shop 2162		Calvin Time	1/16/2017	On the phone with Calvin touching base. We talked about new API socket connections and also back-up plans and recovery plans. There is another company that loss a lot of data and our clients are trying to make sure we have everything in order. It is amazing to see how valuable the data part of the puzzle is.

	Shop 2137		Shawn Time	1/16/2017	On a GoToMeeting session with Shawn. We spent the time looking around and taking notes on the customer queue section. We are planning on redoing the queue and making it corporation specific. We did some practice runs, sample code stuff, and I helped Shawn get some ideas and direction. Basically getting familiar with the turf and/or terrain. We made some plans to touch in two days and then again the next day after that.

	Shop 2193		Black Box Project/ Metrc and Leaf Data	1/16/2017	On a GoToMeeting session with Nick and Steve. Nick had some stuff to sign-off, but we ended up working more on the big customer import stuff. I was doing that while Steve was working on his own projects. Nick was doing his stuff while Steve and talked about conversions, data migration, and progression of system and tools.

	Shop 2201		Migrating patient data for a client	1/16/2017	Working on a migration project of 26,000+ customer/patient records for a client. Quite extensive, it included tons of custom code, custom mappings, flex grid tie-ins, additional contacts, log notes, etc. We also had to debug and/or comb the data (lots of user errors). Tons of clicking.

	Shop 2153		Adilas Time	1/17/2017

	Shop 2198		Elevele: sort	1/17/2017

	Shop 5037		Virtual Post-It Note	1/17/2017	-You can choose! So, do it! Make the things happen that you want. -You cna't barrow time like you can money . . . -What is your level? Stick to it. -Put a load on that you can manage. -Learn to say "no". Nope and i'm Sorry, not right now,ect. -What do we want to be as a company? Big. Small. Medium. -Too many things going . . . life, work, hobbies, ect. -"I've wanted out for years" . . . Am I planning something? What is it? Am I secretly working towards something? Patterns and justifcation. -Talk to the big guy upstairs - he knows. -What do I want to do in order to stay? -Instead of . . . "I want out" . . . what if it was "I want in" . . . there is what that would look like. -What would you do to change it? -What is the ideal? -Find the balance -maintenance -building -dreaming -helping others training -Virtually burn it down -If it all died or got destroyed, where would I be? Am I ok with that? Am I ok? -Time allocations Adilas time me time dev time training time fun team - who are they? -Cut down but keep somebody close - you need some help. -Abundant model . . . lots of good choices - just like Sunday Dinner. -It is okay to make tough choices . . . Do it and stick to it . . HOURS - ( 9:00 - 12:00 ) Steve and I custom v.s. standard, new projects v.s. older, maintenance v.s. building, etc. -Working on a data migration between servers for customers. - ( 12:00 - 1:15 ) Bryan and planning out menu boards - brainstorming and trying to help him. - ( 1:30 - 3:30 ) Russell and a session on changes and choices. - ( 4:00 - 5:15 ) Meeting with Dave Forbis down town logan. Talking about developers, plans, and projects. 30 miles.

	Shop 2163		Calvin Time	1/17/2017

	Shop 2112		Russell time	1/17/2017

	Shop 2190		Meeting with Dave in town	1/17/2017	Setting up some bank stuff with Dave - in town.

	Shop 2154		Adilas Time	1/18/2017	On a GoToMeeting session with Alan and Steve. We ended up migrating some of the data that was needed between corps. This was a corp to corp customer migration. We set it up with a simple web form with some basic info and then ran it based off of first letters of last names. Pretty slick. Alan and I then worked on a custom black box option for the submit cart page. This was one corporation doing a normal invoice and then auto passing invoice data to another adilas site. Basically, a small internal API type transaction. We coded it and used primarily existing functions and methods. It looked pretty clean and straight forward. Cool stuff and a nice little custom wire job. Towards the end, Steve and Alan were working on a cross-corp gram control piece and how the system would feed in data from multiple corps at the same time.

	Shop 2204		FTP setup	1/18/2017	Quick meeting with Bryan to go over some server updates and where things are at. He came onto the GoToMeeting and we just chatted from there. He did recommend that we upgrade the older servers into more updated hardware. We briefly talked about what that would take and a small plan. No real decisions were made.

	Shop 2164		Calvin Time	1/18/2017	On a phone call with Calvin. We were talking about data back-up options. Calvin's client is interested in a physical back-up solution. We didn't spend a ton of time on this, but here are some rough notes. - We could create a service that is attached to adilas. - It would be billed by us and then a portion given back to Calvin. - We could permission it out. - The user could make a request. We could get an email or text number to let them know that it was ready. This would be done on the web. - In the background, Calvin's auto process tool could run the full back-up. Save the SQL files, run some encryption, and create a zip file. - We could then notify the user that the file is ready. We would also need to let them know that the file has a life span of say 24 hours. - Then when they pull down the zip file, we could use a special Calvin (de-crypter tool) tool to unzip and decrypt the SQL file. Anyways, that is just the quick and the dirty of it. We will still need to do more testing, planning, and making decisions.

	Shop 2199		Meeting with Shawn	1/18/2017	On a GoToMeeting session with Shawn. We were both on the meeting but working on differnet projects. Shawn was working on splitting up the customer queue records and I was recording notes and updating elements of time.

	Shop 2203		Working on the mini system for the city of Richmond California	1/18/2017	On a GoToMeeting session with Steve. We started out and I was fixing a small bug dealing with sub inventory. He was working on a custom process for the city of Richmond, California. Once I got my stuff done, we worked together to make a super simple interface that allows for a person to be searched by their driver's license. Once found, they go to a simple page where they enter a numeric value and click submit. It is that simple. We spent the rest of the session building out those smaller little pieces. Good stuff. As a fun side note, we were talking about Alan and his skill level. Pretty awesome. He will be really good.

	Shop 2155		Adilas Time	1/19/2017	On a GoToMeeting session with Nick and Steve. The day started out by Nick and Steve getting some updates on some projects that they are working on for state API socket connections. Steve then suggested that I have Nick help me out with a black box update and clean-up project. I lined Nick out on the project and helped him get started. After that, I spent most of the rest of the session doing a vendor and item (product) migration for a client. Lots of combing data and prepping things. I had to be logged into their site to get all of the database tie-in id numbers and such. Mostly a general work session for all of us.

	Shop 2205		Questions on projects	1/19/2017	On a GoToMeeting session with Bryan. We were looking into some of his existing projects. We bounced between 3 or 4 of them and had some light back and forth on progress, hang-ups, needs, and concerns. We also got on a conference call with another developer to talk about data requirements and needs. Busy times.

	Shop 2165		Working with Steve	1/19/2017	On a GoToMeeting session with Steve going over his new mini system that he is setting up to help with city requirements for gram tracking. This is his first little mini wire job of sorts. Pretty cool. He has a super simple interface where the user swipes a driver's license (or looks one up). It then either shows search results, add new options, or goes direct to the mini add grams page. All of the pages interact and it is super simple. Once the new value is entered, it records the history per client and creates a mini invoice behind the scenes. Good stuff. My job was just helping him with some light navigation and small logic tweaks. He is doing all of this all by himself. His skills are really getting better and better. Yee Haw.

	Shop 2113		Russell time	1/19/2017	On a Zoom session with Russell. We spent the whole time going over his database layout and plan for the AFB blog. Tons of settings, custom permission (for both employee/users and for customers - that is cool), look and feel stuff, navigation links, and tons of toggle on/off type features. It is looking pretty cool.

	Shop 2200		Meeting with Shawn	1/19/2017	Spent the first 1/2 hour working on updating notes and recording details of the other meetings and sessions today. I then started back in the product (items) migration stuff.

	Shop 2207		Product and customer migration	1/19/2017	Finished up a product migration for a client. Clicked through and migrated over 600+ items from over 40 vendors. Also prepped and finished a customer import of over 30,000+ customers/patients for a different client. All new records are live on the correct server. As a side note, most of the item stuff was done earlier today and the customer import was super clean data with almost no custom mapping and custom code. Super clean data and straight forward. That helps a ton.

	Shop 2150		Brandon out of the office All day	1/20/2017

	Shop 2209		Going over the customer queue project with Shawn	1/21/2017	On a GoToMeeting session with Shawn. We looked at the files he has been prepping for the customer queue project. We passed some files back and forth and made a plan for the coming week to test and push on the project. Shawn has done a bunch of database prep stuff to get us started.

	Shop 2210		Emails	1/21/2017	Emails and checking things out.

	Shop 2221		Corp to corp migration project	1/23/2017	Up super early migrating data between corporations on the data 1 box. I had to physically login to both the source (master) account and the receiving (secondary) accounts. Once on those systems, I used existing tools and physically added customer types, part categories, and flex grid titles and custom fields. I then digitally migrated all of the vendors, all parts (items), all customers (patients), and all associated flex grid tie-ins. I was bouncing between being logged onto the live server (remote desktop), new code pages (server-side scripting stuff), and physically being logged into the corporation sites (existing adilas tools). By mixing the different pieces, I was able to migrate all of the data that was needed. It worked out pretty slick. Having said that, I know if there were tons and tons of data, we would need a different tool. Anyways, kinda a fun success story on migrating data between corps and quickly doing thousands and thousands of records. Good stuff.

	Shop 2156		Adilas Time	1/23/2017	On a GoToMeeting session with Steve and Alan. Steve was talking about using QR codes and playing a simple smoke and mirror options for scanning subs, child items, and even parent items. The gist of the conversation was dealing with we already have the wiring built out to scan ~123 and it will add that item from package 123. Piece of cake. All Steve was talking about was showing the users what they want to see and then using a super simple QR code to do the lifting. Basically, they, the users, get to see what they want. That makes them happy. We then use the QR code to store what we need and keep it really simple. All of the real data is stored on the sub and/or on the my cart favorite button. We just help them out and both parties feel like they got what they need. Just some small notes... Maybe expand this. The later half of the session was working with Alan and looking over some new code and logic that he has for the Metrc state API. We covered some of the new functions, did some testing, and looked over the other report pages. Alan was driving and I was the second set of eyes.

	Shop 2211		Alan Time	1/23/2017	On a GoToMeeting session with Alan talking about the C4Ever cash management stuff. Steve chimed in, Bryan chimed in, and we did some drawing to illustrate what the goal was and where we are headed. Some of what we need to do is build out our own interface that talks directly with the BNR (bank note recycler - bill or money collector).

	Shop 2219		ICS mySQL	1/23/2017	On a GoToMeeting session with Bryan. We went over multiple different projects. Some of it was just direction and talking and some of it was getting down deep in the technical stuff. Good session and we covered a lot of ground.

	Shop 2138		SHAWN	1/23/2017	On a GoToMeeting session with Shawn. We were both working on our own projects. I was working on his code of splitting up the customer queue database table. I was going over the migration file and updating database code to talk to the new tables. Shawn was working on other projects and payroll stuff.

	Shop 2157		Adilas Time	1/24/2017	On a GoToMeeting session with Steve. More notes on the QR codes. - They want to be able to put their own SKU or item number on the label. - Steve is allowing them to go to an open package and then populate what they are wanting... (mini preset conversions). They have preset multipliers (0.7grams, 1gram, 3.5grams, etc.). They can then enter amounts and watch to see what the total is. - Steve is recording the number of the presets as a sub attribute held on the sub entry itself. He can then check against those numbers to see how much has been sold and what is still available. - Instead of going subs and sub attributes... what if we break more into a traditional model (one-to-many) and start going vertical vs. horizontal. Create a physical grandchild id, record the weight, the cost, the price, how many made, how many sold, special description, etc. Example: Say PO #27, Line # 4, Sub ~15, Conversion `77 (`=back tick or #=pound). We could then use a QR code that was something like: ~15`77 or ~15#77. - Keep going vertical in a one to many relationship. - On pricing tiers and conversion templates... make these their own free roaming tables. We could then attach them to any sub templates. They exist outside (so we don't have to remake them over and over). We could then attach them as needed. - Conversions will need rules, setup options, verbage, and conversions that allow back and forth traffic. Steve was calling conversions - never land - off in the clouds. - We need to track cart status, quote status, and reserved status. See attached for a simple drawing. Here are some notes. The ~15 is the sub. It is in grams. The `77 and `78 are conversions. The m is for made, the s is for sold, the p is for price, the q is quantity (in grams - same as the parent), a visual unit of measure, and possible pricing rules. Along with that, we also talked about tracking the cart status, quote status, and a new one called reserved (who else if asking for it) status. - We really need to get into sub categories before we get into smart cart logic. This will then make it easier for sales, promotions, campaigns, etc. - How will loyalty points and coupons play into this model? Build the whole system out and let the computer help solve the problems. The loyalty points need to be as automatic as the pricing tiers. Think all roads lead to the same virtual outcome. Mix and blend as needed. - The end goal is the employees scan the item and it knows how much, what, where, and when... Lots of one to many relationships. - Along with this... we will eventually need to look into custom labels. Track _x and _y coordinates, custom verbage, auto feeds, dynamic mapping, etc. Logos, backgrounds, symbols, hard coded stuff, conversion stuff, and pricing tiers. - Conversion land... You may be required to label with a QR code so we could track things back down. We may need to nail down conversions before we get into custom labels. - This may bring things into the 3D world building level. _x = time, _y = resources, and _z = stacking and layering. Conversions and labels might be part of the _z level or Z axis. - We are also seeing more need to track things via RFID tag and other digital models. - Doing conversions... we still need to figure out how to show this on an invoice, quote, and/or cart. We still may need to get into more smoke and mirrors (hidden fields, hidden lines, visual quantities vs actual quantities, etc.). We have lots of other brainstorming ideas and notes on this. Check here in the shop, in adilas, and in the adilas university. - On a different note... What about a cash drawer reconciler? We could add a new placeholder inside the cart struct and populate it with some kind of setting or something. Tie it to the login. It will change on a daily basis. We would then need to look at a way of recording this on the deposit or invoice payment level. We may also have some options based off of users, banks, and other things. This gets into sub locations or more Z axis layering and stacking. - tie the deposits to the drawers. This could also include over and short options if off. - small idea on the cart... if you need drawer management, maybe have a watcher on the view cart page that prompts for a who are you and what drawer. We could keep some of this stuff in the session scope so we don't have to prompt each day. Another option might be to have an assignment where a drawer could be assigned to one or more users per day. Kind of a management tool. If yes, it could look it up and record the values based off of the management tool.

	Shop 2212		Alan Time	1/24/2017	Alan was on the GoToMeeting session but we didn't have much to work on. Just touched base.

	Shop 5038		Virtual Post-It Note	1/24/2017	-Meeting with Steve, on corp-wide settings add one for subs only ( part status ) default to subs only. -9r_sub_price_aty

	Shop 2167		Calvin Time	1/24/2017	Phone call and GoToMeeting session with Calvin and Steve. We talked on the phone and went over things and then came back to the computer. Steve was explaining to Calvin what the problem was and/or is for one of our clients. They are running the system similar to a short order cook that the person in the front gets the order and then has the person in the back fill the order. Things get kinda crazy building the cart and then verifying what is actually going out the door. Chain of custody is really important. Currently we are using the QR codes to record the sub id, the price, and the quantity. This is helping but we need to keep tightening things down. The problem comes in when they start breaking down packages but they really don't add new items. That means that some of the smaller pieces are somewhat floating in the background. They are looking to record some details but not go clear to the mini manufacturing model of a full build PO. Basically, they are skipping some steps because it takes too long. One of the goals is... At any given point we could see where the inventory is at... is it on the shelf, in the cart, quoted, sold, destroyed, unknown, etc. We showed Calvin what we have and what we are planning. Our conversation today was mostly just putting the project out there and letting him know what we are looking for. He said that he would talk with the client and get back with us on Thursday to do more planning and figure out what we want to do. See attached for a video recording of part of the session. Steve is currently doing some light conversion stuff. He has built a page that takes a sub package and allows it to be broken down into smaller pieces. He has named sections (virtual units of measure such as eighths, cones, grams, shake, etc.), we then allows for a quantity, a weight and/or how much of the main item (at the main item unit of measure), and then a price. He then records it on the subs attributes for the child package. We are using QR codes and putting the sub id, the quantity, and the price into the QR code. Part of the process is showing the total quantity that is available. This allows the person to virtually work backwards. If we used a database table and recorded all of the actions. We could take a package and then allow it to be broken down into smaller pieces without doing a full build. Then on the QR code, we could tell that it came from sub or child ~25 and conversion `33 (back tick sign). We could then look-up tons of info on the two different pieces. Package ~25 could tell us batch numbers, costs, parent details, sub attributes, etc. Then conversion `33 could tell us the virtual unit of measure, the real quantity, the factor or fake quantity (show quantity), the price, and how many of these there are. On a new table for tracking what is in inventory, queued up, in the shopping cart, in other carts, and what has physically gone out the door. Is this daily? Is this per corp? How do we clean up things?

	Shop 2114		Russell time	1/24/2017	On a Zoom session with Russell. We went over some Git commands (version control software). Russell made a small spreadsheet to help show flow and what not. That might be a good thing for other developers. We then started into some top level planning for the AFB blog. We setup new branches, created folders, and started into the process of setting up a template to make the thing start working. This was day one on the AFB blog project actually doing real code stuff. Up until this time, most of the work was mock-ups, planning, and concepting. Good stuff.

	Shop 2208		SHAWN	1/24/2017	On a GoToMeeting with Shawn. We were working on our own projects. I was working through the code to split the customer queue table. Going through pages and code changes made by Shawn. Kinda like a giant code sign-off and work session. Shawn's goal was to help prep things, not get the project fully done and tested. That is a different logic path than we normal go with, but I think it will work. Good stuff. Spent the last hour building an update routine to help with live migration and possible things that slip under the cracks. This is part of the database update page.

	Shop 2222		Customer queue prep	1/24/2017	Building a prep file to help with just in time migration. We will be running a huge update while users will be on the servers. The special update will help check for add/edit options for yesterday's data and today's data. That way, we can migrate what we can and then at the last second, make sure all is updated and tight.

	Shop 2223		Migration party with Shawn	1/24/2017	On a GoToMeeting session with Shawn. He was clicking and migrating customer queue records from a big shared table to the new corp-specific tables. Meanwhile, I was working on a customer data upload for a new client. Tons of clicking. After I got finished, I helped Shawn migrate the rest of the customer queue data. We were non-stop clicking from 9 pm to 1:30 am. That's tons of clicks no mater what way you split it up. Pretty crazy. All files and database tables should be good to go.

	Shop 2158		Adilas Time	1/25/2017	On a GoToMeeting session with Steve and Danny. We started to rework the bulk print labels pages from the shopping cart. Part way through, my power went off so I lost the GoToMeeting session. I kept working on things trying to get things cleaned up.

	Shop 2218		ICS mySQL	1/25/2017	On a GoToMeeting session with Bryan. We were working on building a 3rd party API socket for Full Circle. Small light direction and such.

	Shop 2168		General	1/25/2017	Working with Steve over the GoToMeeting session. More work on the print bulk cart labels. He had a couple small questions dealing with looking up subs and sub attributes for sub packages.

	Shop 2232		SHAWN	1/25/2017	On a GoToMeeting session with Shawn. He was getting the Iowa state tax withholding stuff ready and I was working on the bulk print cart labels. We then got his new Iowa payroll files merged in and pushed up to the master branch. We pushed files live, ran database updates, and Shawn did some live testing.

	Shop 2213		General	1/25/2017	On a GoToMeeting session. Mostly working by myself on bug fixes and other random to do list things. Paying bills, doing email, and helping Shawn with a small bug for Iowa payroll and withholdings.

	Shop 2159		Adilas Time	1/26/2017	On a GoToMeeting session with Steve and Nick. We started going over some data import stuff. Nick and Steve then did a small session testing some Leaf Data API connections and pages. I gathered up some of the old business and education bios that we did for Adilas (back in the day) and sent them to Steve. He needed access to them for something. While Steve and Nick were working, I was uploading video recordings and such. We had a small server outage and were scrambling to get things back up. The rest of the time was used doing little random things.

	Shop 2234		printing invoices	1/26/2017	Bryan joined the GoToMeeting session and we talked about his printing options for mini invoices. His current projects requires him to save the invoices as a PDF and then auto print them on the fly. We went over some code and I gave him some new places to look for somewhat similar type logic and code samples.

	Shop 2169		Calvin Time	1/26/2017

	Shop 2115		Russell time	1/26/2017	On a Zoom session with Russell. We spent most of the session getting the underlying infrastructure in place for his blog project. This was stuff like starting pages, black box stuff, error messages, session scope variables, and entrance portals. Good work session. We did run into a couple small snags but were able to work through things. I got kinda frustrated when we were getting some unknown errors. We couldn't figure out what was going on and why it was erring out. We took a break and then came back to it. Sometimes that really helps the mind and the body to take a break.

	Shop 2214		Alan Time	1/26/2017

	Shop 2220		Migration of items and vendors	1/26/2017	Nick and I were on a GoToMeeting. We worked on a vendor migration project. Once we finished that, we switched over and did a part number or item migration for the same company. This was a small training session to help Nick learn how to do data migrations. We have had a lot of data migration projects lately. Good session. We finished both the vendor and items migration.

	Shop 2271		General	1/26/2017	Recording notes from the day and working on a client/patient migration project. Finished up a digital upload for a client. Uploaded over 6,000+ customer/patient records to the data 6 server. Invoiced the client.

	Shop 2151		Brandon out of the office All day	1/27/2017

	Shop 2272		Working on a product migration	1/28/2017	Working on a product and vendor migration project. This one was a little bit different due to the fact we had already migrated both the vendors and items to another corporation. We then had to reuse the existing data and flip the id numbers so that it would work with the new corporation. Kinda an advanced flip flop of sorts.

	Shop 2160		Adilas Time	1/30/2017	On a GoToMeeting session with Steve and Alan. We were mostly working on our own projects for the whole session. We chatted back and forth and got some to do list stuff done. I worked on some small code tweaks to the default search options from within the shopping cart. I also did some emails and light tech support. I ended the session working on the bulk print labels pages and section. That piece still needs some work.

	Shop 2273		Full circle API	1/30/2017	On a GoToMeeting session with Bryan. He had a question on how to get some custom sales data for the Full Circle guys. We went in and looked at his stuff and then spent the rest of the session building a little mini page to help him pull and format the data that he was looking for. See attached for the sample code we built to pull and format the data.

	Shop 2170		Calvin Time	1/30/2017

	Shop 2139		Shawn Time	1/30/2017	On a GoToMeeting session with Shawn. Looking into a custom payroll request for Washington. Small session just touching base and getting a game plan.

	Shop 2233		J&J Trailers - Data Migration	1/30/2017	I was going to look into a request from J&J Trailers to pull in some data from J&J Motorsports. Ran out of time. This did not happen today.

	Shop 2215		Alan Time	1/30/2017	On a GoToMeeting session with Alan and then Bryan. Worked with Alan to show him some older code for interacting with the underlying Java engine. We also went over existing code that was done for C4Ever, the BNR (bank note recycler - cash handling machine), and the Kiosk Simple JavaScript integration that we had built out. That project is circling back around. I helped Bryan out with some small questions as well. In between times, I was working on the logic for the bulk print cart labels page. Spent a lot of time tightening things up and running some tests. Good little work session.

	Shop 2279		Digital Migration	1/30/2017	Finished up the digital migration for a client. They had two corps that needed the same vendors and products uploaded for use. That seems easy but it still took hours and hours as each corporation has different primary keys and different id numbers in the database for vendor/payees, part categories, locations, etc. Finished all migration tasks and invoiced the client.

	Shop 2161		Adilas Time	1/31/2017	On a GoToMeeting session with Nick and Steve. The first two hours were spent on a brainstorming session between Steve and Brandon. Lots of talk on monitoring and capturing the size of the business footprints that each business is leaving. The goal was somewhat of a quantified price increase type discussion. As the discussion continued, we got into a big conversation about our model, what size of company do we want to be, who are the players, how do things work, what about 3rd parties, what other dependent parts are there, etc. Tons of fun questions. See attached for some notes that were taken from the meeting while we were talking. Expand and put some of the key points here in searchable form... :) Spent some time working on the bulk print cart labels pages. Doing some testing and trying to get things in order.

	Shop 2281		API	1/31/2017	On a GoToMeeting session with Bryan. We were looking into a possible printing option for queuing up local print jobs and submitting them via an API socket connect. Bryan was doing most of the work. I was just a second pair of eyes and making comments. I got a call from Calvin so Bryan finished up and then bailed off the session. I'm not sure of the status of what he was working on. I was on the other line.

	Shop 2171		Calvin Time	1/31/2017	On a phone call with Calvin. Talking about quotes and doing custom code work. We also talked about how hard it is to hit a moving target as a developer. After that, we got on a Zoom session and I showed him some cool debugging features for the web/test_adilas_api_calls.cfm page. We went through a couple of things and played around. Good session.

	Shop 2116		Russell time	1/31/2017	On a Zoom session with Russell. He showed me some of the new progress he is making with the AFB blog and what not. It is looking good. On a side note, we used to add 5-10 new settings at a time. Russell is adding hundreds and hundreds of new settings each time. Pretty crazy. We pushed some code around and switched gears. I pulled down his branch and we started in on another part of the project. As we got in to it, we ended up on a lengthy conversation about how we going to structure things and some simple rules about adding new settings and database fields to existing tables. We have to figure out what we want. Sometimes things happen so quickly, you almost feel powerless to effect a change. Or sometimes you get so overwhelmed, it is hard to make a choice on what is happening in the future. You almost feel locked down and unable to make a decision. Very interesting. Long story made short, we bought some time and I told Russell that I would talk to Steve about things. All is well.

	Shop 2216		Alan Time	1/31/2017	Recording notes from the day. Life keeps right on going just as fast as ever. Hang on...

What's New

Products

Find Us