Add data sources for funder APIs

Open
#34 1 comment 0 reactions 0 assignees View on GitHub

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
Domain
api, backend, database

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CDLUC3/dmsp_api_prototype

All issues in CDLUC3/dmsp_api_prototype

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.