all data is live and searchable



« Back . [new search - developer's notebook] . [new search - adilas community funded projects]
Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Red
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 3/14/2016 6:26 am
 
Action Status: Completed
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 995
Template/Type: Brandon Time
Title/Caption: Brandon out of the office all day
Start Date/Time: 6/10/2016 9:00 am
End Date/Time: 6/10/2016 12:00 pm
Main Status: Active
Sorry, no photos available for this element of time.

Uploaded Media/Content & Other Files (2)
Media Name   File Type Date Description
sub_inventory_tables.xlsx   Doc/Spreadsheet 6/11/2016 Brainstorming document for database ideas for sub inventory and cost controls. It also has some ideas on parts/items and conversions.
Sub inventory.docx   Doc/Text 6/11/2016 Brainstorming document for sub inventory and cost controls. It also has some ideas on parts/items and conversions.


Notes:
On a 3 hour GoToMeeting session with Steve. We worked on a number of Steve's projects. He is working on the sub inventory stuff and update PO data for his Colorado Metrc homepage. That page helps our clients pass adilas data to the state compliance sites to help sync up the different sites.

We also went over a number of new code pieces and made a bunch of changes. We chased some bugs down and fixed a couple of other pages that he had issues on. Good work session.

We also had a good brainstorming session on packages and part/item conversions and units of measure. Here are a couple of small notes that went along with our session.

- We may want a couple of new fields on a per part or item basis. This would include fields to hold the normal sales quantity and an alternate unit of measure. Currently Steve is doing this or something like this by hijacking the weight field and the bin number or catalog page field. This is a way to do some smoke and mirrors and setup a one-to-one relationship for the items. In normal English, this means we need a show quantity, a show unit of measure, a real quantity, and a real unit of measure. For example: Say I wanted to sell 1 package which actually was 16 ounces. So, the show values would be the 1 package while the real values would be the 16 ounces. Hopefully that makes sense. Like I said, Steve already has a couple of companies doing this but hijacking other existing fields to make it happen.

- I would love to see conversions be part of a one-to-many relationship vs. a one-to-one relationship.

- Maybe think about the part categories or going up a level or so. We would love to do something along the lines of rules and assignments, similar to the my cart favorite - smart group buttons. These rules and assignments would be for both pricing matrixes and conversions.

- Help things be a factor of one. For example: 1 something equals x of this unit of measure. 1 something else equals y of this unit of measure. Keep things consistent.

- Use the template structures from part categories and sub categories. Be able to go up the chain to reduce the maintenance on the rules and assignments.

- Think inheritance or be able to break out and create your own values if needed (a child could lean on a parents rules and assignments or a child could make their own rules and assignments depending on needs).

- Think tiered pricing, tiered conversions, etc. Both will end up using some kind of rules and assignments of some kind.

- We have some other brainstorming on this same subject for sub inventory stuff. See attached for a multi page document of some of our brainstorming for the sub inventory and cost controls stuff. Some of these subjects get pretty deep.