Patent entity in orcid Push

References

Fixes https://github.com/4Science/DSpace/issues/431
Related to https://github.com/4Science/Rest7Contract/pull/7
Counterpart Frontend/dspace-angular: https://github.com/4Science/dspace-angular/pull/76

This PR is based on the https://github.com/4Science/DSpace/pull/428 PR and should be reviewed/merged afterwards or together to avoid unnecessary merge conflicts.

Description

Support for Orcid Push of Patent Entity. Allow construction of orcid work object from patent entity and support for sync-mode setting change for patent entity.

Instructions for Reviewers

new metadata field to hold the sync setting for patent dspace.orcid.sync-patents
new OrcidEntityType Patent and corresponding Factory OrcidPatentWorkFactory creating orcid Work objects based on Patent entity.
new OrcidPatentWorkFieldMappingto use some entity-specific mapping (fields might differ from publication)
- the mapping can be configured in the orcid.cfg or in the orcid-services.xml the same as the orcid publication factory
- support Orcid pat identifier in the dc.identifier.patentno field
- Patent agency/Publisher dc.publisher is mapped to the journal-title (the swiss knife of the orcid mapping field which can contain Journal title / Book title / Conference title / Magazine title / Newspaper title / Newsletter title / Publisher / Institution / Custodian depending on the document type)
- citation crosswalk to csl/bibtex is not working with Patents
- simple Mapping dspace patent to orcid types
- might be extended in future. We rely to https://info.orcid.org/ufaqs/what-work-types-does-orcid-support/ overview of types
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 Patent 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!

[ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[x] My PR passes Checkstyle validation based on the Code Style Guide.
[ ] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[x] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[ ] If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
[x] If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
[ ] If my PR fixes an issue ticket, I've linked them together.

4Science / DSpace