search

inab / benchmarking-data-model

OpenEBench Benchmarking Data Model repository
Creative Commons Attribution Share Alike 4.0 International
2 stars 7 forks source link

Review accepted values of `visibility` in several concepts #122

Closed jmfernandez closed 1 year ago

jmfernandez commented 3 years ago

Review accepted values of visibility in the data model - visibility level of participant is not being used at the moment and is not planned to be used in the future.

jmfernandez commented 3 years ago

I have removed participant as a possible value for visibility in Dataset in f6f737cdaaefacddd96d0a60fcfc5cb8a33d284b.

But I'm keeping this issue open, because I think this attribute should be a managed one, one which should not be changeable through a document update.

Indeed, it should be an attribute inherent to any entry in the database, not only to Dataset entries. And it should be visible through @visibility. What do you think @redmitry @jlgelpi ?

jmfernandez commented 1 year ago

We have discarded the idea of an additional @visibility attribute. We have been developing and updating these days the privileges matrix, at https://gitlab.bsc.es/inb/elixir/openebench/openebench-security-docs/-/blob/master/roles/README.md . Now other components, like the Keycloak plugin, which take into account both privileges and dataset visibility have to be developed to fulfill it.