-
Type:
New Feature
-
Resolution: Unresolved
-
None
-
Affects Version/s: None
-
Component/s: LanguageResources
-
High
-
Emptyshow more show less
- For each languageResource of type TM and TermCollection an option is given: Search languageResource
- A click on the option opens a window with the current functionality of the concordance search in the editor
- In the drop-down to select the searched languageResource the current languageResource is pre-selected
- In addition 3 more drop-downs allow to filter, which languageResources are selectable in the drop-down, where the languageResource to be searched is pre-selected:
- Client
- Source language
- Target language
- if in the languageResources drop-down "all resources" is selected, all languageResources that match the filter by the other 3 drop-downs are searched. Yet to avoid DOS-attacks on languageResource providers (for example querying of 100 Groupshare-TMs at the same time would not be good for GroupShare), only a few languageResources are queried at the same time. More are queried if
- The user scrolls down
- or there are less than 10 matches from the already queried languageResources
- The user must see, that and if there is the possibility to search for more matches by scrolling down
- Above the languageResources grid next to "Add language resource" a new button "Concordance Search" / "Konkordanzsuche" is added. If it is clicked, the same window opens, but with "All resources" pre-selected in the languageResources drop-down. If in the general client switch a client is pre-selected, this client is pre-set in the clients drop-down.
- causes
-
TRANSLATE-1921 Enable languageResource management features based on user rights
- Backlog
- mentioned in
-
Page Loading...