all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
|||
|
|||
|
|
|
Notes:
|
|
-Make a check list for setting up a new server and/or database. That is okay to write things down. That way we don’t have to remember every little tweak. -I would really like to make some flow charts for pages, functions, and flow for the different pieces. I did this with an intern to talk about flow inside the payroll section. It was fun and helped him get his head around it much quicker. At some future point, it may be fun to animate flow or ever allow some user defined flow with the pieces. -On the server and database names…. Maybe just group everything together and call it “clusters”. Instead of saying domain, data servers, and databases… maybe just say clusters and then use the cluster name to talk about the sub pieces. Kind of general alias vs. super techy stuff. A possible naming convention might be dd-3-7 where dd = domain & database. 3 = the server # and 7 = the database number. Anyway, just an idea. (See 12/20/13 for new names.) -Use the data 1 server for existing clients that are good and solid. -Use the data 2 server for all new clients. -All of the “junk” or existing files and data will stay on the original server. Only good data and files will be moved to new servers. This doesn’t have to happen all at once. Move things as they become ready. -Setup small databases on the adilas server. Migrate that data as a group when ready. This is on a per corporation basis. Basically, we want to keep the new servers as clean as possible. -On making and naming data sources… We may use a general data source that deals on the admin level. We could use that to look-up the more corp or cluster specific databases or data sources. -On images… It may be nice to bury things a level deeper than just the corporation id number. An example might be: images/dd-3-7/corp 5 where the domain or data server are part of the naming convention. -On images… It may be good to stick the company logo inside the corporation image folder in the new structure. If we had to move anything it would all be together. -On the new code, remove all web service calls. Make the new servers even tighter and more dynamic. Basically, we’ll button up some things on the old system and then focus on the new system and new code to head where we want to go. -We may end up doing a sample API using JSON objects to help with emailing the invoices and quotes. In a nut shell, we are going to be headed more and more toward exchanging code and objects using webservices. -As a reminder… “Easy on the how, not so easy on the what.” Quote from a lady in the Box Elder School District. |