#6138 standardize case on GA custom tool type NEEDS MONGO CMD
Top GA custom events are:
Discussion Wiki Tickets blog SVN wiki Git git profile Blog
We need to stop having two capitalizations for blog and git, maybe more. We should use the most popular (e.g. don't just lowercase, that'd cause disconnect with historical values for e.g. Discussion)
IIRC there is GA code in both sftheme and the OSS template. OSS template doesn't need to be changed, just ours, since this is a problem of old app configs.
Or change old app configs in prod, to be consistent?
See also [#3981] which will track this internally
Best to update mongo
sftheme:cj/6138Went with lower-case because 61% of the tool_name values are all lower-case in production.
I thought we were going to change the values in prod
allura:cj/6138https://sourceforge.net/p/allura/pastebin/51818ea7a02bb1761ab804e6/
Code change to enforce new AppConfigs are created with lower-case tool_names, query to update existing entries.
Merged allura; didn't merge sftheme since it's not needed with the mongo approach.
Better to not change the names to lowercase all over the place, but use the entry point name in install_app (not what's passed in as a param) so the saved data is consistent within each tool.
Mongo commands to update individual tools will be needed too.
allura:cj/6138After discussing with Tim, went back to the approach of lower-casing the
tool_namevalue on theapp_configbut changed it to use the defined value from the app for the grouping label so it displays properly but is nicely standardized in mongo.Normalizing mongo to use the app-defined
tool_labelvalue would be a lot more complicated, harder to remember when querying, and still wouldn't fix the display of the grouped tools because of it callingtool_name.lower().capitalize()(essentially).