When DataMind Oda reports a technical problem, the message you see is already written in Oda's own wording: internal names and locations are put into product wording before the text reaches you. This page is a short guide to reading that text, with the shapes you can meet in it and where the original wording stays; the full account of the rewrites is in What Oda shows and what its logs keep.
The short forms below are normal in shown text. Read them as names and places inside Oda's own software, not as files you should find on this computer.
| What you see | What it stands for |
|---|---|
oda/, as in Cannot find package 'oda/ | A part of Oda's installed software, written in Oda's wording. |
oda-<name> | A single word that carried the software's internal name. |
oda, Oda or ODA as a word of its own | The software's own name, keeping the capitalisation of the word it replaced. |
A shortened path, written with / separators | A place inside the installed software; the folders that exist only on this computer are dropped. |
at resolveBareSpecifier (sea-main. | A frame from the place Oda was built: only the file name and the position stay. |
oda/ | A line from Oda's own output naming the part that reported it. A leading label that only repeated the command's name is removed. |
The rules run in a fixed order, so one line can pass through several of them. The result is stable: text that is already in Oda's wording is not changed again. Everything else in a message, such as an error code or a number, stays as it is.
Failure output when Oda starts reads the same way; Startup and diagnostics covers how to read a failed start.
Keep a message exactly as it appears when you pass it on for support: it is already in product wording, so it needs no cleaning up.
oda/ in one message and oda-<name> in another?The two shapes come from different kinds of name. A name that pointed inside the installed software is written with the oda/ prefix, as in Cannot find package 'oda/; a single word that carried the software's internal name is written with a hyphen, as oda-<name>. Both are Oda's own names in product wording, and both are normal in shown text.
A word that used the software's internal name keeps the shape of the word it replaced: an all-capitals word reads ODA, a word with a first capital reads Oda, and a lowercase word reads oda. The rest of the word is unchanged.
The shortened form always uses / separators, whatever separator the computer itself uses. It points to a place inside the installed software, so you will not find it as written among your own folders.
Yes. The rewording is applied before Oda shows text to a person or puts it on the clipboard, so copied text matches the screen. It is a display change only.
An address keeps its form; only a name that stands for Oda is rewritten inside it. The addresses that identify model services keep their spelling as well.
Yes. The rewrite covers only the software's own names, its paths and its build locations; everything else in a message, including error codes such as ENOENT and position numbers such as :3001:14, stays as it is.
No. It is a display change only: the rewrite runs on text on its way to a person, and it never changes how Oda works.