> 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.md).

# Workspace & Data Management

- [Overview](https://docs.geodin.com/workspace-and-data-management/workspace-and-data-management.md)
- [Connecting to a Database](https://docs.geodin.com/workspace-and-data-management/connecting-to-a-database.md): How GeoDin stores data in databases - desktop vs client/server types, the system/user hierarchy and naming rules, and how to create a database connection from the GeoDin object manager.
- [Managing Database Connections](https://docs.geodin.com/workspace-and-data-management/connecting-to-a-database/managing-database-connections.md): Editing, deleting and configuring database connections in the GeoDin object manager - the GeoDin.INI configuration keys, object-manager display options, and the system-tables reference.
- [Supported Database Types](https://docs.geodin.com/workspace-and-data-management/connecting-to-a-database/supported-database-types.md): The database backends GeoDin connects to - Client/Server via OLE-DB or FireDAC, and desktop MS Access - with per-platform drivers, GeoDin-to-DDL data type mappings and example connection strings.
- [Working with Projects](https://docs.geodin.com/workspace-and-data-management/working-with-projects.md)
- [Copying and Transferring Projects](https://docs.geodin.com/workspace-and-data-management/working-with-projects/copying-and-transferring-projects.md): Copying and transferring GeoDin projects - duplicating, exporting, and moving projects between databases.
- [Creating Objects](https://docs.geodin.com/workspace-and-data-management/creating-objects.md)
- [General Data](https://docs.geodin.com/workspace-and-data-management/creating-objects/general-data.md): General data entry for GeoDin objects - identifying information, location metadata, and project association.
- [Sample Data](https://docs.geodin.com/workspace-and-data-management/creating-objects/sample-data.md): Sample data - recording physical samples taken from objects with depth intervals and identifying details.
- [Well Design Data](https://docs.geodin.com/workspace-and-data-management/creating-objects/well-design-data.md): Well design data - casing, screens, backfill, and piezometer installation details for monitoring wells.
- [Data Management](https://docs.geodin.com/workspace-and-data-management/creating-objects/data-management.md): Data Management - the central method for entering general, layer, sample, well design, and sequence data for objects.
- [Working with Measurement Data](https://docs.geodin.com/workspace-and-data-management/working-with-measurement-data.md)
- [Data Sequences and CPT](https://docs.geodin.com/workspace-and-data-management/working-with-measurement-data/data-sequences-and-cpt.md)
- [Managing Documents](https://docs.geodin.com/workspace-and-data-management/managing-documents.md)
- [Document Organization](https://docs.geodin.com/workspace-and-data-management/managing-documents/document-organization.md): Document organization in GeoDin - how documents are stored, named, and grouped within projects and objects.


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.