-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Customization of subject list #5938
Comments
Yes I think there is broad interest in installations being able to customize the Subject list to meet their needs. I recommend reading the following (and replying if you feel moved to):
We put the following warning at http://guides.dataverse.org/en/4.14/admin/metadatacustomization.html "Generally speaking it is safer to create your own custom metadata block rather than editing metadata blocks that ship with Dataverse, because changes to these blocks may be made in future releases of Dataverse. If you’d like to make improvements to any of the metadata blocks shipped with Dataverse, please open an issue at https://github.com/IQSS/dataverse/issues so it can be discussed before a pull request is made." That is to say, we should work toward a general solution, like you're suggesting! 😄 p.s. I can understand why you gave this issue a title of "Localization of subject list" but I wonder if "Customization of subject list" might be a little better and more general. It might speak to more people. |
@pdurbin Thanks! I'll check these links you suggest and get back to this one with ideas. |
Closing in favor of #6030 to evaluate as part of a larger effort. |
In the Dataset's citation metadata there is a mandatory 'Subject' field (according to the hint beside the field: it contains "Domain-specific Subject Categories that are topically relevant to the Dataset."). In Germany the main funding agency has a standard subject list and we would like to use that instead of this subject list. It is clear that the subject list is defined by the citation.tsv file, so the API regarding to the custom metadata block applies if we change the file.
There are two questions:
The text was updated successfully, but these errors were encountered: