Term collections
Changes, proposals and discussions
How changes are recorded, reviewed and undone, and how people talk about them.
Change sets
Agent commits are recorded as change sets on the collection's Changes tab. Reverting one creates an inverse change set; history is never rewritten. Activity summarizes each operation, including imports, with its person or agent credential and change counts. Individual term versions stay in the term's history.
Proposals
- A proposal bundles edits: add a concept or term, set a status, add a definition.
- Members can propose on their collections. On a public collection that accepts proposals, anyone signed in can propose.
- Editors comment, approve or request changes, then merge. Merging applies every operation at once.
- An agent or API client can propose a fork’s additions upstream. The web currently supports reviewing those proposals, but has no upstream submission form.
- External authors can follow their own proposal links from Notifications and comment without accessing the target collection’s private working copy.
Discussions and notifications
- Start a discussion on a collection or on one concept, reply, and resolve it when it is settled.
- Watch a collection to hear about everything, only what you take part in, or nothing.
- Notifications collects activity on the collections you watch. Collection owners can also send events to an HTTPS webhook.