Open ffritze opened 3 days ago
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:
Hi there, I have just committed a removal from changelog.rst.
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: