The-Strategy-Unit / The-Strategy-Unit/TPMAs
Change how we handle creation/deprecation fields
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
TPMA creation and deprecation are described by the active_from and active_to fields in the main lookup. These can be used to filter down from the full set of every TPMAs that ever existed.
But the values in these columns are NHP demand-model release versions. TPMAs existing beyond NHP now; we probably shouldn't tie these to core NHP functionality.
Suggestion:
- Extract the
active_fromandactive_tofields (containing NHP model versions) into their own separate lookup (withtpma_codeas the unique joining key). - Use dates as values for the
active_fromandactive_tofields. This still allows filtering for currently-active TPMAs. - Introduce a changelog. This could be as simple as
tpma_code,date,descriptionto explain a change that didn't warrant a new TPMA code. This could be used downstream by e.g. tpma-explorer.
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 locating the main lookup and the current active_from and active_to fields, then review the linked tpma-explorer issue for downstream expectations. Done means the NHP-version fields are separated into a lookup keyed by tpma_code, active dates support filtering, and a changelog records relevant changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100