'secured' status #165
-
When I submit a folder to the vault and is successfully secured, it gets the label 'secured'. When I add a new file to that folder in the research environment, the label 'secured' remains visible when the current contents are not secured in the vault. Should that label not disappear or specify something in the likes of 'current version not secured' as that specific folder contents is not secured (only a previous version of that folder is secured)? |
Beta Was this translation helpful? Give feedback.
Answered by
lwesterhof
Feb 13, 2024
Replies: 1 comment 3 replies
-
Any input? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a historical artifact. Originally a folder would still be locked after it was secured in the vault space as a data package. The user had to unlock the folder to start working on it again. This behaviour was later changed and a folder would be automatically unlocked after securing the data in the vault space.
Would it make sense to display the secured label as is, but remove it as soon as data in that folder is modified?