Set up company web search
DataMind Oda can search the web and read pages through your company's own web access, the company path (datamind). Its address, and any key it needs, are set for your deployment, and once you are signed in to your company's DataMind server the session itself authorises the calls. This page covers that path's setup and its messages; the calls and their results are on Searching and reading the web, and how Oda chooses a service is on Web search providers.
What the company path does
- Searches and page reads run on your company's side. Your company's DataMind server performs the search and retrieves the page, and Oda receives what came back; on this path nothing is fetched from your computer.
- A search returns its sources. Each source carries a title and an address, with a snippet and a date when the service supplies them. An entry without an address is skipped, and a duplicate address is kept once, first one wins.
- A search never returns page text. Reading a page is a separate step, and Oda reads pages on its own when a task needs their words.
- A page read reports the page's status. A page that answered 404 was still read, and its status is the result, not a failure.
- A second path exists. Public pages can also be read from your computer, without credentials, through the anonymous reader; Anonymous web fetch safety covers its rules.
See or change the endpoint
- Open Settings > Plugins > Plugin configuration > Web search.
- The Endpoint field holds the address the company path uses. View or change it there; only you should choose or change the endpoint.
- Save. The next search uses the new address, with no restart and no re-registering.
- Kept separate from chat. The search endpoint is deliberately independent of the endpoint your chat models use: changing your chat model does not move the search, and changing the search does not touch your chats.
- A failed call points back here. The message on a failed call names this settings section, so a search problem starts with the Endpoint field.
- What your company controls. Which services your installation offers, and which one is chosen, belongs to your company's deployment; Web search providers covers the choice. A service counts as usable only when its setup is complete: a key where one is needed, an address that parses, and positive limits.
The key and your session
- A signed-in session stands in for a key. With a signed-in DataMind session, the endpoints follow the session and the session authorises the calls; no separate key of yours is involved.
- Where a key is used, one order decides. A key set directly for the service wins; otherwise Oda looks in its stored credentials, where a key saved on Settings > Models lives (Set up models and providers, Stored credentials); last, a key from the environment Oda starts in.
- A change applies from the next search. The endpoint and any key are read afresh for each search, so a change you save is used without a restart; only a value from the environment is read when Oda starts.
- Signed out, nothing is sent. While you are signed out, these calls stop before any network request is made, and Oda reports that web search needs a sign-in or a key; sign in and try again (Install and sign in).
- A stale session is refreshed once. When a call is rejected because your sign-in has gone stale, Oda refreshes it once and repeats the call, so a sign-in that lapses mid-task usually passes unnoticed.
- A newer Oda may be needed. When your server needs a newer version of Oda for these calls, the call stops and Oda raises the Update DataMind Oda notice; Update DataMind Oda walks through updating.
- Redirects are refused, not followed. A request that carries your credentials stops at a redirect response: the address it points to is never contacted, so your credentials are never sent on to it.
- Proxies are honoured. When a proxy is set in the environment Oda starts in, web search and page reads use it (Network proxies in Oda).
When something fails
A failed call leaves its message with the step in the chat. These are the company path's messages:
| Message | What it means |
|---|
Platform web search error (HTTP <status>) | The search reached your company's service and came back with an error status. |
Platform web read error (HTTP <status>) | The page read came back with an error status. |
Platform page read failed: <detail> | The service reported the read itself as failed; the detail, when present, says why. |
Platform web request aborted | The call was stopped before it finished. |
Platform web search returned an unprocessable response body | The answer was not in a shape Oda could read. |
Platform web read returned an unprocessable response body | The same, for a page read. |
- Failures about the key. When no usable key reached the service, the failure says so; store a key or set one as above, and the next search can use it.
- When a message repeats. Keep it as it is and contact your DataMind OS administrator; Troubleshooting collects the messages you may see.
Questions, answered
Where do I view or change the search endpoint?
Open Settings > Plugins > Plugin configuration > Web search and edit the Endpoint field. Only you should choose or change it. Saving serves the next search, and a failed call points you to the same place.
Do I need a key for company web search?
No, not while you are signed in: the endpoints follow your DataMind session, and the session authorises the calls. Where a key is used, a key set directly for the service wins, then a stored credential (a key saved on Settings > Models), and last a key from the environment Oda starts in.
When does an endpoint change take effect?
On the next search. The endpoint and any key are read afresh for each search, so nothing restarts and nothing re-registers. A value from the environment Oda starts in is the one exception: it is read when Oda starts.
Does the search endpoint follow my chat model?
No. The search endpoint is deliberately independent of the endpoint your chat models use, so an error about web search points at its own settings path, not at your model setup.
Why does Oda say web search needs a sign-in?
Because you are signed out. While you are signed out, these calls stop before any network request is made, and Oda reports that web search needs a sign-in or a key. Sign in, then try the search again.
What does Platform web search error (HTTP <status>) mean?
The search reached your company's service and came back with an error status. Try once more; if it keeps failing, keep the message and the status for your DataMind OS administrator.
What does Platform page read failed: <detail> mean?
Your company's service could not read the page and reported why; the detail, when present, names the reason. Check the address, or ask Oda to read a different page.
What does Platform web request aborted mean?
The call was stopped before it finished, for example because the work was cancelled. Nothing was left half-done on your side; send the search again when you want it to run.
Does a company search return page text?
No. A search returns its sources only: a title and an address for each, with a snippet and a date when the service supplies them. When Oda needs the page's words, it reads the page in its own step.
Why does a redirect stop the call?
Redirects are refused rather than followed on this path: the address a redirect points to is never contacted, so your credentials are never sent on to it. Ask Oda to read or search the final address directly.
What happens when the server needs a newer Oda?
The call stops and Oda raises the Update DataMind Oda notice. Update Oda, then try the search again; Update DataMind Oda walks through the update.