Closed floriangantner closed 5 months ago
thanks @floriangantner for this contribution. The code looks good I have just minor comments inline, can you check? are you willing to perform the same change also to add support for patent?
I've checked the comments. Support for patent will soon come in some own PR.
I can confirm, that we have integrated this PR into our production system already and it's working fine. So I guess it should be easily mergable. TORE is on version 2023.02.02.
Orcid push for product has become part of the 2023.02.03 release, thus closing the issue
References
Description
Support for Orcid Push of
Product
Entity. Allow construction of orcid work object from product entity and support for sync-mode setting change for product entity.Instructions for Reviewers
List of changes in this PR:
new metadata field to hold the sync setting for product
dspace.orcid.sync-products
new OrcidEntityType Product and corresponding Factory
OrcidProductWorkFactory
creating orcid Work objects based on Product entity.new
OrcidProductWorkFieldMapping
to use some entity-specific mapping (fields might differ from publication)orcid.cfg
or in theorcid-services.xml
the same as the orcid publication factorysimple Mapping dspace product to orcid types
data-set
extended profile orcid sync preferences operation to support the change of the sync settings for the corresponding profile
Tests: copied and aligned tests for creation of the orcid work objects for Product entity
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
pom.xml
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.