Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
Medium
-
-
Description
Currently the name of a language resource is not unique.
This can lead to confusion at the side of the user.
The name should be unique within one service type.
The GUI and the API should check on language resource creation, if the name already exists and if not show an error.
Existing naming duplications should be renamed by appending a number.