rdmorganiser / rdmorganiser/rdmo

Feature to mark answers or parts of an answer as private

Open
#341 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature-request
Dominant language
Python
Stars
133
Forks
60
Avg merge
3d 14h
Merged PRs (30d)
21

Description

It would be good to have a feature to mark answers or parts of an answer (e.g. only a text field with supplemental information) as private when filling out a questionnaire, i. e. a researcher should be able to mark any answer or part of an answer they enter as private. The idea would be to be able to define in a view whether these private answers should be visible in the exported document or not.

By presenting a researcher two views, one that includes private answers and the other that excludes them, it would be possible for them to export one DMP document for internal use with all information and a second, official DMP only containing public information for a research funder, for example.

An example would be the question "Where is your data stored?". For a research funder, an answer "on an institutional server" would be sufficient, but within the research group the information of the server address (either as IP or DNS) would be needed. While this information is irrelevant for the funder, it is essential, especially after the end of a project, in order to be able to find all of the files that were generated during the project.

Contributor guide

Open the contributing guide

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

No files, tests, or entry points are named. Begin by locating the questionnaire answer and document-export entry points, then determine how private whole answers and private text portions could be represented; done means producing internal and public exports with the appropriate information included or excluded.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.