floriangantner
commented
5 months ago @olli-gold we were struggling with some similar problem and have solved this for our ResearchData Entity. We have also prepared this for Product entity. The changes are the same for any additional entity you might want to push to orcid as Work or Funding (e.g. Pushing projects with funding information instead of Funding).
https://github.com/uniba-ub/DSpace/tree/uniba-orcid-product
https://github.com/uniba-ub/Rest7Contract/tree/uniba-orcid-product
https://github.com/uniba-ub/dspace-angular/tree/uniba-orcid-product
Restrictions:
- NISO-Roles for contributors are not supported by the orcid model used in dspace (https://github.com/ORCID/orcid-model/blob/master/src/main/java/org/orcid/jaxb/model/common/ContributorRole.java)
- Type-Mapping is not fully checked.
- citation is not working; currently only available for Publication
Is your feature request related to a problem? Please describe. The ORCID push queue may contain only items of the
dspace.entity.typepublication or funding (depending on the configuration and the settings). Products, which are the Entity Type for Research Data in DSpace-CRIS, will not get it into the push queue and can therefore not been pushed to ORCID from DSpace-CRIS.In DSpace-CRIS 5 research data was treated like publication items and they could have been pushed to ORCID as works on ORCID side.
Describe the solution you'd like I would like to have Research Data, which is stored correctly as Products, within the ORCID registry queue, to be able to push those items from DSpace-CRIS to ORCID.
Describe alternatives or workarounds you've considered As far as I see, this is not configurable after all, so I do not see a chance for a workaround on it.
Additional context None I am aware of.