-
Notifications
You must be signed in to change notification settings - Fork 2
Datahub Data Initiative
The DataHub makes it easy for multiple teams, labs or users to get access to Storage, Databases, Data Science and Analytical tools:
- Storage accounts: A Data Project includes a storage explorer to upload/download files with a friendly user interface.
- Databricks integration: The Data Project has a direct link to Databricks workspaces and also simplifies the mounting of the storage account for the notebooks
- Power BI integration: The integration implements NRCan's governance model and connects users directly to their workspaces and key reports.
- SQL Server: A SQL Server can be associated to a project and the connection details will be directly available to the users.
- PostgreSQL: Postgresql servers can also be linked and the project tools can generate the associated Azure token for integrated authentication.
- Data Sharing: A simple workflow lets users select a file, and request data sharing (see Data Sharing for more details)
- User onboarding: Project administrators can invite other users to their project(s)
The Data Projects workflow let users request access to:
- Project specific Databricks workspace (*)
- Project specific WebForm
- Project specific PowerBI workspace (*)
Access request to resources is open to all NRCan users.
If a user needs access to one of those service it can result in the following two workflows (only for resources *):
- Workflow 1: Request for resource creation. This request will be reviewed by the DataHub team and if approved, a resource will be added to the system Terraform and deployed on the next system update.
- Workflow 2: Request access to an existing resource. If approved by the project administrators, the DataHub system automation will add the user to the resource with limited access. Additional ACL for the resource access need to be managed within the resource itself.
Each data project has a list of project owners. That list of project owners is maintained by the project owners of the DataHub project tracker which includes the key members of DataHub.
The project owners consists of a list of Azure usernames and lets user approve other user access to a resource (see list above).
Each initiative only would have two statuses: Opened or Closed. The sub-status would be determined from the dates in the Engagement table.
- Opened
- On Hold - we expect an engagement to start.
- Active - aka we have an engagement open (could be queried)
- Support - engagement is completed or no engagement required. We are avail to respond to Assyst tickets.
- Closed
Each initiative that is in Support mode should have a tile in tools for access to Assyst. If possible, we should see if we can prefill some of the parameters.