Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

orcid sync-mode for patent entity #76

Closed

Conversation

floriangantner
Copy link

@floriangantner floriangantner commented Feb 27, 2024

References

Add references/links to any related issues or PRs. These may include:

** This PR is based on the #73 PR and should be reviewed/merged afterwards or together to avoid unnecessary merge conflicts. **

Description

Add support for the Patent entity being pushed to orcid.

Instructions for Reviewers

  • support for orcid-sync-settings for Patent. The current value is readed and changes are transmitted to the extended endpoint.
  • icon for patent entity (assuming some file icon is more general and suitable for this entity type than some copyright or trademark icon)
  • translation keys for english support

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 & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using yarn lint
  • My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

@floriangantner
Copy link
Author

Orcid push for patent has become part of the 2023.02.03 release, thus closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Orcid Push for Patent Entity
1 participant