all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
-Using in-line extensions will give us the flexibility of Microsoft Excel with the power of a relational database and cloud based infrastructure. That will be awesome. -The key pieces are: 1. Centralize the data 2. Be able to collect and store the data 3. How to interact with the data 3.1. Interface 3.2. Flow & Processes 3.3. Analytics & Reporting 3.4. BI (Business Intelligence) & Big Data Space & Time Brainstorming: -Brainstorming on project phases and sub locations... Theses are subs of elements of time (and space). These pieces position or arrange how and where and what is happening or has happened or will happen. I think that we need to keep them subs or functions of time and space. However, I also think that we need to record the current state or status on the main. This allows it to be searched and referenced quicker. -We already store the action status value on the main elements of time table. These sub locations or projects phases would be the same way. We would hold an unlimited list of sub locations or project phases on or in the sub tables... but we would also make the current sub location or current project phase be part of the main element of time. -I'm really excited to see “space” or organization of time start playing into the mix. This is exciting! -If we are talking about subs showing up on the main individual data items or data objects, there are other pieces that want to be counted or accounted for. For example: Say a person was adding sub dates and times (virtual timecards) to a project. It sure would be nice if the total amount of time (sum of the subs) could show up on the main. All of the details are still held in the subs, but the current value becomes part of main. This is also true for things like action status logs, sub dates and times, project phases, sub locations, etc. -Elements of time and space need to be a foundational wrapper for all functionality for adilas. We already do this in a very light way. Invoices are assigned to locations and dated; PO's are assigned to locations and dates; deposits and expense/receipts are assigned to a date and one or more locations at a time. Inventory is tracked per location and by date (sometimes multiple dates). Almost everything we do has a component of space (locations and layering) and time (dates and date/time stamps). We already play this game... What if we just take it to the next level and allow the users to virtually wrap the system, the groups, and the individuals in both time and space? That would be awesome! -Time and space is ok (still works) but space and time sounds better. What about elements of space and time? -What if we add the word “space” into all of our pieces of documentation, literature, notes, quick search, etc. It may be made fun of at first but I think it could gain some ground especially if we start teaching and using those concepts together. -On the quick search – I would like options to search time or elements of time. I would also like a quick search option for space and time or elements of space and time. The space and time options could search much more and find all instances of things in both main and sub tables and database fields. If you searched space and time it could be the global adilas or all adilas searchable. -Locations and dates are a general way of saying space and time. We already knew that dates and times were important but we didn't know how deep locations or layering pieces would be (organizing your data). We've got to include space... It adds to and increases what dates and time can do by itself... It is a compound concept that needs both space and time! Think of our little assembly line graphic for our world building concepts... (Please see sketch on scan in photo gallery): -Space is how we organize over time -Pretend that the dots are checkpoints or key phases (dates/times) -Pretend that the top line is operations and the bottom line is accounting -Time goes both directions -Pretend that the vertical lines show permissions or access levels. Who gets to play at what level? -Pretend that the pods are areas or sub locations or departments (space) -In between checkpoints we have to allow some flex in the model -Lately I've been toying with the idea of a wrapper or a way to combine core concepts. I want them (core concepts) to interact and play together. I've been headed towards a wrapper of time (see entries from 5/22/14 and 6/3/14 in adilas university – developer's notebook). Anyway, my new direction is a wrapper or foundation of both space and time. You've got to have them both. -The bottom level (number 10) of the world building concepts currently says... Run all levels over “Time”. I think it needs to read – Run all levels through “Space” and “Time”. The word “through” may be a good general term for a wrapper, media, medium, or channel. We'll try that and see how it goes. |