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

[MAINTENANCE] Unify N2T and EZID Resolver Logic Post-Migration #652

Open
4 tasks
adambuttrick opened this issue Jun 5, 2024 · 0 comments
Open
4 tasks
Labels
maintenance Routine or one-off maintenance or clean-up task

Comments

@adambuttrick
Copy link

adambuttrick commented Jun 5, 2024

Service/repository
EZID Resolver

Describe the current state/issue

As the N2T migration nears completion, the final state of N2T's resolver and that implemented in EZID have somewhat diverged.

Describe the desired state/solution

The logic for these should be unified or kept consistent to the largest degree possible moving forward.

Tasks

  • Confer with Dave on the current state of the N2T resolver, documenting any differences from the EZID implementation.
  • Define total possible scope of alignment and required changes to EZID resolver.
  • Update EZID resolver logic relative to the above.
  • Define and document plan for updating logic in both services (to the extent possible) relative to changes in N2T.
@adambuttrick adambuttrick added the maintenance Routine or one-off maintenance or clean-up task label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Routine or one-off maintenance or clean-up task
Projects
None yet
Development

No branches or pull requests

1 participant