AI search complements structured search — it does not replace it. Behind the scenes your question becomes the same clause-and-operator query, so results are exact and explainable, not a black box.
How it works
- You enter a natural-language request, e.g. “recent SEM or TEM studies”.
- Dataerai reads the statistics of the data you can see — which fields exist, their common values, their ranges — and a language model designs a structured query that captures each facet of your request.
- It enumerates real alternatives as OR branches (
SEMorTEM), combines facets withand, and excludes withnot— every value drawn from your actual data, not invented. - Each branch is probed for a match count, and you see the designed query — editable chips, or a read-only OR-tree when it nests — with counts, before it runs against the assets you can already access. AI search never widens your permissions.
Reading the results
When a translation is worth explaining, an insights panel appears beneath the search box before you go to the results, so you see the query that was designed and how it landed:- Per-condition matches — a count next to each branch of the query. An amber “no matches” tells you a value you expected isn’t in your data before you commit.
- Grounding misses — if a “like this” phrase resolves to no value you can see, you get a badge saying the search was widened to a text search, instead of a silently empty page.
- No exact matches — if a precise query matches nothing, Dataerai widens to the closest results by meaning and shows a “No exact matches — showing the closest results by meaning” banner.
Summarize selected assets
When AI search is enabled, you can also ask Dataerai to summarize a set of assets in plain language. Select up to 50 assets in the results, then click Summarize in the summary panel. The summary streams in as it’s generated — click Stop at any time to keep what’s arrived so far. The panel notes how many assets were included and flags any that were skipped because you don’t have access or were too large to read in full.What makes a good query
Concrete attributes
“files of type pdf”, “assets created after 2024-01-01”, “records with a DOI” — these map cleanly onto metadata fields.
Topical phrases
“microscopy images of biological samples” — handled by the semantic image lane, when your administrator has enabled it (see below).
Topical & visual matching
For “find me things about X” questions, AI search can rank figures by visual similarity rather than keyword overlap — so “biological samples” returns images that look biological, not just ones whose caption happens to share the words. This lane is off by default and is enabled by your administrator. It also requires that your images have been processed for similarity search. Until then, topical queries fall back to the structured translation. A related value-similarity lane lets you describe a metadata value you can’t name precisely (“scanning-electron-type techniques”) and have Dataerai match it to the real values that exist in your data. It is enabled separately by your administrator; see the “like this” examples in Grounded OR-tree search.Availability
AI search appears only when your organization has opted in to AI features. If you don’t see the AI search input, ask an organization admin to enable it — see AI policy & access.Next steps
Grounded OR-tree search
The deep dive — how queries are designed, with a gallery of examples.
Structured search
The clause-and-operator query AI search compiles to.
AI policy & access
How admins turn AI search on for an organization.
Agent configuration
Point AI search at your own models.