@@ -51,12 +51,13 @@ The same data are presented in different views for different purpose:
- To check all imported data independently of their quality assessment status, views without a suffix are available for every table. These Views are read-only, for changing or deleting data, please use the aforementioned views.
At the top of every schemata are three support views starting with a underscore _.
- The _column_definition conatins comprehensive information about a columns properties regarding its description, data type, constraints or keys and should therefore serve as a tool for importing activities.
- The _controlled_vocabularies contains predefined column entries originally stored in hidden and only maintained by tethys_ca. They serve as foreign key for __import views and are marked as such in the _column_definition view. The reason to limit their creation rights lies in their low diversity but simultaneously high number of references, which therefore enables the tethys_ca to preserve data integrity from below.
- The _table_definition view contains information about all views and tables of its schema and should therefore enhance your knowledge about the database.
- The __column_definition conatins_ comprehensive information about a columns properties regarding its description, data type, constraints or keys and should therefore serve as a tool for importing activities.
- The __controlled_vocabularies_ contains predefined column entries originally stored in hidden and only maintained by _tethys_ca_. They serve as foreign key for __import_ views and are marked as such in the __column_definition_ view. The reason to limit their creation rights lies in their low diversity but simultaneously high number of references, which therefore enables the _tethys_ca_ to preserve data integrity from below.
- The __table_definition_ view contains information about all views and tables of its schema and should therefore enhance your knowledge about the database.
### Views in public
- View for data evaluation and extraction: In the schema _public_ quality checked data are combined to wide tables combining all collected information. They only miss columns which are recorded for data traceability, e.g. columns with the originally reported text strings, which were mapped on the controlled vocabularies.
- Views for data evaluation and extraction: The views, with the same name of the environmental compartments from which its data originates, conatin quality checked data, that was combined to wide tables displayng all collected information. They only miss columns which are recorded for data traceability, e.g. columns with the originally reported text strings, which were mapped on the controlled vocabularies.
- Views to support the quality assessment workflow: The two views __qa_awaiting_ and __rejected_data_ should provide an overview of not yet either quality assessed or corrected data. They aggregate information about data recently imported or unsuccessful quality assessed regarding its schema, view, number of rows ad its importer respectively its quality assesor.
## User rights management
User rights for working with the database depend on PostgreSQL roles. The following roles were defined:
