Actions
Bug #18192
closed
Advanced search is showing ROX IDs in the search field syntax instead of clear values
Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Workbench2
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Description
We have switched Arvados to use ROX IDs in the vocabulary.json. Setting properties is working fine and it's resolving ROX IDs in most UI components to the clear text values. However it seems that the Search field is not able to do so.
To reproduce this open the advanced search and add a property. It will show correctly as clear text in the dialog but as ROX:ROX in the search field.
Expected behaviour is to show resolve ROX IDs in the search field to human readable text and to use ROX IDs in the background for the API call.
Updated by
Actions