Add data sources for funder APIs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start by locating the existing funder API logic and the backend's affiliation record, schema, resolver, and model definitions. Trace how affiliations and funder API calls are represented before deciding how each API becomes a data source. Done means each API has a backend data source, affiliations reference their data sources, the supporting schema, resolvers, and models work, and the old APIs are removed.
Written by the indexing model from the issue text.
Description
Move the logic we currently have in the API for interacting with the funder APIs into the backend.
- Create a data source for each API
- Update the affiliation record to include a ref to the datasource so that we know which datasources belong to which affiliations
- Add schema, resolvers and models to support calling the APIs
Delete the old APIs afterward.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CDLUC3/dmsp_api_prototype
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
CDLUC3/dmsp_api_prototype#45 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
CDLUC3/dmsp_api_prototype#42 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
CDLUC3/dmsp_api_prototype#39 · 1 comment ·
-
Update publish plan resolver for EZID registrationMay be free again @jupiter007 claimed this 134 days ago, and no pull request is open. Open
CDLUC3/dmsp_api_prototype#32 · 3 comments · 1 assignee ·
-
bug indices
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in CDLUC3/dmsp_api_prototype
Similar issues
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JSPrismarine/JSPrismarine#3271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day