As shown in the video below, a subject navigator search on app.islg subscriber site gives a number of matches that cannot be understood. Legacy admin, subscriber, as well as app.islg admin site all give the correct count of 8 matches, but app.islg subscriber site gives 37 matches that cannot be explained.

This would be a high priority issue, as active subscribers may be confused by the presented number of matches on app.islg which is different from the legacy subscriber site.

Subject Navigator result count (14-Jun-21).mp4 5.95 MB • Download

Hi Harsh and Martin ,

Could you comment on what's happening above, when you perform a search for "injunction" in the subscriber side of the subject navigator: https://app.investorstatelawguide.com/SubjectNavigator/Index?searchType=3&searchRequest=injunction&isStemming=1&isSynonyms=0&isFuzzy=1&fuzzyTypo=1, it indicates that there are 37 matches when there are only 8 instances of "injunction" within the displayed subject navigator branches. What is causing the discrepancy between the number of matches and the number results displayed?

Thanks,

Morgan

This looks like a bug.
Harsh : do you agree?

Hi Harsh ,

Following-up on above, could you comment whether we have a bug here?

Thanks,

Morgan

Hi Radomir ,

Could you please explain the above question ? how will consider match count if we search with any word in Subject Navigator in ISLG application ? 

Hi Harsh ,

I indexed documents on production copied the index locally for testing and I also see 37 documents. When I open the Subject Nav index using dtSearch Desktop and search for "injunction" there, there are 37 results and I see them in the fields.

image.png 138 KB • Download

So, I'm not sure how to help you here. The indexer picks up what's in the database procedure. I suspect the problem is in the DB. In the service response you see all cases where "injunction" was found:

image.png 65.3 KB • Download

I guess you can analyze this output, compare with the expected results, find on which records you're getting unexpected matches and analyze why that data was in the DB row.

Hi Radomir ,

We are displaying total result count 37. Could you please tell us what is the logic behind calculate total result. Which column or what you are considering to calculate totalresult ?

Hi Harsh , all columns containing text are considered. As you can see in the screenshot from my previous message, dtSearch says there are 127 hit counts and text search in the result payload also shows 127. That means all hits are there in the payload. Just check the payload and see in which fields "injunction" appears. That should be it.

Hi Morgan and Paul ,

We have resolved the Subject Navigator subscriber side result count on staging.islg. Please check and confirm.

Ok. Thanks Harsh .

Paul , can you confirm whether the issue is resolved?

Thanks,

Morgan 

Hi Harsh :

As you can see in the video below, there is a discrepancy between staging admin and staging subscriber re: result count (8 on admin which is wrong v. 6 on subscriber which is correct). It needs to be addressed before we could mark this item complete.

Subject Navigator result count 2 (27-Jul-21).mp4 6.38 MB • Download

Thanks,

Paul

Hi Paul ,

The above issue is resolved on staging.islg. Please check and confirm.

Hi Piyush :

This issue isn't fully resolved. As I described in the video below, the match  count for both admin and subscriber sites should always be the same no matter what the search term/phrase is. 

Subject Navigator result count 3 (28-Jul-21).mp4 6.84 MB • Download

Hi Paul ,

There was some issue in admin side which we resolved now you can see 147 count in admin side and 144 on subscriber side.

The minor difference will be there because of following reasons.

1) In admin side we also find the word for unpublished branch but on subscriber side we display only published branch.

2) Also SN search result in admin side populated by DTSearch Indexing which is currently running on every Sunday. so might be there will be a minor difference in count for admin and subscriber side.

3) The third point is like Dispute Document branch you tagged but that Dispute Document is not published but admin side it is considering in search count.

Hope this is fine.

Hi Harsh :

Ok, I understand. However, there is still a question outstanding.

Re: 1) When I search for how many entries (not branches) are still unpublished on staging.islg admin site for "res judicata," there are 4 Pey Casado v. Chile II Award unpublished entries as shown below, while the difference you indicated is 3 (147 staging admin v. 144 staging live). Why is there a discrepancy of 1 still?

image.png 68.1 KB • Download

Re: 2) I'll let Martin comment.

Re: 3) This is fine, but the four entries I pointed out above are entered under an active branch ( Treatment of res judicata by other investment tribunals).

Re: #2, we currently can only run once weekly due to performance considerations. But this will be improved once we no longer have ISLG Legacy and are migrated to a new server.

Hi Martin :

Can you create a DevOps item if there isn't one already and add it to the sprint after we upgrade the server?

Thanks,

Paul

Hi Paul ,

We are now running indexing daily against app.islg since we have disabled Legacy. 

If the only remaining item in this thread was related to run the indexing daily on app.islg, then it is done and we can mark it as closed.

Thanks,
-Martin