Thot Thesauri

• Get a conceptRead everything Thot publishes about one concept: its name in English, French and German, the other names it goes by, where it sits among the broader and narrower terms, the XML value attached to it, and (for a concept in the date thesaurus) the range it covers, both as Thot writes it and as numbers you can sort on. This is the one step behind a catalogue record that stores nothing but 'thot-374' and has to show a king's name and his dates.
• Get several conceptsRead the same full record for a list of concepts at once. A catalogue record names its script, its language, its genre and its date as four Thot identifiers; this turns all of them into readable terms in one step rather than four that each do the same thing. Comes back with a name-by-identifier map beside the records, so a workflow can read one straight off.
• Get a thesaurusRead a whole Thot thesaurus: every term in it, in the language you choose. The API serves a thesaurus as the nested source of a tree widget; this brings it back as rows, each carrying its identifier, the term above it, how deep it sits and the whole path down to it, so a workflow can filter and join it without walking a tree.
• Search a thesaurusFind the concepts in a thesaurus whose term matches some text, closest match first. Every other step here needs a 'thot-' identifier and nothing in Thot turns a word into one, so this is where a workflow starts from a term someone typed. Case and accents are ignored, and each match comes back with the whole path down to it so a term that appears twice can be told apart.
• Get a concept as RDFGet a concept's SKOS record as RDF/XML, exactly as Thot serves it, for loading into a triple store or handing to something that reads linked data. Get a concept reads the same document and reports what it says instead, so use this one when the document itself is what you need.

No actions match that.