ORCID Registry Queue table: Fix behavior on item removal from the table

[alisaismailati]

References

• Fixes ORCID Registry Queue table becomes empty when all items on the last page are unlinked #3462

Description

Fixes include refactor the ORCID queue component (orcid-queue.component.ts) to update pagination options not only when changing pages (handled by the pagination component) but also when items are removed from the table. Additionally, eliminate the flickering behavior on item removal.

Instructions for Reviewers

List of changes in this PR:

• The first refactor involves storing data in a component variable and, upon deletion, removing the element from the list without making another call to retrieve data.
• If the last element on the page is removed, navigate to the previous page by updating the current page in the pagination options and reflecting it in the URL. This way we may retrieve the remaining data for that new page.
• Additionally, handle the fragment to scroll into view (table) on page change, as the pagination component's fragment handling was not working correctly in this case. This way when we change the page of the table, we will be repositioned again to the table.

Include guidance for how to test or review your PR.
Steps described on #3462

Result:
(p.s test is done using dummy data for the publications)

orcid-queue.mp4

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• 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 npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run 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.