The only reason we use variable maps are to add context to
what/where/whay for each of the variables we use. If we could add that
context to the interface, it would do away with a duplication step that
is often lost, outdated and unusable for future admins to use. The
implications of this go far beyond admins. This would help ClientCare,
for example, in their attempts to help diagnose issues. If they have
context into the intended use of a variable, then they can better help
to troubleshoot rela...
Would like to see ALL settings for a particular variable be made
available (at least visible) to admin users. Expand the settings
approval process to account for settings that could incur additional
costs and/or affect data processing (eVar full subrelations).