rdmorganiser / rdmorganiser/rdmo
[enhancement] Filtering and faceting a project per user and role
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
Descriptive summary
Filtering and faceting of a project will provide per user and role defined views as well as per user sub-interviews.
Affects
Users and Managers
Rationale
Active data management requires RDMO to provide even more granular user based roles and view. For example a project employee must not see all answers (costs may possibly stating his salary) and answer all questions.
Expected behavior
-
tagging of
- Authors to see/edit questions/answers
- users to answer questions (assign)
-
tag projects or data sets within or across projects to allow cross-view / cross-evaluation
Use case: sub projects and data sets in collaborative research centers
Related work
Implement editorial workflow issue 84)
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
The issue names no files, tests, or entry points. Start by reviewing the related editorial-workflow issue 54 and clarifying the proposed author and user permissions, assignments, and project or dataset tagging; done requires an agreed design covering visibility, editing, answering, and cross-project evaluation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100