-
Notifications
You must be signed in to change notification settings - Fork 447
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
[Port dspace-7_x] ORCID Push Queue: add support for Products and Patents #3351
base: dspace-7_x
Are you sure you want to change the base?
[Port dspace-7_x] ORCID Push Queue: add support for Products and Patents #3351
Conversation
Hi @atarix83, |
I had a chance to talk briefly with @sheilarabun from the ORCID US Consortium , and it's clear that these Product/Patent PRs are "nice to have" but not as high priority as the other ORCID integration bug fix PRs that were funded by the ORCID Global Participation Fund grant. Therefore, I'm going to leave these Product/Patent PRs open, but I've flagged them all as "low priority" as they are waiting for more feedback from the DSpace community. Up until now, I haven't heard requests to add "Product" and "Patent" as new Entity Types in DSpace. So, we need to get more feedback on that idea -- if many agree these types should be added, then we will immediately move these PRs forward. But, in the meantime, sites that want Product/Patent integration with ORCID should feel free to test these PRs and report back. That will help us to better determine the demand for this feature. |
…pace-7_x/CST-14906_product_patent_orcid # Conflicts: # src/app/item-page/orcid-page/orcid-sync-settings/orcid-sync-settings.component.ts
References
Description
The ORCID push queue may contain only Publication or Project items (depending on the configuration and the settings). This pull request add support for Product and Patent.
Instructions for Reviewers
Please refer to instructions available in REST PR DSpace/DSpace#9850
Checklist
main
branch of code (unless it is a backport or is fixing an issue specific to an older branch).npm run lint
npm run check-circ-deps
)package.json
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.