Queries
Examples
Description
A component that lets users retrieve specific information from the system through defined search criteria. Its purpose is to provide fast, targeted access to existing data, filtering the contents of the repository according to parameters supplied by the user.
Mandatory capabilities
Mandatory capabilities
- Allows the user to specify search criteria through fields, filters, or parameters
- Retrieves the records in the repository that match the criteria, without transforming or aggregating them
- Returns the results in a format the requesting user or system can interpret
Additional capabilities
Additional capabilities
- Advanced search with combinable filters: narrows the search through multiple simultaneous criteria (date range, category, author, etc.) in addition to free text
- Combining data from multiple sources: retrieves information that requires relating data from different entities or repositories of the system
- Result export: lets the user download the records found as a file (CSV, Excel, JSON), keeping the raw data without aggregations
- Pagination: splits the results into pages to handle large volumes without overloading the interface
- Autocomplete and suggestions: proposes terms or records as the user types
- Search history: records the user's previous queries and allows reusing them
Boundaries
What it is not
Information flow
Input
Search parameters (text, filters, selection criteria)
→
Output
Set of records or data that match the specified criteria
Variants
- Interface-based search: the user interacts with graphical fields and filters; typical of searches on websites and end-user applications
- Language-based search: the user writes queries in a formal or natural language (SQL, GraphQL, natural language)
- Predefined search: the system offers preloaded queries that the user only triggers, without composing the criteria
Typical dependencies
- Central repository or Database on which the search is performed
- Authentication and Authorization systems (when the results are restricted by permissions)
Mapping to the Digital Board
Manual UpdateNo
Automatic UpdateNo
Data ConceptsAlways
On-Demand OutputsAlways
Automatic OutputsNo
Autonomous ProcessesNo
| Section | Relationship | Notes |
|---|---|---|
| Manual Update | No | The search criteria (text, filters, parameters) are transient input used to retrieve information; they do not modify persistent data in the system. |
| Automatic Update | No | — |
| Data Concepts | Always | The entities being searched (videos, products, records). |
| On-Demand Outputs | Always | List of results returned to the user. Result export, when that capability is present. |
| Automatic Outputs | No | — |
| Autonomous Processes | No | — |
Digital Board example
Manual Update
—
Data Concepts
Video
On-Demand Outputs
Result List
Smart search suggestions
Automatic Update
—
Autonomous Processes
—
Automatic Outputs
—