# Field names and data types - minimal data submission

The following files are necessary for a minimum data deposition of simple data, such as those describing experiments where 'compound X has affinity (Ki) of Y uM in assay Z.'  For most depositors, this data model is sufficient to capture their data. Such depositors need only deposit their data using the files in this section. These must all be tab-separated files (.tsv).

Files which can be used to supply supplementary data about the files in the minimum data deposition are explained in the [Supplementary data file](/chembl-data-deposition-guide/file-structure/supplementary-data-files.md) section.  

Additional files required to deposit more complex data are found in the [Complex results sets](/chembl-data-deposition-guide/file-structure/supplementary-data-files/complex-results.md) section.

Comparatively large datasets may need splitting into subsets in order to ensure timely feedback and loading. We will let you know if this applies to your data. 

#### **Common data issues to beware of**

* Character fields **cannot contain newline characters**. Everything in a text field must be on a single line. 
* If there is no value for a field, **leave it blank**. Never use arbitrary placeholder values like `ASSAY_ORGANISM='no organism'`. 

**PLEASE NOTE: For ease of viewing the column headers have been formatted as rows.  When submitting data to ChEMBL the formatting should be rotated by 90 degrees so that the fields are column headers, and each row below is a data entry point.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://chembl.gitbook.io/chembl-data-deposition-guide/file-structure/field-names-and-data-types-minimal-data-submission.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.