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: Yellow
Created By: Brandon Moore
Created Date/Time: 4/27/2015 2:46 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 3782
Template/Type: Other Documentation
Title/Caption: Brainstorming about the need to mix elements of time, sub functions, and 3D world building concepts
Start Date: 4/21/2015
Main Status: Active
click to enlarge - photo by: Brandon Moore -
click to enlarge - photo by: Brandon Moore -
click to enlarge - photo by: Brandon Moore -

Uploaded Media/Content & Other Files (3)
Media Name   File Type Date Description
20150421_113648.jpg   Image/JPEG 4/27/2015 Whiteboard session for elements of time and world building concepts. Photo 3 of 3.
20150421_113616.jpg   Image/JPEG 4/27/2015 Whiteboard session for elements of time and world building concepts. Photo 2 of 3.
20150421_113553.jpg   Image/JPEG 4/27/2015 Whiteboard session for elements of time and world building concepts. Photo 1 of 3.


Notes:
These are some whiteboard brainstorming pictures of a brainstorming session between Brandon Moore and Calvin Chipman. We were talking about how relationships, inside of adilas, are created and/or manufactured. The subject covered was dealing with how we want to help to virtually adopt different players and player groups inside of adilas to the sub functions of elements of time and space. The subject was somewhat on the topic of data glue.

We covered main application types (system player groups), main id numbers (how they connect), and what natural options and relationships already exist. We figured that at the most basic level, we could use the following fields to connect any piece to any other piece.
  • Corp Id or World Id Number
  • App Type Id (2=Deposit, 3=Invoice, 4=PO, 5=Expense/Receipt, 6=Balance Sheet Item, 7=Stock/Unit, 8=Customer, 9=Vendor/Payee, 10=Employee, 11=Part, 12=Element of Time, 13=Quote)
  • Main Id - What is the corresponding main id number to create the main id and app type id combo? These combos deal at the data level for the data item. For example: App type 2 and deposit number 50. That makes a specific named deposit. Or app type 3 and invoice number 700. That creates an invoice entity or individual. Or app type 11 and part id number 1000. This would be how the system would talk to and/or communicate with a part number or item (general inventory item).
  • Sub Id - Optional. This would be a sub id number if we need to connect to a sub. If not, it would be left at 0.
  • Table Name - This would be a string or text value that would help us know what table we were talking about. This helps us possibly connect an unlimited number of subs or sub tables.
The other fun thing about this brainstorming session was the fact that we listed out a number of the subs of each player group as well as listed out some of the sub functions of time. The sub functions of time are still somewhat new and a budding subject inside of adilas.

This brainstorming session also mixed a little bit of 3D world building with sub functions of time, permissions, settings, photos and scans, locations (stacked model), and with media/content (files).

By the time we were done, we were talking about a thing called the application flex grid (connecting different worlds or software applications together) and real in-line extensions (possible ways of extending any table or column in the entire database). Good session.