Separate the study form view into edit & view
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
# TL;DR
Separate the study edit form into a view for editing and a view for seeing the details without being able to edit.
# Narrative
The current dual use of the study form is confusing to maintain permissions for (some people can see details but not make changes) and to use - in order to see the details of a study, like the actual protocol, you have to click "edit study" and may or may not be able to actually save changes.
This especially impacts situations like studies in the Demo lab, where all researchers should be able to see all details, but while they can preview the study, they have to clone it to see the details because they can't see the edit view.
# Acceptance Criteria
- [ ] Separate study detail edit & detail views
- [ ] Buttons for edit & view added to the main study detail page per permissions (e.g. "Edit study" and "View study details" buttons)
- [ ] Tests of permissions are broken out everywhere the study edit form is currently tested
- [ ] "Shared preview" option on study still only grants ability for any researcher to preview study - not READ_STUDY_DETAILS equivalent
Contributor guide
Research direction
Start from the current study edit form and the main study detail page, then inspect the existing permission tests around that form. Separate editing from read-only details, add permission-aware edit and view buttons, and ensure shared preview does not grant study-detail access; the acceptance criteria define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100