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

[Port dspace-8_x] Orcid Authorization / Synchronization Page Fixes #3216

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

vins01-4science
Copy link
Contributor

@vins01-4science vins01-4science commented Jul 25, 2024

Please note that this development has been funded by the ORCID Global Participation Fund.


main version here: #3181
DSpace 7_x version here: #3182

References

Description

This PR solves various issues related to the orcid synchronization feature (those issues were related to the stale status of a request saved inside the cache). The full list of issues can be found here: #8925.

Instructions for Reviewers

You should check the behavior of the synchronization page, as suggested inside the issue #8925.
Moreover, you should check that the code parameter of the URL is cleared once the account has been connected successfully by using the proper button (Connect to Orcid)

List of changes in this PR:

  • Introduces reactive states derived from item inside orcid-sync page
  • Removes unnecessary navigation
  • Introduces catchError operator and handles failures with error messages

Checklist

  • 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.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • 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.

feat:
- Introduces reactive states derived from item inside orcid-sync page
- Removes unnecessary navigation
ref:
- Introduces catchError operator and handles failures with error messages
@vins01-4science vins01-4science added high priority authentication: general general authentication issues 1 APPROVAL pull request only requires a single approval to merge integration: ORCID Related to integration with ORCID identifier system labels Jul 25, 2024
@tdonohue tdonohue added this to the 8.1 milestone Jul 25, 2024
@tdonohue tdonohue added the bug label Jul 25, 2024
@kshepherd kshepherd self-requested a review November 27, 2024 12:20
Copy link
Member

@tdonohue tdonohue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Merging as this was approved/merged for main in #3181 by @kshepherd . The changes in this PR are identical.

@tdonohue tdonohue merged commit 30718cb into DSpace:dspace-8_x Dec 2, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 APPROVAL pull request only requires a single approval to merge authentication: general general authentication issues bug high priority integration: ORCID Related to integration with ORCID identifier system
Projects
Development

Successfully merging this pull request may close these issues.

2 participants