Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Blue
Created By: Shannon Scoffield
Created Date/Time: 8/13/2013 6:34 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 1195
Template/Type: Daily Ideas
Title/Caption: Daily Ideas
Start Date: 4/20/2013
Main Status: Active

click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
 


Notes:
-Thinking about “roll call”… I don’t even know if this is possible, but would happen if you had one table just for roll call? This would be what flag, what date, what checkpoint, what status? This is just an idea but if we had everything in one place, it sure would make reporting easier. Currently we have all of the pieces (mostly) but they are all continued in-line or on tons of different tables.
-This idea is somewhat related to some topics back in October and November of 2010. We have tons of brainstorming on watchers, feeders, standalone declarations, etc. A global “roll call” table may end up being part of those options.
-In a nut shell – things happen every day (changing, turning, staying, coming, going, becoming, etc.) Our goal is where is it at (the objects and/or data) when the day closes? Almost like a “snapshot” or daily summary. If more details are needed, we could always go back and check on the objects history.
-The one (or more) problems with this deal with changes and going back in time. This is especially true if one value is related to another value. You end up getting a cause and effect chain of events.
-One way to solve this is to put each corporation on its own mini adilas and then look-up all of details, dates, and flags on the fly. We could speed things up by using numeric dates, smaller tables, and using global watchers that help things stay contained. We have a thing called the “ice down” date. That could help us lock things down and then don’t allow any changes. If a change is needed, we could back up the ice down date and then record changes. That date could be a backward compatible border or boundary of sorts. Basically, a no one goes past here unless the ice down date is backed up.
-Another thought keeps playing through my head… what if you still kept – all data is live and searchable – but added a lock or sorts. You still want all of the data but you also don’t want everything to be flexible all the time. Maybe once you lock it down, no one gets to touch, unless the lock down (ice down) date gets pushed back. Everything is still there and plays a part but it prevents tampering and changing once it gets perfectly locked down.
-Maybe think about formulas in a spreadsheet… But be able to lock them down…