> For the complete documentation index, see [llms.txt](https://whiteklay.gitbook.io/virtual-data-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whiteklay.gitbook.io/virtual-data-assistant/how-to-guides/data-catalog/data-discovery.md).
# Data Discovery
VDA offers powerful and comprehensive data exploration capabilities, allowing users to efficiently locate and access the data they need. This functionality supports searches based on various criteria, including table names, column names, database names, schema names, and tags associated with tables. Here’s a detailed overview of these search capabilities:
#### Table Search
Description: Allows users to search for data by specifying the table name.
Use Case: Ideal for users who know the specific table they need to access or analyze.
Example: A user can quickly locate the "Bank" table to review the data
Benefit: Streamlines the process of finding relevant tables, saving time and effort.
#### Column Search
Description: Enables users to search within tables based on column names.
Use Case: Useful when users are looking for specific data attributes or fields across multiple tables.
Example: A user searching for "card" can find all tables containing this column.
Benefit: Facilitates detailed and targeted data searches, enhancing data discovery.
#### Database Search
Description: Supports searches by database names(Ex. postgres, Oracle etc), helping users locate data within specific databases.
Use Case: Essential for organizations with multiple databases, allowing users to focus their search on a particular database.
Example: A user can search for the "postgres" to find all relevant tables and datasets within this type of database.
Benefit: Simplifies navigation through large, complex data environments by narrowing down search scope.
#### Schema Search
Description: Allows users to search based on schema names within a database.
Use Case: Beneficial for users who need to access data organized under specific schemas.
Example: Searching for the "public" schema will return all tables and objects within that schema.
Benefit: Provides an organized view of data structures, making it easier to locate data assets.
#### Tag-Based Search
Description: Enables searches using tags associated with tables, allowing for thematic or categorical searches.
Use Case: Useful for users who categorize data tables with tags such as "financial," "archived," or "sensitive."
Example: A user searching for the tag "sensitive" will find all tables marked as containing sensitive information.
Benefit: Enhances data organization and discoverability, enabling users to find data based on specific characteristics or purposes.
### Data Exploration Benefits
Efficiency: The ability to search based on table, column, database, schema, and tags significantly reduces the time spent locating specific data.
Comprehensiveness: By supporting multiple search criteria, the VDA tool ensures that users can find exactly what they need, regardless of their starting point or the detail they have.
Usability: A user-friendly search interface allows both technical and non-technical users to perform searches with ease, promoting wider adoption and usage.
Data Discovery: Enhanced search capabilities foster better data discovery, enabling users to uncover hidden insights and relationships within the data.
Organization: Helps maintain a well-organized data environment, where data assets are easily accessible and efficiently categorized.
---
# 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://whiteklay.gitbook.io/virtual-data-assistant/how-to-guides/data-catalog/data-discovery.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.