all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||
|
|
|
Green
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
I met with Russell for a couple hours today. Part of the discussion was dealing with the project manager and the employee timeclock applications. We talked a lot about tracking sub details of both time and space (organization). These are a list of a few of the topics that had some weight: - Subs of subs - be able to stack and inter-join - Tags - quick way of marking - Colors - visual way to organize - Phases - what states or statuses are needed - how do they change - Locations and sub locations - what movement or flow is needed to track the where - Categories, groups, & types - what groupings are used and how are things organized - Flags - what is special or needs to be noted about different things - Levels, order, priority, & position - how and where are things organized - up/down, back/front, left/right, etc. - Style/CSS - what styles are applied and why - Icons and images - how can we represent different groups, flags, tags, categories, levels, etc. - Settings, permissions, & custom - who gets access and what are the rules, defaults, and the mix or combination - JSON or database - how and what do we store? - quick look-up and reports or flexible random mix or a combination of both Anyways, I think it is interesting that it come back to story telling and catching the who, what, where, when, how long, how much, and the why. Those are really simple terms but seem to blossom and expand without end. Also by way of a note, these values need to be ready to be applied to any of the main player groups. These values will be native to elements of time, but also need to be able to be applied to things such as invoices, customers, PO's, deposits, inventory items, stock/units, expenses, users, vendors, balance sheet items, quotes, and other elements of time. They may also need a way for the main player group or individual item to hold the last known value as part of the data and story. As a reference, think of the way the action status logs are done and how the main element of time holds the last known status. That makes it easy to search the main based off of the sub tracking criteria. Anyways, just some notes on sub tracking... |