opensafely-core / opensafely-core/opencodelists

Enhancement request: add warning for older dm+d codelists

Open
#2,861 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
60
Forks
16
Avg merge
4d 12h
Merged PRs (30d)
17

Description

Summary

Add warning for users cloning older dm+d codelists:

User joined Office Hours last week and asked why he couldn't edit the clone of a dm+d codelist. It turns out that the codelist is so old that the dm+d builder is unable to handle it and so the user will need to create it from scratch unfortunately.

What would you like to achieve?

Make it clear to users that dm+d codelists (or does this apply to other codelist systems?) beyond a certain age won't be editable after cloning and would need to be recreated instead.

Who would benefit and how?

Users find the cloning feature useful to update codelists that were created by another user. But it's off-putting if they don't know that some codelists can't be edited after using the new feature.
It's makes sense that the older codelists may not be easily editable but users may not be aware of this or why. Some messaging would help dispel the feeling they're missing something / done something wrong.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Trace the codelist cloning flow and identify how dm+d codelist age and editability are determined. Confirm the age threshold and whether the same limitation applies to other codelist systems. Done means users receive clear messaging that an old cloned codelist cannot be edited and must be recreated instead.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.