Check the Locked state about jatos

[kristian-lange]

Yes, this is on purpose and actually requested by the BUPO (you!).

On Tue, Nov 11, 2014 at 5:56 PM, elisafilevich [email protected]
wrote:

In the MechArg (maybe changed in the OSA) if you locked the study, you
can't try it. That's not great, but it's understandable. If it's on purpose
we should state it.

—
Reply to this email directly or view it on GitHub
#36.

[elisafilevich]

not even try? Ok, but as I said this makes sense, we just have to document it in the wiki.
closed

On Nov 11, 2014, at 6:33 PM, kristian-lange [email protected] wrote:

Yes, this is on purpose and actually requested by the BUPO (you!).

On Tue, Nov 11, 2014 at 5:56 PM, elisafilevich [email protected]
wrote:

In the MechArg (maybe changed in the OSA) if you locked the study, you
can't try it. That's not great, but it's understandable. If it's on purpose
we should state it.

—
Reply to this email directly or view it on GitHub
#36.

—
Reply to this email directly or view it on GitHub.

[kristian-lange]

The reason for this behaviour is that if one is doing the study, he is
creating new results and thus changing the data. But we don't want allow
data change.

On the other side, we could allow to 'show' studies. It generates results -
but doesn't change the original study or components data. Result data are
separated from the study or component data. So it shouldn't be a problem.

On Tue, Nov 11, 2014 at 6:33 PM, Kristian Lange [email protected]
wrote:

Yes, this is on purpose and actually requested by the BUPO (you!).

On Tue, Nov 11, 2014 at 5:56 PM, elisafilevich [email protected]
wrote:

In the MechArg (maybe changed in the OSA) if you locked the study, you
can't try it. That's not great, but it's understandable. If it's on purpose
we should state it.

—
Reply to this email directly or view it on GitHub
#36.

[elisafilevich]

Yes, yes, I see this. We make better decisions than ourselves.