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
(3)
|
||||
| Media Name | File Type | Date | Description | |
| table_planning_for_mini_conversions.xlsx | Doc/Spreadsheet | 6/6/2017 | We were working more on the database design and concepts for the mini conversion project. Today we added part id's, store id's, and some other small tweaks. Trying to solve things on paper first, before we go to code. | |
| scratch paper_r3_sub_inventory_mini_conversions.docx | Doc/Text | 6/6/2017 | This is the main scratch page for the mini conversion project. We are using it to help us gather information and ideas. We will keep adding to it as we go. | |
| pricing_matrix_work_around_for_blum.jpg | Image/JPEG | 6/6/2017 |
This is a screen shot of how one of our clients, Blum, out of California are using their own pricing matrix using flex grid. The screen shot is of an item. It has a specific unit of measure. It hat has some flex grid assigned to it. The flex grid is a simple list of prices. The secret to the list is the associated number or position behind the scenes. Position 1 was for a full ounce, position 2 was for the 1/2 ounce, position 3 was for the 1/4 ounce, and position 4 was for the 1/8 ounce. Basically, the user would enter a quantity (weight in grams) and the system would see if it had rolled over to certain pricing thresholds. If yes, it would use the price based on hard coded values in the code so that it would use the price for the full, 1/2, 1/4, or 1/8 ounce. Pretty creative. We had Eric Tauer on the call with us. He is the developer that implemented the tie-in flex grid work around. We talked and took some other notes. See the other attachments for more details. |
|
|
Notes:
|
|
On the morning GoToMeeting session with Steve and Eric. As part of the meeting, Eric was talking about De-normalizing data and where to use and set things. He was talking about query tuning, indexing, and other performance tuning concepts. Most of this was dealing with database administrator things. - What about watchers and feeders - What if we moved away from transactional data and more into preset aggregates and daily totals per category and per location. - You can replicate and index the id's but you don't want to replicate all of the other features. That is where you join tables and look things back up when searching and displaying the data. - Eric volunteered to be the adilas DBA (database administrator)... :) - Often you have to feel the pain first and then you start going in and fixing things. - Some of the aggregates and roll-ups are for the user who wants to see all of the data in the entire database. This is often done in data warehousing for system-wide or global analytics. We spent most of the meeting talking about the mini conversion project. We made some more progress and added a number of new notes and even tweaked out our database planning spreadsheet. See attached for more info. As a side note, we talked quite a bit today about prices and the pricing model. We also talked a little bit about sub part categories and how they play into the mix. See the scratch page for more info. |