all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
On the morning GoToMeeting session with Steve. Alan popped in and Steve and Alan went over transfers as I did some phone calls and tech support stuff. I showed Steve some of the stats and such from the Bear 100. Next year we want to make it better, more mobile friendly, and use it kinda like some light advertising. Idea from Steve... track our own progress on big projects like the runners in the Bear 100 race. Setup some checkpoints, list out pages, database tables, requirements, other known pieces, etc. Then show progress, estimates, start and end times, running times, etc. Don't make it to crazy but show some progress and such. Doing this would help those interested on the project as well as the developer who are working on the project. Basically a full project view or bigger overview of sorts. On API's - We talked about how the 3rd party solutions and how they compete with the normal API sockets. Currently we have a one-to-one relationship to hold assignments, on/off status, and usernames and passwords. We are seeing a need to make that into a deeper one-to-many relationship. We talked about how we have about 4 main roads coming and going, into API socket land. They are the demo road (limited), internal road, normal API socket road, and the 3rd party solution's road. We currently have one record per corp that we store and maintain at the world level. We may need additional records per user, per 3rd party solution, and per main or normal API socket connect. We even talked about building things out to a virtual permissions type level for the API sockets. This would deal with the one-to-many relationships, what roads to travel on, what methods or functions were open/closed, what sub functions or sub selections are open/available, and who gets access to use them. Along with that, Steve was talking about having a way to switch between different users/parties (think of visual views of the data subsets). It would basically, show what sockets were turned on per party (internal user or 3rd party). We were talking different words such as: views, tabs, or visual cards. Another idea that needed to be recorded was more new sub homepages. This could be things such as transfer homepage, API socket connects homepage, sub inventory homepage, mini conversion homepage, barcode homepage, RFID tag tracking homepage, special tracking account homepage, etc. Keep breaking things down into homepages, groups, types, subs, etc. Allow things to keep virtually sub dividing and/or fracturing. That seems to be the trend and matches our experience. |