Broader access to API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
Allow researchers to generate their own tokens. Currently an admin has to make a researcher a token and provide it to them in order to use the API. Ideally anyone could try out the API on their own, without this manual step; this would encourage more development (not by us!) of coding tools that make use of automated data retrieval.
Considerations:
* Rate limiting
* MAYBE limit how long a token is active (e.g. a year)
* Logging activity (token + request)
* Alert system so we don't have to manually monitor logs
Contributor 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.
Research direction
No files, tests, or entry points are named. Begin by locating the API token and researcher-authentication flow, then resolve rate limiting, token lifetime, request logging, and alerts; done means researchers can generate usable tokens without admin intervention and the monitoring controls are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100