floradanna

I am not sure this is an ideal process, because if an error occurs the user needs to go back to the source/sample table and re-select all samples. Moreover, by...

Just few comments to clarify the issue: * samples are already included in batch sharing permission; only samples that are linked to assays disappear form batch sharing permission GUI. So...

Maybe the reason could be that there is no Sample Type specified under "Registered Sample". I highlighted in red in the image below. 

oh, I see now. It is indeed unexpected behaviour then. We have to make clear what is shown by default and what is meant with "other projects" here.

@somathias @reutenauer when implementing the ISA-JSON compliance flag, we should make sure that it propagates to all ISA elements (study, assay, sample types, samples etc). This might help with the...

Another aspect to take into account is that it is not only about GUI. If the user type the following URL https://datahub-test.elixir-belgium.org/assays/58/edit directly , the user must be always redirect...

Investigation created via SP is associated with Project 1. User can edit associated Project 1 via "Manage Investigation" both from SP and default view. - if a second project is...

implement it as list in ISA-JSON comment

Test with #1547

Hi @froggypaule, apologies for the late response. Are you still in need of technical help? Please, let us know