As shown in the video below, certain documents that I expect to see under the search field of Disputes & Dispute Documents do not appear as suggested options.

Indexing search field (29-Oct-21).mp4 11.6 MB • Download

Hi Harsh and Martin ,

Now that the daily indexing on dtSearch has been implemented, shouldn't we be seeing the documents Paul describes above in the search results?

Thanks,

Morgan

 

Hi Morgan and Paul ,

This issue is resolved on app.islg. Please check and confirm.

Hi Harsh ,

Can you describe what the issue was? Do we risk encountering it again?

Thanks,
--Martin

Hi Harsh :

The issue is resolved, but I won't mark this item complete until you provide an answer to Martin 's question above.

Thanks,

Paul

Hi Martin ,

The issue is regarding foreign characters text. In auto suggest, we fetch the data from database and for foreign characters we have updated the query so foreign characters data match with text. 

Hi Harsh ,

Is there a reason why we do not use the COLLATE keyword in our query? This would prevent us from having to modify the query everytime we encounter a new accent.

Example below would return any records with "cafe" or "café":

SELECT * 
FROM MyTable
WHERE MyField COLLATE Latin1_General_CI_AI Like '%cafe%' COLLATE Latin1_General_CI_AI

Hi Harsh ,

Let's discuss on Tuesday.

--Martin

Hi Martin ,

I looked into this and found that when any Accents characters saved in database that time it is stored in table as html code. so when we search those words we need to convert those html codes as normal string.

We will look into this how will convert while we fetch data using search query.

Hi Martin ,

We did one solution for replace html code through query on app.islg. so please check with Paul for Dispute Document and let me know if you still have any issue.

Hi Paul , can you take a look and let us know if this particular issue has been addressed?

Hi Harsh , is the new solution designed to take care of any accent we encounter moving forward?

Hi Martin :

I tried to test it, but suggested documents do not appear as shown in the video below. I'll take a look again once the suggestion functionality (1:13 video above shows what I expect) is restored.

Disputes Dispute Documents no suggested results (24-Nov-21).mp4 2.2 MB • Download

Thanks,

Paul

Hi Harsh ,

Can you let us know once the suggested matches function is restored?
I would also like to understand why this is not working. Have we changed code on app.islg? Or is the issue related to indexing?

I believe this was working correctly on Monday.

Thanks,
--Martin

Hi Martin and Paul ,

The issue is solved on app.islg for search result in app.islg. actually I tried one thing in my local SQL Server and it seems fine for me.

When I executed same query on server then it was throwing error because our carbon 60 server is SQL 2014 version and in our local SQL is 2019 version.


so I restored old query again.

Hi Martin :

Suggested matches are working again on app.islg.

If there are two different SQL versions, is the Carbon 60 server 2014 version older than the local SQL 2019 version? If Harsh restored the old query again, would it be an issue as we revert to an older version?

Please let me know before I can mark it complete.

Thanks,

Paul

Hi Harsh ,

Since you had to revert back to the prior query, does this mean we are still vulnerable to incomplete searches when dealing with accents?

If that is the case, I will create a new backlog item to address this specific issue.

Thanks,
--Martin

Hi Martin ,

I did some changes in query which dealt with accents characters. Paul , could you please check on app.islg with 3 to 4 different examples.

Let us know if you still have an issue for accents characters.

Hi Harsh :

Foreign character issue is resolved.

However, the suggested match is still not producing IC/0310/12 Union Fenosa Gas v. Egypt, Decision on the Request for a Continued Stay of Enforcement of the Award, 18 October 2019 as an option. Compared to the very first video,  IC/0310/13 Union Fenosa Gas v. Egypt, Procedural Order No. 1 (Annulment Proceeding) now shows up as a suggested match, but IC/0310/12 still doesn't. 

Martin : are we ok reverting to the 2014 version of SQL or do we still need a new backlog item?

Thanks,

Paul

Hi Paul ,

Our app.islg SQL Server runs on version 2014. We are stuck with this version until we upgrade our servers (planned for Q1 2022).

In the meantime, Harsh took another approach and the latest SQL query he worked on is compatible with SQL 2014.

Thanks,
--Martin

Hi Paul ,

Can you please send the video to elaborate issue because I check app.islg database and I didn't found  following full citation for UIN IC/0310/12.

Union Fenosa Gas v. Egypt, Decision on the Request for a Continued Stay of Enforcement of the Award, 18 October 2019.


Cc : Martin  

Hi Harsh :

The video describes the indexing issue that still persists.

Indexing search field (30-Nov-21)-2.mp4 4.82 MB • Download

Thanks,

Paul

Hi Martin ,

We did some R&D and fond the solution that we need to replace html code while data will be add/update in database and by using function we convert html code to string for those data which already added in table.

Could you please add this item in next sprint with 12 hours effort time.

I have created DevOps item https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1262 and ranked it near the top of the backlog.

Thanks, Martin . 

Hi Paul ,

This task is done on staging.islg.  Please check and confirm.

You can check by add foreign characters in Dispute Document Full Citation field and Publish it. Then, try to search that full citation in Dispute document' s auto suggest search on subscriber side.

Please provide your feedback.

Cc : Sharmila Martin  

Hi Harsh :

When the content team tests this item, do we need to wait 24 hours for indexing to take place on staging.islg before testing?

Irit : could you test this on staging.islg after Harsh answers my question please?

Thanks,

Paul

Will do, Paul .

Irit

Hi Paul and Irit ,

You can add the data through admin side on staging.islg and publish it. Once you completed that process then let me know so I will run the indexing job on staging.islg.

Once the job will run you can find the search data on staging.islg.

Hi Harsh and Paul ,

I uploaded and published a new PDF and HTML to staging.islg admin site.  Please let me know when indexing is complete and I will check staging.islg live site.

Thank you,
Irit

Hi Harsh and Paul ,

I checked staging.islg live site but the newly uploaded Dispute Document from yesterday does not appear. 

I'm following up to see if indexing is complete? Please let me know when it is complete and I will check staging.islg live site again.

Thank you,
Irit

Hi Irit ,

Today, We run the indexing on staging.islg. Please check and confirm.

Hi Harsh and Paul ,

This is to confirm that the document appears on staging.islg live site.

I checked staging.islg live site and the newly uploaded Dispute Document that I uploaded on December 16th now appears. 

Thank you,
Irit

Thanks, Irit .

Harsh : could you let us know when this is deployed to app.islg, so we can test again and mark it complete?

Paul

Hi Paul ,

This task is done on app.islg. Please check and confirm.

It looks good now. Thanks, Harsh .