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

DOIs that need to be synced still shown as "stale" #8677

Closed
NateWr opened this issue Feb 21, 2023 · 0 comments · Fixed by #8688
Closed

DOIs that need to be synced still shown as "stale" #8677

NateWr opened this issue Feb 21, 2023 · 0 comments · Fixed by #8688
Assignees
Labels
Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround
Milestone

Comments

@NateWr
Copy link
Contributor

NateWr commented Feb 21, 2023

Describe the bug
The status for DOIs that have been republished since they were last deposited used to be called "Stale". This was renamed to "Needs Sync". However, the status badge that appears on the right of each DOI in the list still says "Stale". See screenshot:

needs-sync

This should be changed to match the filter name.

To Reproduce
Steps to reproduce the behavior:

  1. Create at least one submission with a DOI that is marked registered.
  2. Create a new version of that submission and publish the new version.
  3. Go to DOIs management UI.
  4. See error

What application are you using?
main branch (3.4 pre-release)

@NateWr NateWr added the Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround label Feb 21, 2023
@NateWr NateWr added this to the 3.4.0-1 milestone Feb 21, 2023
@NateWr NateWr moved this from Backlog to Todo in Metadata and Distribution Feb 21, 2023
@ewhanson ewhanson linked a pull request Feb 23, 2023 that will close this issue
@asmecher asmecher modified the milestones: 3.4.0-1, 3.4.0-0 Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug:1:Minor A bug found in uncommon paths, with low consequences, limited users or has an easy workaround
Projects
Development

Successfully merging a pull request may close this issue.

3 participants