Info

This is a pre-requesite to develop TRANSLATE-3034 Manage custom attributes in TermPortal GUI

Problem

Proprietary attributes of a tbx will be available for the whole translate5 instance. TermPMs can see them even when they are not allowed to see the termcollection the attributes are used in. This should not be the case as the attributes could contain information not intended for others.

Solution

• change proprietary attributes to be linked to the TermCollection, where they are available.  Therefore if there the same attribute needs to exist in 2 TermCollections, it needs to exist now twice in the DB. With that change all currently existing proprietary attributes would still be available in all currently existing TermCollections, but not in new ones anymore
• from then on we would make proprietary attributes from new imports only exist in the TermCollections, where they are imported into
• those proprietary attributes should still be possible to be disabled as they are currently
• There should be a new switch in the TermPortal, usable for TermPMs (all clients) only, that
  • on click removes the deactivated proprietary attributes from being  present in a termCollection
  • removes them completely from the TermPortal, if they are not linked to any TermCollection anymore