Open BPeuch opened 3 years ago
Nǐ hǎo,
I was wondering if someone could test this on Demo Dataverse? We cannot do it ourselves because I don't think we may inject an edited .tsv file in the system ourselves.
@BPeuch hi! Generally speaking, we don't recommend changing citation.tsv (and other blocks that ship with Dataverse) unless you're making some sort of general improvement and plan to make a pull request.
Have you played around with external vocabularies? They're documented here: https://guides.dataverse.org/en/5.12/admin/metadatacustomization.html#using-external-vocabulary-services
I'm concerned they won't "just work" with Topic Classification (we've gotten Author Affiliation to work with ROR, at least) but hopefully as we work on controlled vocabularies in the following issue, we'll start to make some overall progress:
If you want to keep going with an internal metadata block, I'd suggest making a new one, outside of citation.tsv.
Happy to chat more! It's completely understandable what the end goal is! More vocabularies!
Version: 4.20
Zdravo,
We think there might intereferences between dataset templates and controlled vocabularies.
We tried to add a controlled vocabulary for the
Topic Classification
>Term
field (based on the CESSDA Topic Classification) by modifying the citation.tsv file.Everything seemed to work fine when we got to the
Add Data
>New Dataset
form: the field had become a dropdown menu and the input values could be selected.But then, after saving the changes, the field was empty in the metadata:
(And the content of the
Vocabulary URL
field also appears between quotation marks.)Interestingly, if we add more instances of
Topic Classification
by clicking the+
button, the value put in those new instances are saved, but never the first one.We tried creating a new dataset but this time without any dataset template (we have one selected by default). Then the information was properly saved in the dataset's metadata.
I should also specify that, in our templates (all of them), the
Topic Classification
>Vocabulary
andTopic Classification
>Vocabulary URL
are prepopulated, but not the case of theTopic Classification
>Term
field:(There is also a custom watermark as you can see, but we added it only after observing the problem.)
We could perhaps try to replicate this issue on Demo Dataverse?