GDCC/8914 COAR Messaging Improvement #11983
Open
Conversation
This file contains hidden or 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
GDCC/8914-COAR-compliant_messaging
…om/GlobalDataverseCommunityConsortium/dataverse.git into GDCC/8914-COAR-compliant_messaging
GDCC/8914-COAR-compliant_messaging
GDCC/8914-COAR-compliant_messaging
GDCC/8914-COAR-compliant_messaging
…com/GlobalDataverseCommunityConsortium/dataverse.git into GDCC/8914-COAR-compliant_messaging
GDCC/8914-COAR-compliant_messaging
This was referenced Dec 4, 2025
cmbz
added
FY26 Sprint 14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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: This PR updates the COAR Notify Relationship Announcement support in Dataverse to avoid sending repeat messages, i.e. when a new dataset version is published but the relevant metadata field (e.g. Related Publication) hasn't changed.
It also fixes a minor bug that prevented values in the publicationURL field from being used when a publicationIDType was provided.
Which issue(s) this PR closes:
Special notes for your reviewer: This is a relatively small PR that includes the changes in #10490 and the bugfix from #11991. It should be clearer once those PRs are merged.
Suggestions on how to test this: Setup messaging to some test service, or probably easier, verify that a message is not sent when a later version is published without a change in metadata by turning on fine logging and looking at what's sent.
The bug fix can be tested by selecting an ID type (like 'url') and putting the value in the 'URL' field for the related publication and verifying that a message is sent when the dataset is published.
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?:
Additional documentation: