Display overview fix #11034
Open
Display overview fix #11034
+6
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qqmyers
requested changes
Nov 19, 2024
| @@ -7,6 +7,10 @@ This API changelog is experimental and we would love feedback on its usefulness. | |||
| :local: | |||
| :depth: 1 | |||
|
|
|||
| v6.5 | |||
There was a problem hiding this comment.
This is only for API changes so I don't think we want an entry here.
There was a problem hiding this comment.
Yes, the release note is enough. Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
On the metadata page there can be duplicated / redundant metadata entries. This pull-request fixes an IF-clause in metadataFragment.xhtml to eliminate the redundant display of metadata fields
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: (from Jim) - see the issue - looks like you can see the issue if you configure the ORCID script but not the ROR script via the external vocabulary mechanism (https://github.com/gdcc/dataverse-external-vocab-support/blob/main/examples/authorIDandAffilationUsingORCIDandROR.md describes adding both, the ROR script can be dropped by removing the JSON object for the ROR script).
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?: included
Additional documentation: