all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
| Media Name | File Type | Date | Description | |
| locking_and_conversions.xlsx | Doc/Spreadsheet | 2/28/2017 | MS Excel document with lots of notes and such on table locking and row locking. We also talked about some known issues with mini conversions and such. This was a brainstorming session between Brandon, Steve, and Calvin. | |
|
Notes:
|
|
On a GoToMeeting session with Steve. We widened out the sub inventory attribute values field. This allows the users to put as much data as needed in a custom built drop-down menu. We went from a max of 255 characters to 65,000 max characters. We often call this unlimited (even through it really does have a limit, it hardly ever gets reached). We met with Calvin at 11 am to go over plans for the mini conversions and transactional data for the cart and breaking things apart. - Communication between us (adilas and adilas developers) and our clients. This is huge. Projects are deep and take tons of time. We need to communicate things as they happen and progress. This is a constant battle. - Agendas (theirs and ours), this makes it tough if they are not communicated. Establishing an actual project scope and requirements of the project is a big deal. Otherwise, their ideas and conception of the product may be multiple projects all combined together. - QR codes and special barcoding options - going clear to a mini conversion level. This is more than just the codes themselves, it deals with sub inventory packages, mini conversions, etc. - We are still having struggles with clients not wanting to pay for new features. They just expect us to pick up the bill. They figure, if we are going to make it available for all of our clients, they shouldn't have to pay for it. We need to help educate our clients on how things work and how much they gain from a communal watering hole of sorts. It is like a piggy-back style of development vs. a standalone development cycle. - We talked about some pricing things. Calvin's rate is $100/hour. We talked about some possible things and ways to work out a deal. We can't afford him at the $100/hour rate. We talked about a discounted rate, trading for leads, trading for other products, and even introducing him into the reoccurring revenue sharing idea and concept. - Let's plan this project out and come up with a price tag that is agreeable for both parties. - We also briefly talked about some of Calvin's other tools. Such as Gmext, FTP stuff, MySQL editors, and other projects. - Calvin likes to think in code... Instead of just concepting on paper, he thinks in code... Where is it going to end up? - Linking things... every child has a parent and so on. Every mini conversion has a sub (child) and a parent (main item). - We talked about locking tables and rows. This is dealing with the inventory state in time... such as made, quoted, in the cart, requested, etc. We need to be able to lock and keep those records tight... The problem comes in when multiple parties are trying to access the same record at the same time. We need to form a line and/or a queue of sorts. - We went into MS Excel and did some sample table building. See attached for some additional notes and known issues. |