rdmorganiser / rdmorganiser/rdmo
[DMP Review] a task should specify why it is triggered
Open
Nobody has claimed this yet.
type:feature-request
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Rationale / Begründung
Users should get more information of why a specific task is activated and visible.
At the moment, tasks show the question to which the condition is linked to, but don't describe why it is shown. (e.g. because an option is not selected)
Affected
Users
Minimal functionality
- Tasks should contain the evaluation of the condition in natural language
Nice-to-have functionality
References / Verweise
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; start by tracing how task conditions are evaluated and how their linked questions are currently displayed. Done means tasks explain in natural language why their condition was triggered, including cases such as an option not being selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100