Skip to content
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

Open
alejandratenorio opened this issue Feb 6, 2025 · 5 comments
Open

Term URI (Keyword) link doesn't work as expected. #11220

alejandratenorio opened this issue Feb 6, 2025 · 5 comments
Labels
Type: Bug a defect

Comments

@alejandratenorio
Copy link
Contributor

What steps does it take to reproduce the issue?
Add an URL in Term URI and save.

Image

  • When does this issue occur?
    When you go to the dataset and click on the link, it redirects to the dataset itself, not to the actual URL.

Image

  • 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?

@alejandratenorio alejandratenorio added the Type: Bug a defect label Feb 6, 2025
@qqmyers
Copy link
Member

qqmyers commented Feb 6, 2025

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 -

keywordTermURI Term URI A URI that points to the web presence of the Keyword Term https:// url 22 <a href="#VALUE" target="_blank" rel="noopener">#VALUE</a> FALSE FALSE FALSE FALSE TRUE FALSE keyword citation
where you can see the href is just copying the value from that field.

Are you using a custom citation block?
Any custom header/footer that could be interfering with the display?

@alejandratenorio
Copy link
Contributor Author

Dear @qqmyers

It works well,

Image

Let us check our citation.tsv.

@alejandratenorio
Copy link
Contributor Author

Dear @qqmyers

We checked our citation.tsv, this metadata have the default configuration,

keywordTermURI Term URI A URI that points to the web presence of the Keyword Term https:// url 22 <a href="#VALUE" target="_blank" rel="noopener">#VALUE</a> FALSE FALSE FALSE FALSE TRUE FALSE keyword citation

Could be our Dataverse version?

@qqmyers
Copy link
Member

qqmyers commented Feb 6, 2025

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.:
Maize "<a href="" http:="" aims.fao.org="" aos="" agrovoc="" c_12332""="" target="" _blank""="" rel="" noopener""="">http://aims.fao.org/aos/agrovoc/c_12332</a>" (AGROVOC)

So something is escaping/changing characters somewhere.

@qqmyers
Copy link
Member

qqmyers commented Feb 6, 2025

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 "<a href=""#VALUE"" target=""_blank"" rel=""noopener"">#VALUE</a>" which looks at least similar to what is showing up in your page.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug a defect
Projects
None yet
Development

No branches or pull requests

2 participants