For simplicity of usability and development the proposing of terms is done in the same terminology portal, that already exists for viewing the terminology.

The communication with the server will be done via REST as it is standard in translate5. Since we are using jquery in the termPortal instead of ExtJs, a jquery rest-client class may be used like https://plugins.jquery.com/rest/ (research more in depth on development).

Existing REST-calls are documented in the API

Every PM and Admin and API user has the possibility to search the terminology of all customers.

Envisioned further development (not part of the current concept)

It is envisioned, that every PM and Admin and API user will be able to edit terminology and access the termPortal of all termCollections of all customers by default and that proposed terms these users are able to accept or reject the proposals.  In addition these users can directly edit and add terms.

All other users don't by default. For other users an additional role terminologyEditor will be available and can be assigned for the same purpsoe. Users with this role will be able to edit the terminology of all customers, that are assigned to them.