Please complete the following fields as applicable:
What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
3.1.1
Expected behaviour:
Fields that are intentionally hidden in the interface and so impossible to fill in should not appear in the json export of a plan.
Actual behaviour:
When exporting a plan in json format we can see fields like: "ethical_issues_exist":"unknown".
It gives the appearance off an incomplete plan and may be confusing to systems using RDA-DMP-Common-Standard and looking for these kinds off fields.
Steps to reproduce:
Go to a plan and export it in json format.
Please complete the following fields as applicable:
What version of the DMPRoadmap code are you running? (e.g. v2.2.0) 3.1.1
Expected behaviour: Fields that are intentionally hidden in the interface and so impossible to fill in should not appear in the json export of a plan.
Actual behaviour: When exporting a plan in json format we can see fields like: "ethical_issues_exist":"unknown". It gives the appearance off an incomplete plan and may be confusing to systems using RDA-DMP-Common-Standard and looking for these kinds off fields.
Steps to reproduce: Go to a plan and export it in json format.