Evaluate and document evaluation of ROR plug-in on Demo Dataverse

[jggautier]

#9151 tracked work done to adjust the controlled vocabulary javascript so that it could be used on the Author Affiliation field in Demo Dataverse and depositors can choose affiliations from RORs database.

This issue is about the recommendations I made in #9151:

1. Evaluate the change to the Author Affiliation field on Demo Dataverse, comparing it to the best practices in the document that the NIH GREI ROR Task Group drafted
2. Document that evaluation so that we can build on it as research and design continue for using ROR and other controlled vocabularies, like ORCID, across all of the metadata fields that Dataverse ships with

The Dataverse UX Working Group is discussing how it can continue the research and design needed for support of PIDs that describe people and organizations and I think that evaluating the changes to the Author Affiliation field on Demo Dataverse would be a part of that work.

I'm proposing that the definition of done for this issue be the second item in that list, about documenting an evaluation of the changes to the Author Affiliation field on Demo Dataverse.

[jggautier]

The UX WG will evaluate and document the ROR plug-in as part of its first design sprint for improving the collection and use of metadata about people and organizations associated with deposits, including use of ROR and ORCID. The GitHub issue at IQSS/dataverse-pm#127 lists GitHub issues where we'll track progress of the design sprint, so I'll close this GitHub issue.