isabella232 / tech.datopian.com

Datopian are experts in data management. This is an overview of our technology.

heroImage	heroText	tagline	pageClass	footer
https://playbook.datopian.com/img/datopian-dark-logotype.svg	Datopian Engineering	Experts in data management	home	Copyright © 2016-present Datopian

Datopian Tech 👩‍💻

We are experts in data management and engineering

This is an overview of our technology

Data Management Systems

A Data Management System (DMS) is a framework. It can be used to create a variety of solutions such as Data Portals, Data Catalogs, Data Lakes etc. We have developed two DMS stacks that share a set of underlying core components:

• CKAN: the open source data management system we created in 2007 and that we continue to develop and maintain. The main information on CKAN is at https://ckan.org/. Here we have some specific notes on how we develop and deploy CKAN as well as our thoughts on the next generation of CKAN (v3).
• DataHub: our version of a next generation of CKAN that powers DataHub.io. DataHub and CKAN v3 share many of the same core components. We are actively working on a DataHub v2 and an outline can be found here https://github.com/datopian/datahub-next

Solutions

You can use a DMS to build many kinds of specific solutions

• Data Portals are gateways to data. That gateway can be big or small, open or restricted. For example, data.gov is open to everyone, whilst an enterprise "intra" data portal is restricted to its personnel.
• Data Catalog: see https://ckan.org/
• Metadata manager: see Publishing
• Data Lake: you can use a DMS to rapidly create a data lake using existing infrastructure. For example, using the DMS' catalog and storage gateway with existing cloud storage and data processing capabilities.
• Data Engineering: you can use components of the DMS to rapidly create, orchestrate and supply data pipelines.

Features

A DMS has a variety of features. This section provides an overview and links to specific feature pages that include details of how they work in CKAN and CKAN v3 / DataHub.

:::tip There are many ways to break down features and this is just one framing. We are thinking about others and if you have thoughts please get in touch. :::

• Discovering and showcasing data (catalog and presenting)
• Views on data including visualizing and previewing data as well Data Explorers and Dashboards
• Publishing data
• Data API DataStore
• Permissions and Authentication
• Versioning
• Harvesting

Components

A DMS has the following key components:

• HubStore
• Data Flows and Factory
  • Loading to DataStore
• Storage
  • Blob Storage
  • Structured Storage - see DataStore

https://coggle.it/diagram/Xiw2ZmYss-ddJVuK/t/data-portal-feature-breakdown

<iframe width='853' height='480' src='https://embed.coggle.it/diagram/Xiw2ZmYss-ddJVuK/b24d6f959c3718688fed2a5883f47d33f9bcff1478a0f3faf9e36961ac0b862f' frameborder='0' allowfullscreen></iframe>

Frictionless

The Frictionless approach to data. See https://frictionlessdata.io/

Our team created this whilst at Open Knowledge Foundatioin and continue to co-steward it.

OpenSpending

https://openspending.org/

Developer Experience

Service Reliability Engineering (SRE) and Developer Experience (DX) for our CKAN cluster technology.

• Developer Experience
• DX - Deploy
• DX - Cluster

Old cluster

• Deploy in old cluster
• Exporting from CKAN-Cloud
• Cloud - start on CKAN cloud documentation

Research

• Data Frames and what would a JS data frame library look like
• Dataset Relationships

Miscellaneous

• Glossary »
• Notebook -- our informal blog »