Skip to content

PD-5947 Move the record corrections page to the Angular app - #2908

Open
cryptalith wants to merge 1 commit into
mainfrom
lmendoa/PD-5947
Open

PD-5947 Move the record corrections page to the Angular app#2908
cryptalith wants to merge 1 commit into
mainfrom
lmendoa/PD-5947

Conversation

@cryptalith

@cryptalith cryptalith commented Aug 21, 2026

Copy link
Copy Markdown
Member

Summary

  • Serves /record-corrections from a new lazy-loaded feature module instead of the legacy FreeMarker/ng2 page, matching the Figma design.
  • Reuses the existing public /record-corrections/next and /previous endpoints as-is (keyset pagination by row id, page size 10, no backend contract change).
  • /about/trust/integrity/record-corrections redirects to the new route and carries its own title label, since TitleService matches the requested URL rather than the redirected one.
  • Loading state uses the shared SkeletonPlaceholderComponent from @orcid/ui, laid out in the table's own columns.
  • Page title set to "Record corrections - ORCID" per the acceptance criteria.

Pairs with ORCID/ORCID-Source#lmendoa/PD-5947, which flips nginx routing to this page and removes the legacy view. This Angular PR is safe to deploy first — nginx still routes the path to the legacy app until that PR lands.

Serve /record-corrections from orcid-angular instead of the legacy
FreeMarker page, following the Figma design. The page keeps using the
existing public /record-corrections/next and /previous endpoints, which
paginate by row id rather than by page number.

The pre-migration /about/trust/integrity/record-corrections URL redirects
to the new route. TitleService matches on the requested URL rather than
the redirected one, so that path carries its own label.

The loading state uses the shared skeleton placeholder from @orcid/ui,
laid out in the table's own columns so it resolves into the loaded rows
without the layout shifting.
@amontenegro

Copy link
Copy Markdown
Member

Task linked: PD-5947 Update record corrections page

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.

2 participants