> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/workspace-and-data-management/creating-objects/data-management.md).

# Data Management

Data Management - the central method for entering general, layer, sample, well design, and sequence data for objects.

The **Data Management** method is the central interface for entering and editing data for an object (borehole, sample point, monitoring well). It presents the available data tabs based on the object type, and is launched by double-clicking the **Data management** method icon on a selected object.

## Reference: Data tabs

Typical tabs include:

* [General Data](/workspace-and-data-management/creating-objects/general-data.md) - identifying information, coordinates, project association
* Layer Data - geological layer descriptions, stratigraphy, layer-by-layer entry
* [Sample Data](/workspace-and-data-management/creating-objects/sample-data.md) - physical samples and their depth intervals
* [Well Design Data](/workspace-and-data-management/creating-objects/well-design-data.md) - casing, screens, backfill, piezometer details
* Data Sequences - continuous depth-indexed measurements (CPT, geophysical logs)

For the comprehensive object operations workflow - creating, editing, validating, importing, exporting, and reporting object data - see [**Object Operations Reference**](/object-types/object-operations-reference.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.geodin.com/workspace-and-data-management/creating-objects/data-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.