As described in the video below, IC/0291/03  Kruck v. Spain Decision on Jurisdiction and Admissibility - 19 April 2021 HTML and analysis data show up when accessing it through Home - New Dispute Document Analysis on the subscriber site on app.islg. However, when subscribers try to find the same document via Disputes & Dispute Documents library, it is not showing up. The problem seems to be confined to this document only. It was published yesterday (more than 24 hours ago).

This is a high priority item.

Newly published documents not showing up when searching through Disputes Dispute Documents library (8-Jul-21).mp4 7.97 MB • Download

Hi Harsh ,

This was reported by a client, please address as an Unplanned/Critical task.

Thanks,

Morgan

Hi Paul and Morgan ,

The indexes is running every week's Sunday. so last indexes was generated on 4th July.  Hence, This newly published document is not display in Dispute Document Search. Now 11th July the new indexing will be generated again and then above document will be display on search.

If you go directly click on Mathias Cruck and others v. Kingdom of Spain (ICSID Case No. ARB/15/23) dispute on app.islg then the document is displayed.

Hi Harsh ,

Thanks for the explanation.

Martin , I think this raises the issue again on converting to daily indexes for all the dtSearch based searches. When should we start integrating this into the roadmap? Would it be best to do this when we tackle this item: https://dev.azure.com/tologix/ISLGRebuild/_backlogs/backlog/ISLGRebuild%20Team/Backlog%20items/?workitem=699?

Thanks,

Morgan

Hi Morgan ,

I believe we will have more processing power once ISLG Legacy is officially retired, and once we are running on an upgraded server.

It might be best to implement the backlog item you referred above once we are on the new server.

Harsh : do you agree with the above? Do you have further advice on this topic?

Thanks,
--Martin

Hi Martin and Morgan ,

To run daily indexes are not associated with SQL Database Server. Actually, We need to perform task that make daily window schedule command that run Indexes in  one separate folder on we server and once indexes done then will copy to that folder to our main folder. By doing this task only 10 to 15 min window the indexes will not work on server. But, FTS indexes size is so large so we need to first doing this task on staging.islg as a testing purpose and then will implement this task on production indexes.

Will discuss in today's call.

Hi Harsh and Martin ,

Note I've created an item in the backlog linking this to-do: https://dev.azure.com/tologix/ISLGRebuild/_backlogs/backlog/ISLGRebuild%20Team/Backlog%20items/?workitem=818.

My understanding is that our capacity to deal with this issue will increase after we have retired the legacy application, and I have prioritized the item accordingly. Similar to the item dealing with setting up a series of SQL jobs to improve performance of the Citators: https://dev.azure.com/tologix/ISLGRebuild/_backlogs/backlog/ISLGRebuild%20Team/Backlog%20items/?workitem=699.

Thanks,

Morgan