- Tue Jan 23, 2018 12:24 am
Brodie Murdoch 1306312 wrote:I think this is a great idea although it would need to be restricted down a bit in terms of information and data going into VATSPY. At the end of the day ARTCC/VACC/Divisions do have the final say in terms on what they want and don't want to display and it should ONLY be the Director or the Airspace Operations Director of the ARTCC/VACC/Division who are allowed to introduce update and remove information and data from VATSPY per how they manage the info in their area/s unless permission has been granted from them for someone else to do it. Because the last thing that we need in someone who doesn't know how the division/VACC and who hasn't gotten permission to add information which is not based on what the specific ARTCC/VACC/Division uses.
E.g. Adding a position like a sector for enroute which is used in RL but not in VATSIM
Brodie, we're going to be taking steps with each ARTCC/VACC/FIR/Division to ensure those who are making the updates are those who are authorized to do so. It wont be a "free for all" method when it comes to updating. We will not be adding data or removing data on our own. Data will only be altered when it has been specifically requested to be altered by authorized staff of the ARTCC/VACC/FIR/Division, or is altered using an authorized account of the ARTCC/VACC/FIR/Division. The updates will be made directly by the ARTCC/VACC/FIR/Division, or, if they are unable to make the update themselves due to not understanding how the file structure works, or how to make the changes on their own, they can email us directly from their VATSIM staff email address and request the change and our staff can make the changes for them. The reasons we have an approval method is one, due to if the data is incorrectly entered, it can cause a compile error when VAT-Spy starts and the program wont function, and two, to ensure the changes are being made by authorized staff of the ARTCC/VACC/FIR/Division.
In terms of centralizing the data, Ross has mentioned this...
Ross Carlson 887155 wrote:If someone commits to maintaining the data, I will commit to updating VATSpy such that it pulls the data from the source automatically so that it is disseminated to the membership without each person having to manually download and install.
Which reading directly from his statement and expanding slightly, centralizing this data in one place, which is what we're doing, will allow Ross to update VAT-Spy and it will automatically pull these changes directly into VAT-Spy each time the application loads, meaning the user no longer has to manually seek out these updates and copy and paste them in. With the application functioning in this manner, it will require one central source location for the membership to make changes to the data it is pulling, which is what this project is taking the steps to do. I've spoken directly with Ross about this and he has agreed to work with us as the source of centralizing the data.