I will make all dictionary keys for game objectives consistent by editing the San Diego Regional MongoDB collection and changing the code.
There is also an unnecessary translation between strings in input-data.php and input.php.
I will get rid of this and ADD a similar function to potato.php to translate from dictionary keys to display names. This makes more sense because all backend keys should be consistent, while we should not rely on these keys as display names themselves.
For example, we should always use "CapBallInCenter" in the backend, not switch between "In Center Vortex" and "CapBallInCenter." In addition, if "In Center Vortex" is what we want displayed on the website, we should choose that display name independent of the key used in the backend.
This will help in implementing modularity for the game objectives.
I will make all dictionary keys for game objectives consistent by editing the San Diego Regional MongoDB collection and changing the code.
There is also an unnecessary translation between strings in input-data.php and input.php. I will get rid of this and ADD a similar function to potato.php to translate from dictionary keys to display names. This makes more sense because all backend keys should be consistent, while we should not rely on these keys as display names themselves.
For example, we should always use "CapBallInCenter" in the backend, not switch between "In Center Vortex" and "CapBallInCenter." In addition, if "In Center Vortex" is what we want displayed on the website, we should choose that display name independent of the key used in the backend.
This will help in implementing modularity for the game objectives.