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

Validate author information using ORCID API (during author merge) #2026

Open
14 tasks
rija opened this issue Sep 10, 2024 · 0 comments
Open
14 tasks

Validate author information using ORCID API (during author merge) #2026

rija opened this issue Sep 10, 2024 · 0 comments

Comments

@rija
Copy link
Contributor

rija commented Sep 10, 2024

User story

As a curator
I want to bring up the information from ORCID about an author
So that I can decide where is the correct information, in either author entries I want to merge, or on ORCID,
and I can select the value I think it's the correct one

Acceptance criteria

Given conditions
When event
Then outcome

Given conditions
When event
Then outcome

Additional Info

Product Backlog Item Ready Checklist

  • Business value is clearly articulated
  • Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
  • Dependencies are identified and no external dependencies would block this item from being completed
  • At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
  • This item is estimated and small enough to comfortably be completed in one sprint
  • Acceptance criteria are clear and testable
  • Performance criteria, if any, are defined and testable
  • The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

  • Item(s) in increment pass all Acceptance Criteria
  • Code is refactored to best practices and coding standards
  • Documentation is updated as needed
  • Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
  • No deviation from the team technology stack and software architecture has been introduced
  • The product is in a releasable state (i.e. the increment has not broken anything)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To Estimate
Development

No branches or pull requests

1 participant