> 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 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geodin.com/workspace-and-data-management/creating-objects/data-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.