-
Notifications
You must be signed in to change notification settings - Fork 494
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
Computational Workflow metadata block bug: links don't link #10339
Comments
Related to: IQSS/dataverse-pm#146 |
In the metadatablock's TSV (see copy on Google Sheets), the field's "fieldType" is url, so it accepts only that. But its "displayFormat" is empty, where we would normally have something like So I think we'd want to add |
@jggautier yep, sounds right. We'll also want to update the version in git, of course: https://github.com/IQSS/dataverse/blob/develop/scripts/api/data/metadatablocks/computational_workflow.tsv |
Ah, yeah updating that TSV file, not the Google Sheets copy, is what I meant. Once that TSV file is updated, I could update the Google Sheets copy. |
@cmbz FYI, @kmika11 made a pull request... ... so I advanced it to "ready for review" and removed this issue (10339) from the board, like we usually do. It was in "this sprint". I'm not sure if Katie has permission to do this on her own but we could obviously adjust perms for the future. Thanks for the pull request, Katie! |
In the Computational Workflow metadata block, the field for "External Code Repository URL" requires a valid URL, but then does not present a link in the UI.
What steps does it take to reproduce the issue?
When does this issue occur?
When adding a URL to the "External Code Repository URL" field in the Computational Workflow metadata block.
Which page(s) does it occurs on?
The dataset page, under the Metadata tab.
What happens?
Plain text is displayed.
To whom does it occur (all users, curators, superusers)?
All users.
What did you expect to happen?
A clickable link to be displayed that takes the user to the URL location.
Which version of Dataverse are you using?
6.1
Any related open or closed issues to this bug report?
No
Screenshots:
--
The text was updated successfully, but these errors were encountered: