|
1 | | -# Inserting data into DebiAI |
| 1 | +# Inserting Data into DebiAI |
2 | 2 |
|
3 | | -Being a data visualization application, providing the project data to DebiAI is a required step. |
| 3 | +As a data visualization application, providing project data to DebiAI is a required step. |
4 | 4 |
|
5 | 5 | ## Requirements |
6 | 6 |
|
7 | | -### A DebiAI instance |
| 7 | +### A Running DebiAI Instance |
8 | 8 |
|
9 | | -You will need to have a running DebiAI instance to insert you project data to. (see [Installation](../introduction/gettingStarted/installation/README.md)) |
| 9 | +You need a running DebiAI instance to insert your project data. (See [Installation](../introduction/gettingStarted/installation/README.md)) |
10 | 10 |
|
11 | | -### Data |
| 11 | +### Data Format Requirements |
12 | 12 |
|
13 | | -The data you want to analyze with DebiAI will need to respect a specific format. |
| 13 | +The data you want to analyze in DebiAI must follow a specific format. |
14 | 14 |
|
15 | | -- **CSV like format** |
| 15 | +- **CSV-like Format** |
16 | 16 |
|
17 | | - If your data can be represented in an array like format, adding them to DebiAI will be easy. The data can also support different levels of nesting (see [unfolding columns](../dashboard/unfolding/)). |
| 17 | + If your data is structured in an array-like format, adding it to DebiAI is straightforward. DebiAI also supports different levels of nesting (see [Unfolding Columns](../dashboard/unfolding/)). |
18 | 18 |
|
19 | | -- **Data types** |
| 19 | +- **Supported Data Types** |
20 | 20 |
|
21 | 21 | DebiAI supports the following data types: |
22 | 22 |
|
23 | 23 | - `num`: numerical values |
24 | 24 | - `str`: string values |
25 | 25 | - `bool`: boolean values |
26 | | - - `array`: array of values (see [unfolding columns](../dashboard/unfolding/)) |
27 | | - - `dict`: dictionary of values (see [unfolding columns](../dashboard/unfolding/)) |
| 26 | + - `array`: arrays of values (see [Unfolding Columns](../dashboard/unfolding/)) |
| 27 | + - `dict`: dictionary objects (see [Unfolding Columns](../dashboard/unfolding/)) |
| 28 | + - `None`: missing values |
28 | 29 |
|
29 | | - Dates are supported by DebiAI, you can provide them as strings. |
| 30 | + Dates are supported and should be provided as strings. |
30 | 31 |
|
31 | | -- **Missing values** |
| 32 | +- **Handling Missing Values** |
32 | 33 |
|
33 | | - DebiAI supports data with missing values (`None`, `NaN` or `null` values) since 0.29.0. The missing values will be displayed as `null` by widgets that support them. Statistics about missing values will be displayed in the dashboard. |
| 34 | + Since version 0.29.0, DebiAI supports missing values (`None`, `NaN`, or `null`). Widgets that support missing values will display them as `null`, and statistics about missing data will be available in the dashboard. |
34 | 35 |
|
35 | | -- **Samples size** |
| 36 | +- **Sample Size Limitations** |
36 | 37 |
|
37 | | - It is not recommended to provide more than 2.000.000 samples, as it will take a long time to process. We are working on improving this limit. |
| 38 | + Providing more than **2,000,000 samples** is not recommended, as it may significantly increase processing time. We are actively working on improving this limitation. |
38 | 39 |
|
39 | | -## There is currently two ways to insert data into DebiAI: |
| 40 | +## Methods for Inserting Data into DebiAI |
40 | 41 |
|
41 | | -- ### [Python module](pythonModule/README.md#python-module) |
| 42 | +There are currently two ways to insert data into DebiAI: |
42 | 43 |
|
43 | | -The main way to add provide the project data to the application is through the DebiAI Python module. |
44 | | -The module was designed to be used directly in your Python workflow, to add model results directly after its evaluation for example. |
| 44 | +<img src="/debiai_architecture.png" alt="DebiAI architecture" width="400"/> |
45 | 45 |
|
46 | | -- ### [Data providers](dataProviders/README.md#data-providers) |
| 46 | +<LinkableChoices :choices="[ |
| 47 | + { |
| 48 | + title: '1. Data Providers', |
| 49 | + description: 'Make DebiAI directly access your project data', |
| 50 | + imageLink: '/getStarted/data.svg', |
| 51 | + elementIdDestination: '_1-data-providers-recommended' |
| 52 | + }, |
| 53 | + { |
| 54 | + title: '2. Python Module', |
| 55 | + description: 'Directly insert data from your Python workflow', |
| 56 | + imageLink: '/install/python.svg', |
| 57 | + elementIdDestination: '_2-python-module' |
| 58 | + } |
| 59 | + ]" |
| 60 | +/> |
47 | 61 |
|
48 | | -A DebiAI data provider is a REST service that will expose your project to DebiAI. |
49 | | -DebiAI will directly ask for the data from your project making the data loading process very quick and customizable. Unlike the DebiAI Python module, the provided data won't have to be duplicated in the DebiAI application. |
| 62 | +### **1. [Data Providers](dataProviders/README.md#data-providers) (Recommended)** |
50 | 63 |
|
51 | | -Making a data provider is the most efficient way to make your project data accessible to DebiAI, no matter the data base that your project is using. |
| 64 | +A **DebiAI Data Provider** is a service that exposes your project data to DebiAI. This method allows DebiAI to directly retrieve metadata from your project, making data loading **fast** and **customizable**. |
| 65 | + |
| 66 | +✅ **Key benefits**: |
| 67 | + |
| 68 | +- No need to upload or duplicate data in DebiAI. |
| 69 | +- Always up to date with the latest project data. |
| 70 | +- Works with any files or databases used by your project. |
| 71 | + |
| 72 | +⚠️ **Limitations**: |
| 73 | + |
| 74 | +- Requires a custom implementation to expose your data. |
| 75 | + |
| 76 | +To simplify implementation, you can use the [DebiAI Data Provider Python module](https://github.com/debiai/easy-data-provider). |
| 77 | + |
| 78 | +### **2. [Python Module](pythonModule/README.md#python-module)** |
| 79 | + |
| 80 | +You can also insert data directly from your Python workflow using the [DebiAI Python module](https://github.com/debiai/py-debiai). This is useful for integrating new data or model results immediately after generation. |
| 81 | + |
| 82 | +✅ **Key benefits**: |
| 83 | + |
| 84 | +- Easier to implement. |
| 85 | + |
| 86 | +⚠️ **Limitations**: |
| 87 | + |
| 88 | +- Requires data duplication in DebiAI, increasing load time. |
| 89 | +- Data updates must be done manually. |
| 90 | + |
| 91 | +While easier to implement, this method is less efficient than using a Data Provider. |
| 92 | + |
| 93 | +--- |
| 94 | + |
| 95 | +By following the recommended **Data Provider** approach, you ensure an optimized project data integration with DebiAI. |
0 commit comments