From 558a3afa563344aac034fa737aac12df2de106f4 Mon Sep 17 00:00:00 2001 From: Martin Weise <martin.weise@tuwien.ac.at> Date: Wed, 29 Jan 2025 18:50:35 +0100 Subject: [PATCH] Updated image Signed-off-by: Martin Weise <martin.weise@tuwien.ac.at> --- .docs/concepts/data-visibility.md | 31 +++++++++++++++++-------------- .gitlab/agents/dev/values.yaml | 2 +- dbrepo-auth-service/init/app.py | 2 +- 3 files changed, 19 insertions(+), 16 deletions(-) diff --git a/.docs/concepts/data-visibility.md b/.docs/concepts/data-visibility.md index ecb33cbfc7..31c6ca3682 100644 --- a/.docs/concepts/data-visibility.md +++ b/.docs/concepts/data-visibility.md @@ -11,34 +11,37 @@ subset of a database. In total there are four possible visibility settings that can be applied on database level and then at the subsequent levels (table, view, subset). We give two examples for better understanding: -!!! example "*Example*: Database that is hidden but certain views and subsets are visible" +!!! example "Example: Database that is hidden but certain views are visible" - Database Airquality has the settings to hide all data and schema by default. + Database *Airquality* has the settings to hide all data and schema by default. - * Table `sensor_measurements` + * Table `sensor` inherits the settings from the database by default and therefore is also **hidden**. Nobody can + read/write to this database by default. Only designated users that the database owner allows to read/write can do + so. + * View `v_sensor` inherits the settings from the database by default and therefore is also **hidden**. The database + owner wants the data to be visible to the public (anonymously), so he changes the settings to data=visible, + schema=hidden. Now everybody can see the data but not the table(s) that contain the data. #### Visible !!! info "Possible use-case: data publication supplement to an open-access publication" -Where the database's data and metadata is set to be *visible*. This means everything in the database (tables, views, -subsets) are visible by anyone from the public. +Where the resource's data and schema is set to be visible. #### Data-only !!! info "Possible use-case: private sensor measurements with timed embargo" -Where the database's data set to be *hidden* but the schema to be *visible*. This means everything in the database -(tables, views, subsets) are by default not visible by anyone from the public. You can however make specific views that -join tables and/or filter certain columns and apply a 14-day delay-embargo. - -<figure markdown> - -<figcaption>Figure 1: Public view that joins two private tables and applies a time-embargo</figcaption> -</figure> +Where the resource's schema visibility is hidden but the data is visible. #### Schema-only +!!! info "Possible use-case: publish data for reviewers before the final publication" + +Where the resource's data visibility is hidden but the schema is visible. + #### Draft -!!! info "Possible use-case: project data storage before publication" \ No newline at end of file +!!! info "Possible use-case: project data storage before publication" + +Where the resource's data and schema visibility is hidden. It will not be findable even in the search. \ No newline at end of file diff --git a/.gitlab/agents/dev/values.yaml b/.gitlab/agents/dev/values.yaml index da48b95f4e..70ada3ca20 100644 --- a/.gitlab/agents/dev/values.yaml +++ b/.gitlab/agents/dev/values.yaml @@ -28,7 +28,7 @@ authservice: secret: MUwRc7yfXSJwX8AdRMWaQC3Nep1VjwgG setupJob: image: - name: registry.datalab.tuwien.ac.at/dbrepo/auth-service-init:1.6.3rc0 + name: registry.datalab.tuwien.ac.at/dbrepo/auth-service-init:1.6.3rc1 persistence: enabled: true diff --git a/dbrepo-auth-service/init/app.py b/dbrepo-auth-service/init/app.py index 270e959fec..f22541ba55 100644 --- a/dbrepo-auth-service/init/app.py +++ b/dbrepo-auth-service/init/app.py @@ -46,7 +46,7 @@ def save(user_id: str) -> None: database=os.getenv('METADATA_DB', 'dbrepo')) cursor = conn.cursor() cursor.execute( - "INSERT IGNORE INTO `mdb_users` (`id`, `username`, `email`, `mariadb_password`, `is_internal`) VALUES (?, ?, LEFT(UUID(), 20), PASSWORD(LEFT(UUID(), 20)), true)", + "INSERT IGNORE INTO `mdb_users` (`id`, `username`, `mariadb_password`, `is_internal`) VALUES (?, ?, PASSWORD(LEFT(UUID(), 20)), true)", (user_id, system_username)) conn.commit() conn.close() -- GitLab