Allow for Missing Value Codes and Explanations in Editor

[maier-m]

Allow for missing value codes and explanations in the attribute editor as an enhancement to the editor.

[jagoldstein]

It would be helpful to prioritize this/ assign it to a milestone as it is the last piece of metadata that we regularly ask submitters for that does not have an entry field or a workaround in the new editor.

It seems silly to have researchers fill out everything on the webform, but then also email us missing value code explanations. While most end up sticking this in the entityDescription, it is easier for the support team to only ADD these explanations, rather than also removing them from entityDescription, thus why we prefer email.

[laurenwalker]

I will assign this to 3.4.0, which is the milestone for the new attribute editor. I think at this point we're going to stop adding things to the current attribute editor and try to focus our time on the new one.

[jeanetteclark]

I'm going to bump this issue with a comment, since it is something that we regularly do for PIs as part of our dataset processing

[mbjones]

I'll second @jeanetteclark 's bump, and add a high priority label. I think this type of change would easily be added to the existing attribute editor, and so unless the attribute editor refactor can be done very quickly, this should probably be done to the existing editor first. Missing value codes are key metadata that we need to be collecting.

[laijasmine]

checking in on this issue to see if adding the missing value fields to the editor can be prioritized

[laurenwalker]

Yes, I will try to get this into the next minor release

[laijasmine]

Thanks Lauren!

[robyngit]

This is now complete pending review in branch feature-612-missing-value-code