search

LSCOIT / LegalNavigator

Phase 3 Access2Justice continued
Creative Commons Attribution 4.0 International
9 stars 3 forks source link

Search API does not return expected results #421

Open aroubin opened 5 years ago

aroubin commented 5 years ago

From @aroubin on October 2, 2018 0:17

Invoking Search API with query "my spouse is beating me up" only returns web links. Providing the same utterance to LUIS returns "domestic violence" topic (0.92).

POST request to the search API: { "sentence": "my spouse is beating me up", "location": {state: "Hawaii", locality: "Hawaii", address: "Hawaii"},

"translateFrom": "", "translateTo": "", "luisTopScoringIntent": "", "isFromCuratedExperience": false }

Copied from original issue: Microsoft/Access2Justice#532

aroubin commented 5 years ago

Issue still occurring. Observations:

  1. FE code passes incorrect parameters to the API. specifically, location and address in addition to state.

expected body of POST request: { "sentence": "how can i get my children to stay with me? my wife took them away after we split.", "location": { "state": "Hawaii" } }

  1. The API returns no intents but some web links, though they are not displayed on the front end. Hit A2J search API with the above contents in the body of the POST to repro.

  2. Hitting LUIS directly with the query definitely produces an intent with 0.90 confidence level (note, API key removed): https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/798c5bc8-c457-430a-958e-ac3fd209e0e0?subscription-key=[removed]&verbose=true&timezoneOffset=0&q=how can i get my children to stay with me? my wife took them away after we split

aroubin commented 5 years ago

From @vennasr on October 31, 2018 15:22

Search returning proper results after the case sensitive issue fixed by Alaa. Other reason to reproduce this issue is the latest develop code was not deployed in the develop site. As discussed, the only change we need to do as part of this bug is to remove additional fields from Location object.