Harvest: map publisher tag to distributorName
What this PR does / why we need it:
Which issue(s) this PR closes:
- Closes https://github.com/IQSS/dataverse/issues/8739
If you are still interested in this PR, can you please merge and resolve any merge conflicts with the latest from develop? If so, we can prioritize reviewing and QAing the changes. If we don’t hear from you by May 22, 2024, we’ll go ahead and close this PR (it can always be reopened after that date, if there is still interest).
The branch is now up to date with develop and the sql migration file was renamed to match the latest version - please tell me if there is any convention I'm missing.
@plecor can you please add a release note snippet that describes what this pull request does? Please see https://guides.dataverse.org/en/6.2/developers/version-control.html#writing-release-note-snippets
Also, it would be nice to add something to the guides but I'm not sure where. Maybe we should add a changelog to https://guides.dataverse.org/en/6.2/admin/harvestserver.html ? Would that make sense?
Finally, tests are always nice but not strictly required. There are some in HarvestingServerIT.java.
Thanks @pdurbin.
I created a release note and added the relevant test to HarvestingClientsIT. I'm really not sure however where this would fit in the docs.
@plecor I went ahead and added a new changelog for harvesting clients: https://dataverse-guide--9013.org.readthedocs.build/en/9013/admin/harvestclients.html#harvesting-client-changelog
In review we'll see what others think.
coverage: 22.754%. remained the same when pulling 7e72b256598b0f01dfa9d2bfa0a0c394f8a47494 on tcoupin:8739-publisher-during-harvesting into 4dfb9e76d8ae02a06d4817467d7236c3808bf094 on IQSS:develop.
This branch has some conflicts to resolve before I can QA.
@ofahimIQSS I updated the branch to resolve the conflict.
what harvesting client should this be tested with?
Tested Harvesting, performed regression testing in internal - no issues found. Conflict needs to be resolved.
@ofahimIQSS I resolved the merge conflicts.
Tested after conflict resolution - no issues found. Merging PR