Term collections
Collections and terms
How to build and maintain a collection: concepts, terms, statuses, sources and history.
Creating a collection
Create a collection in your personal workspace, or in an organization where you are an owner or editor. Set a default license for new terms; terms without their own source take it. Archiving a collection hides it but never deletes it.
Concepts and terms
- Add a concept with one or more terms, then add terms in other languages to it.
- Each term has a status (preferred, admitted, deprecated and others), a type, a usage note, definitions and a source with a license.
- Editing a term's spelling, status, type or usage note creates a new version. Its source, provenance and definitions are kept.
- Withdrawing a term or removing a concept keeps it in history, and both can be restored.
- Concept history shows every version of every term, including withdrawn ones.
Working with the public bank
- Add a public concept to your collection by reference. Its terms stay read-only, but you can prefer, admit, deprecate or hide a term in your collection only.
- When a private concept shares a term with a public one, Termbanks suggests linking them. A linked concept's next reviewed release adds its terms to the public concept instead of creating a duplicate.
- Similar concepts, by meaning in any language, are suggested next to each concept. You can copy selected terms (with their sources and licenses) or mark a suggestion as not related. Nothing is ever merged automatically.
- You can suggest terms for a public concept through one of your collections; they go public through that collection's reviewed release.
Organizing the table
- Choose and order the language columns. Hiding a language keeps its terms.
- Add a collection note and subject domains to a concept.
- Write style guidelines for the collection. Agents receive them with translation context.
- Follow one published release of an upstream collection exactly, or follow it live.
Editing safely
Every edit carries the collection's revision. If someone else changed the collection first, the edit is refused with a conflict instead of overwriting their work; refresh and try again.