-
Notifications
You must be signed in to change notification settings - Fork 24
7.2. User Status, Categories and Access Permissions
Users have one of the following status: unregistered, pre-registered, or registered. A registered user is one who went through the process of signing up for HADatAc and confirming the authenticity of her/his email address. A user is allowed to register if the user was pre-registered by an administrator. A user is said to be unregistered if the user is neither pre-registered nor registered.
Users have categories as described below. For instance, a registered user is capable of logging into the system and owning data. An admin user has the permission of granting admin permission to any registered user.
Master User: One default administration user must be created during HADatAc configuration (see Section 2.1.8). This is a special case of an Administration User as described below.
Administration (admin) User: This is the user who can pre-register new users and grant admin status to other registered users. Right after installation, the Master User is the only user with admin permission, and consequently the only user capable of pre-registering other users. Once users complete their registration including the verification of their email addresses, admin users can grant new users with admin permission, which would enable any of these new administration users the pre-register new users.
Data Owner: Every registered user is considered a data owner, whether the user actually owns or not any data in the data repository. A data owner is capable of the following: uploading data and metadata into the system; recording deployment metadata; annotating data with metadata; setting the permission of who has the right of accessing their data; deleting their data from the system.
Guest User: Every user is considered unregistered until the user logs into the system. Unregistered users can access and download publicly available data. Unregistered users cannot upload and own data in the HADatAc system.
One needs to be a HADatAc administrator to pre-register users in HADatAc. Also, the pre-registration requires a SMTP mailer to be set so that HADatAc can use email exchange to authenticate users (see Session 2.1.2).
The pre-registration consist of a manager creating a new user that includes the email of the new user. This is accomplished by going to Home > User Management > Pre-Register New User, and filling out the pre-registration form. A user is said to be a pre-registred once one new account is created for the user.
A registration becomes full registration once the new user sign up using the same email address that was pre-registered, and he/she authenticates the account by replying a verification email sent by HADatAc to the pre-registered email address.
Please see instructions in Section 2.1.8.
Users having admin privilege can perform backup and recovery operations on user graph (e.g. user profiles, access levels, etc) and authentication (e.g. accounts, encrypted passwords, security roles, etc) when system upgrade necessitates this. To backup, go to the Manage Users page and then you will see an button called Backup User Authentication for exporting a .json file containing required information for recovering later, and another button called Backup User Graph for exporting a .ttl file containing the whole user graph. To recover, in the same page, use the file upload panel called Load User Graph from turtle first to upload the previously saved .ttl file for recovering the user graph and then use another file upload panel called Load User Authentication from json to upload the previously saved .json file for recovering the user authentication.
Copyright (c) 2019, HADatAc.org
-
Installation
1.1. Installing for Linux (Production)
1.2. Installing for Linux (Development)
1.3. Installing for MacOS (Development)
1.4. Deploying with Docker (Production)
1.5. Deploying with Docker (Development)
1.6. Installing for Vagrant under Windows
1.7. Upgrading
1.8. Starting HADatAc
1.9. Stopping HADatAc -
Setting Up
2.1. Software Configuration
2.2. Knowledge Graph Bootstrap
2.2.1. Knowledge Graph
2.2.2. Bootstrap without Labkey
2.2.3. Bootstrap with Labkey
2.3. Config Verification -
Using HADatAc
3.1. Initial Page
3.1.1. Home Button
3.1.2. Sandbox Mode Button
3.2. File Ingestion
3.2.1. Ingesting Study Content
3.2.2. Manual Submission of Files
3.2.3. Automatic Submission of Files
3.2.4. Data File Operations
3.3. Manage Working Files 3.3.1. [Create Empty Semantic File from Template]
3.3.2. SDD Editor
3.3.3. DD Editor
3.4. Manage Metadata
3.4.1. Manage Instrument Infrastructure
3.4.2. Manage Deployments 3.4.3. Manage Studies
3.4.4. [Manage Object Collections]
3.4.5. Manage Streams
3.4.6. Manage Semantic Data Dictionaries
3.4.7. Manage Indicators
3.5. Data Search
3.5.1. Data Faceted Search
3.5.2. Data Spatial Search
3.6. Metadata Browser and Search
3.7. Knowledge Graph Browser
3.8. API
3.9. Data Download -
Software Architecture
4.1. Software Components
4.2. The Human-Aware Science Ontology (HAScO) -
Metadata Files
5.1. Deployment Specification (DPL)
5.2. Study Specification (STD)
5.3. Semantic Study Design (SSD)
5.4. Semantic Data Dictionary (SDD)
5.5. Stream Specification (STR) -
Content Evolution
6.1. Namespace List Update
6.2. Ontology Update
6.3. [DPL Update]
6.4. [SSD Update]
6.5. SDD Update -
Data Governance
7.1. Access Network
7.2. User Status, Categories and Access Permissions
7.3. Data and Metadata Privacy - HADatAc-Supported Projects
- Derived Products and Technologies
- Glossary