-
Notifications
You must be signed in to change notification settings - Fork 498
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
Term URI (Keyword) link doesn't work as expected. #11220
Comments
Can you reproduce this on https://demo.dataverse.org/ ? It's a strange issue as that link is generated from code reading the citation metadata block -
Are you using a custom citation block? |
Dear @qqmyers It works well, Let us check our citation.tsv. |
Dear @qqmyers We checked our citation.tsv, this metadata have the default configuration,
Could be our Dataverse version? |
Possibly - I didn't think there were changes in this since 6.4 but maybe there were - perhaps someone else can think of a relevant change. I do see from your page that the value in the href is messed up rather than missing, e.g.: So something is escaping/changing characters somewhere. |
One guess - could someone have looked at/saved the citation.tsv using Excel? When that's done Excel may escape entries that include quote marks. When I just tried here, I see that the formatting is changed to If that's it, the fix would be to get a fresh copy of the citation block from https://github.com/IQSS/dataverse/raw/refs/tags/v6.4/scripts/api/data/metadatablocks/citation.tsv and load it following the instructions in https://guides.dataverse.org/en/6.4/admin/metadatacustomization.html#loading-tsv-files-into-a-dataverse-installation . That should overwrite the formatting for the language field and fix the issue. |
What steps does it take to reproduce the issue?
Add an URL in Term URI and save.
When you go to the dataset and click on the link, it redirects to the dataset itself, not to the actual URL.
Which page(s) does it occurs on?
Dataset page
What happens?
the link redirects to the dataset itself, not to the actual URL.
To whom does it occur (all users, curators, superusers)?
all users
What did you expect to happen?
the redirects to it's URL.
Which version of Dataverse are you using?
6.4
Any related open or closed issues to this bug report?
Screenshots:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
The text was updated successfully, but these errors were encountered: