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

Align Funder table with Research Organization Registry (ROR) #2135

Open
14 tasks
only1chunts opened this issue Dec 17, 2024 · 0 comments
Open
14 tasks

Align Funder table with Research Organization Registry (ROR) #2135

only1chunts opened this issue Dec 17, 2024 · 0 comments

Comments

@only1chunts
Copy link
Member

User story

As a admin user
I want to know that our funder organisation list if upto date
So that I our users have the most upto date list to chose from

Acceptance criteria

Given a user wants to include some funding information
When they come to enter the Funder name
Then they are presented with a upto date list of option from Research Organization Registry (ROR)

Given a user wants to include some funding information
When they come to enter the Funder name
And the funder they want to add is not present
Then they are able to include a free text option
And they must complete the other mandatory information about that funding body; Organisation type, Other names/Alias, Location, Website/URL and (optional) any other known identifiers , e.g. ISNI, GRID or Wikidata.
Those details should then be used to request the addition of that institute to ROR, they have a manual form to do that here but they probably have a programatic method using their API too.

Additional Info

Our original list of funders was taken from FundRef (a long time ago!) but since 2024 FundRef has been merged into ROR, there is an announcment article here.

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: No status
Development

No branches or pull requests

1 participant