IQSS
IQSS/8914 COAR compliant LDN messaging
What this PR does / why we need it: This PR updates our COAR LDN messaging to be compliant with the final specification.
Which issue(s) this PR closes:
Closes #8914
Special notes for your reviewer: This work was done quite a while back but there's discussion about reviving the effort - verifying that the code is compliant and possibly looking into making it more general/able to support other COAR scenarios, etc. I've created a draft PR to make the existing work easier to asses and to make it easier to find this code if/when that effort gets going.
The code has not yet been built/tested after the merge with Dataverse ~v6.2 (EE10 and multipid updates since the original work).
Suggestions on how to test this:
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:
coverage: 24.165% (+0.1%) from 24.037% when pulling 54b060cdcecbd910db685925b842d05ed540cede on GlobalDataverseCommunityConsortium:GDCC/8914-COAR-compliant_messaging into b8f5c1e7a4fb0907b6ca03268b28301717ff0bff on IQSS:develop.
Note: A v.1.0.0 version of the COAR Notify specification has just been released - see https://coar-notify.net/2024/significant-revision-to-specification/. This PR has not yet been checked to make sure it is consistent with the changes in this release.
Working with Colin Lukens to test this against a DASH/DSpace test instance and finalize the PR once we know it works/bugs are fixed, etc.
I'm also seeing a lot of these in the log
6.2025.3|edu.harvard.iq.dataverse.api.LDNInbox|_ThreadID=240;_ThreadName=http-thread-pool::http-listener-1(7);_TimeMillis=1763736091927;_LevelValue=1000;|
Ignoring message from IP address: 178.128.69.202|#]
LDNInboxIT is not included in tests/integration-tests.txt which explains why there were no failures in the pipeline tests