The-Strategy-Unit / The-Strategy-Unit/tpma-explorer
Fetch data from most appropriate location
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
For MVP purposes, some lookup data is being stored in inst/data/. Ideally this will be read in from a central/original source.
In future we may store TPMA content centrally (https://github.com/The-Strategy-Unit/nhp_planning/issues/411) and could retrieve the data from there (setting up a GitHub app so that the deployed app can read the data). The supporting data container is closing (https://github.com/The-Strategy-Unit/nhp_planning/issues/432), so we should avoid it.
More generally, should we read from the GitHub API to fetch e.g. strategy text from nhp_inputs, or just read directly from the URL? There's some demo code in github_dashboard for ther API, including PEM generation for access tied to an app rather than an individual's PAT.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the lookup data in inst/data/ and the demo GitHub API code in github_dashboard, then compare the GitHub API and direct-URL options for content in nhp_inputs/inst/app/strategy_text. Done means selecting and documenting an appropriate central source and retrieval approach, while accounting for the referenced TPMA and supporting-container changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, r
- Domain
- backend-api-design, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100