Aviary variable metadata has a large number of "alternate" names for historical variables that trace where those values are present inside the code, but not the same as names used to define an input file. These variables needed to be commented out to avoid conflicts with the converter utility, but retaining them may be useful for traceability and debugging.
A plan for these commented out variables is needed. Should they be added to a new key in the metadata to keep the F2A converter clean? Or perhaps documentation via comments is acceptable, and just re-formatting the commented out information is all that is needed.
Is your feature request related to a problem? Please describe.
Desired capability or behavior.
Aviary variable metadata has a large number of "alternate" names for historical variables that trace where those values are present inside the code, but not the same as names used to define an input file. These variables needed to be commented out to avoid conflicts with the converter utility, but retaining them may be useful for traceability and debugging.
A plan for these commented out variables is needed. Should they be added to a new key in the metadata to keep the F2A converter clean? Or perhaps documentation via comments is acceptable, and just re-formatting the commented out information is all that is needed.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response