As Dataverse expands to new disciplines and as we seek new ways to ensure high quality metadata, we should take an opportunity to discuss where we can make some improvements. We鈥檝e had good feedback from the community across several issues (#5938, #6003, #3622, #6000, #4772, #350, #2603, #4282), which I鈥檝e tried to capture as use cases below.
This issue will focus on proposing a solution to cover as many of these use cases as possible (and others that I'm sure I'm missing) instead of trying to push forward individual issues.
Awwww yisss, let's get the party started!

May I add to the list:
FWIW: Clowder has implemented this type of functionality, pulling controlled vocabulary from external services or static json lists posted to a URL. In their case, I think the semantic term and value are recorded, but not the provenance of when the vocab choices were retrieved. The GUI just presents pull down lists or autocompletes for these terms rather than a type-in.
If anyone wants pointers to look at their GUI for this or to hear more about the implementation, let me know.
@qqmyers is there a demo site for Clowder so we can play around with the UI? And get a sense of the UX?
They have an official demo site, but I'd suggest https://sead2.ncsa.illinois.edu/ where I know what features are turned on.
Had a brief discussion in design mtg today about the potential for a consistent application support of markdown in areas such as metadata block help text (#6476), as well as metadata values entered by dataset creators (#6383) and even dataverse descriptions (no specific issue yet, but this one is kinda sorted related #1249). Adding note here of proposed project synergy per request from @TaniaSchlatter.
I updated #4772 with some slides from the Flexible Metadata session at DCM2020 as input for this issue.
Most helpful comment
They have an official demo site, but I'd suggest https://sead2.ncsa.illinois.edu/ where I know what features are turned on.