Ambiguity in the search Asset result in RAM.
![]() We are using REST API’s in our application in order to get the desired result from RAM. In order to search for an asset in RAM, the result it is giving is ambiguous, here are some scenarios:
There is an Asset with Asset name “vvvvvvvvvvvvvvvvvvvvv1” in
After applying all these three filters (Community as “Test_Community”, Asset type as “Test_AssetType” & State as “Submitted”)for the search, in the result list this Asset (vvvvvvvvvvvvvvvvvvvvv1) is displayed among all other Assets fulfilling same filter criteria. But now when I search with giving the search string as: · Case 1
1. Search String: “v”
2. Search String: “vvv”
3. Search String: “vvvvvvvv”
4. Search String: “vvvvvvvvv”
5. Search String: “vvvvvvvvvvvvvvv”
6. Search String: “vvvvvvvvvvvvvvvvvvvvv”
7. Search String: “vvvvvvvvvvvvvvvvvvvvv1”
· Case 2 : Under same community, Asset type & State, there are some other Assets (VAV1, vav4 & vav6). So after applying all the above filters and again trying to search for the asset via search string, giving search result like this:
1. Search String: “v”
2. Search String: “vav”
3. Search String: “vav4”
4. Search String: “vav6”
5. Search String: “VAV1”
And so on… I am not able to understand the different result for different scenarios, they all are quite confusing. Can anyone provide any help as why all these results are like this?And is there any other Search Query String which can be used to fetch the search result from RAM?
|
One answer
![]()
Note that the free form text search looks at various aspects of the asset. Name/Description is part of it, but it also includes related asset (their name/version), tags, attributes etc.
for the “vvvvvvvvv”which results in something, ... it seems like it found it in the meta for that asset. Note also, that the search is working by first tokenizing the text, and then indexing the tokens. So “vvvvvvvvv,foo” will be tokenized as “vvvvvvvvv” and "foo" since a comma is considered as a "special character" that separates them.. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.