---
title: "Project checklist and best practices"
description: "You have decided to go along and you have just spun up your Project! As the first users of our platform we"
url: https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/tutorials-project-checklist
lang: it
lastUpdated: 2026-09-14
---
> For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/it/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/it/llms-full.txt.

# Project checklist and best practices

## Objective

You have decided to go along and you have just spun up your Project! Great!

What's next? Where to start?

As the first users of our platform we, have accumulated several years of experience in carrying out data Projects. We have curated a list of best practices, learned through our services practice over the years, which we are excited to share with you.

Projects on **Data Platform** allow you to gather a team and work together on the same data Project.
You can start with some basic file uploading and seamlessly switch to near real-time data processing, keeping your methodology and easily scaling as your Project grows.\
So start, iterate, and grow your Project step-by-step: your Project will meet your growing needs.

A typical Project often goes through the following **main milestones**:

- A quick [checklist](#checklist) on the use case and Project scope
- Give your [teammates access](#user-management)
- Do iteratively, and as needed:
  - Adapt the [Project resources](#manage-resources) to your needs
  - Define [Data Sources](#collect-data)
  - Design [Tables](#organize-data)
  - Build [Actions and Workflows to process data](#process-data)
  - Build [Queries and Dashboards](#write-queries) to visualize your data
  - Build [Apps & API](#build-applications)
  - Give [access to end-users](#give-access-to-your-application)
  - [Monitor Jobs & Deployments](#monitor)
  - Get feedback

## Checklist

:::warning
We recommend you go through our [Getting Started guide](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-getting-started.md) so you get a good understanding of the key Project components and Data Platform concepts.
:::

Before take-off, here are some basic checks on your use case scope and agenda that we share with you:

- Data sources
  - Which data do you need?
  - Is data available? How? Is data history available?
  - Storage sizing: how much data volume and compute will this Project require?
  - How often should it be refreshed?
- Describe your own personal data book:
  - The "data story": where does it come from? How has it been produced? Your data flow history?
  - Data fields: what does it mean? what is it for?
  - Detailed Business Rules (about data)
  - KPI: how to compute them? what do they mean?
- What is to be produced?
  - UX Storyboard
  - API for external use
  - Exporting files
- Risk detection and mitigation
  - What could go wrong? What is intricate in your Project?
  - Identify/anticipate possible bottlenecks or hurdles
- Identify & Leverage short iterations
- View and check data as early as possible
- Release early, release often!

## User Management

Projects make it easy to work as a team on a Project. There are two levels of team management:

- [Members](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/manage-organizations.md) of your Data Platform organization are your teammates. They have created a Data Platform account
- [Users](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-users.md) in your Project are either teammates working on this Project, or end-users of your API and apps
  - Members of an organization are automatically added as users in all Projects in this organization. Permissions must be granted manually to non-admins.

After [adding your team to your organization](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/manage-organizations.md), check [how to give them access rights in each Project's **Identity Access Manager**](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-users.md#manage-project-iam-users) according to their skills and permissions.

Your end-users access rights are also managed in the Identity Access Manager.

## Manage resources

Projects were designed from scratch to scale easily as the requirements of your data Project evolve. You can independently **scale horizontally and vertically** any component of your choice in just a few clicks, for example your [apps](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-app-services-apps.md).

Each component in your Project will consume [resources](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/manage-pricing.md) when it is actively running (either through a job or a deployment).

:::info
Even when it is idle, your Project uses a handful of DPUs by default. You can manage this amount in the [Control Center](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/control-center-monitoring.md#infrastructure-monitoring-panels).
:::

[<span aria-hidden="true">↪</span> Learn more about resource consumption](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/manage-pricing.md)

## Collect data

Take a look at [available connectors](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/connectors-sources-configure.md) and remember that it is always possible to write a [custom action](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-actions-custom.md) to do whatever is not already possible through the interface.

If you need to manage files in your Project, we recommend using the [Lakehouse Manager buckets](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-buckets.md):

- organize buckets either **by topic** (referentials for instance), **by type of processing** or **by providers** depending on your needs
- within a bucket, you can use **folders** to better organize your files
- when defining a [source](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-connectors-sources.md), the _Data Platform Buckets_ connector allows you to select a bucket then select files as sources
- if you have multiple files in the same bucket/folder:
  - if each file is different, you can [analyze](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-connectors-analyzer.md) them separately and use them as a source for [Data Processing Engine actions](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-dpe-actions.md)
  - if all files need to be processed the same way: you just need to select one to **analyze**, you will use it as a source and [use segmentation over a set of files](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/tutorials-segmentation-files.md) to process them
- check out [how to send files to the buckets with S3<sup>1</sup>-compatible tools](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/tutorials-bucket-s3-access.md) to integrate in your in-house process

## Analyze data and design blueprint rules

Once you have set up your sources, take the time to [analyze](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-connectors-analyzer.md) them and configure basic source cleaning rules called [blueprint rules](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/connectors-analyzer-blueprint-rules.md). This can help fix some common issues such as:

- date formatting
- number formatting
- clean up strings
- skip incomplete lines
- ... and much more

In the long run, this step will save you a lot of time!

## Organize data

The [Tables page](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-tables.md) is where you [prepare your database schema](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/getting-started-organize-data.md#organize-your-data-in-tables).

### Tables

- We recommend using a prefix depending on the type of data:
  - `ref_`: for referentials and stable data, without any temporal information
  - `raw_`: data imported _as is_ with minimal changes. This can be used to trace back data issues
  - `prm_`: primary tables, i.e. improved quality data from `raw_`
  - `fct_`: consolidating `facts` from several `prim_` and `ref_` in a common `scale`
  - `agr_`: aggregation of data on a different `scale` (for instance `datetime` to `date` or `date` to `year`)
    - they are usually designed to optimize queries
    - build one `agr_` table per **scale granularity** adding all needed attributes
    - then add attributes names that indicate granularity (`agr_station_yearmonth`, `agr_movie_date`)
  - `tmp_`: temporary tables used for processing (mark them as **not queryable**)
  - `mlm_`: for tables used in a machine learning model
- Give clear names that describe what one row of data represents
- Define [indexes](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-manage-tables.md) to speed up data operations

### Attributes

Use [Attributes tab](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-attributes.md) to review all attributes, in which tables they are used, which DPE Actions uses it, etc.

Here are some best-practices about attributes (i.e. field names in tables):

- attribute type: choose between _dimension_ or _measure_
  - _dimension_: qualitative information that can be scaled by, filtered by, etc but not summed.
  - _measure_: numerical information that can, most of the time, be summed, counted, averaged, etc.
- attribute naming:
  - use a _prefix_ to distinguish them (e.g. `client_`, `fb_`, `site_`)
  - name `measure` attributes so they give a hint on a temporal window:
    - `_nb_` : number for that day
    - `_total_` : value for this day
    - `_diff_` : difference from previous day
    - ...
  - clearly indicate what it is (i.e. `_amount_`, `_ticket_`, `_fans_`)
  - give unit of measure if not obvious (i.e. `_g`, `_kg`, `_wh`, `_kwh`, `_eur`, `_usd`)

:::warning
It is very important to **use the same attribute name and type** across all tables to **name the same piece of information**. Thus when playing a query in the [Analytics Manager](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-analytics-manager.md), it dynamically checks the most suitable object for required fields.
:::

### Explorer

Use [Explorer](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-explorer.md) to quicly check table contents.

## Process data

The [Data Processing Engine (DPE)](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-dpe.md) is used to build [actions](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-dpe-actions.md) which are the heart of your physical data flow. They can run alone or organized into groups named [workflows](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-workflows.md).

### Actions

Make sure you have a deep look at provided [actions types](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-dpe-actions.md).

If you need to go further, start writing a [Custom Action](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-actions-custom.md) using our [SDK](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-developers-python-sdk.md) to interact with the rest of your Project leveraging **Python** or **PySpark**.

:::info
Use the [notebooks](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-notebooks.md) to quickly prototype a Custom Action, then export it to the Data Processing Engine
:::

- For [Aggregate Actions](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-actions-aggregate.md):
  - `scale`: must be the same granularity as the primary key of the destination table
  - **double check your rules for joining tables**: this is the main source of errors
- Set **log level** appropriately during lifecycle (i.e. `debug` if needed, `info` otherwise)
- Use **Auto flush all** to flush all caches and visualize the updates brought by the action on the datasets

### Use Repositories and Versions

As your Project grows, don't forget you can organize actions in [repositories using versions](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-actions-manage.md#manage-actions) according to your needs.

:::info
Actions are listed in alphabetical order: you can add prefixes such as numbers to better organize them.
:::

### Use segmentation

To leverage the full power of the Data Platform's DPE, use [Segmentation](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-jobs-segmentation.md) to parallelize computing tasks at an action's level.

### Use a perimeter

To limit an action or a workflow on a subset of your data, e.g. for last 30 days, use the [Perimeter](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-jobs-perimeter.md) option.

## Write queries

Use folders and repositories to organize saved [queries](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/analytics-manager-queries.md) in the [Analytics Manager](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-analytics-manager.md).

For instance:

- _Data Quality_: queries to check Data Quality
- _Data Analysis_: queries to view basic features
- _App-xxx_: prepare queries to use inside your Application
  - This allows you to update the database schema and the queries without having to deploy a new app version
  - Give clear, descriptive names to your queries

### Query Engine

- unified SQL Engine over multiple databases
- [Explorer](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-explorer.md) in Lakehouse Manager
- [Build and Publish Dashboards](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/analytics-manager-dashboards.md)
- [Access from tools like PowerBI](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-connectors-consumers.md)

## Build applications

Take the time to understand [Application Services](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-app-services.md) and the possible [settings](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-deploy.md#application-settings).

### Helpful tips

- Design a Storyboard before starting your Project
- Make sure your `dynamic parameters` are present in all tables you need to request
- Use **object's label** in **Tables** for automatic translation
- Leverage [Formatters](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-formatter.md) and [Translations](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-translations.md)
- Leverage [Style templates](https://docs.dataplatform.ovh.net/#/en/technical/sdk/app/charts/template) to streamline your Apps development

A typical application development lifecycle is:

1. Design a storyboard

- check data is available
- identify `dynamic parameters`
- identify needed _charts_ and _custom components_

2. Analytics Manager: prepare and check needed queries
3. Implement a first version in the UI

- set up `dynamic parameters`
- set up `dashboards` and `menus`
- set up available `charts` as needed
- set up `dictionaries`, `formatters` and `translations`

4. Improve that version

- Adapt CSS as needed
- Leverage [Style templates](https://docs.dataplatform.ovh.net/#/en/technical/sdk/app/charts/template)
- Implement your own [custom chart](https://docs.dataplatform.ovh.net/#/en/technical/sdk/app/custom-chart) or [custom component](https://docs.dataplatform.ovh.net/#/en/technical/sdk/app/custom-component) as needed

5. Test and iterate again
6. Give access to more users

### Customize your application further

Application is based upon the ReactJS framework. We strongly recommend you go through our [guide on advanced app customization](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/tutorials-app-development.md).

### Git repositories

It is usually recommended to [synchronize your application with a Git repository](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-git-integration.md) and deploy two applications:

- `my-develop`: synchronized with your **develop** branch
- `my-master`: synchronized with your **master** branch

### Custom Domain Names

By default, your application is available at :

```yaml
https://my-project.eu.dataplatform.ovh.net/my-develop-app/
```

You may change it easily in the [App's settings](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-deploy.md#application-settings) to be :

```yaml
https://my-beautiful-app.eu.dataplatform.ovh.net/
```

If you need further customization, you may register [your own domain and provide your own SSL certificates](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/app-services-apps-custom-domain.md) :

```yaml
https://my-beautiful-app.example.com/
```

## Give access to your application

By default, every `Application` created in **Application Services** has its counterpart in the **Identity Access Manager**.

- [Application Services](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-app-services.md)
  - it manages the instance that will be deployed and run
  - it is linked to an **Identity Application Manager's Application**
  - it will use that **IAM App** configuration about **Auth Providers**, **Users**, etc
- [Identity Access Manager](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-application-authentication.md), you can define:
  - Logo
  - Application Title
  - Allowed Authentication Provider

Add all the [end-users](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-users.md) that will have access to your application (using [authentication providers](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-auth-providers.md) if your company has a SSO provider), and use [roles](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-roles-conditions.md) and [groups](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/iam-groups.md) to manage data access control.

## Front API

Default Front API checks authentication, process App's requests adding **dynamic parameters** and **implementing ACLs**.

Here are some scenarios where custom API is needed.

- Implement transformers
- Implement custom "evolution"
- Implement complex ACL

## Monitor

[Control Center](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-control-center.md) gives access to:

- [monitoring](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/control-center-monitoring.md) resource usages and health
- [logs of all deployments and jobs](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/control-center-logs-explorer.md)
- [creating alerts on deployments and jobs](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/landing-page-control-center-alerting.md)
- a complete view of all [jobs executions and scheduling](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/control-center-jobs-central.md) at Project and Organization's level

## Project Backup

### Project Configuration

Learn more about how to [backup and restore your Project configuration](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/tutorials-export-import-config.md).

### Exporting data

Using a [Data Processing Engine custom Action](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/dpe-actions-custom.md), you can export all your data to a [bucket](https://docs.ovhcloud.com/it/guides/public-cloud/data-platform/lakehouse-manager-buckets.md) in the Lakehouse Manager.

## Go further

If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/it/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.

Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated [Discord channel](https://discord.gg/ovhcloud).

If you need support with your OVHcloud services, create a request in our [Help Centre](https://help.ovhcloud.com/csm?id=csm_get_help).

Join our [community of users](https://community.ovhcloud.com/).

1
: S3 is a trademark of Amazon Technologies, Inc. OVHcloud's service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.