Hi Harsh :

As the video shows below, "Document Reference (Quick Links)" is not showing any Non-Investment Dispute Documents (anything with "NU/#####" UINs). We are able to make and save references using "Cited Document UIN" below, but admin users who would be tagging the HTML will not know the UIN, and they need to be able to use Quick Links to find relevant Non-Investment Dispute Documents.

NU documents not appearing under Quick Links (19-Mar-21).mp4 4.63 MB • Download

Thanks,

Paul

Hi Paul ,

As per requirement, We haven't pulled Non-Investment Document in Quick link. We only pulled Dispute Document UIN in quick link.

Following is the User Story for Quick link.

https://industrialagency.tpondemand.com/RestUI/Board.aspx#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiIn0=&boardPopup=userstory/8498

Hi Morgan :

This requirement needs to be changed before I can have analysts drafting DCDs directly on HTML. 

Thanks,

Paul

OK. Thanks Harsh and Paul .

Ketan , we can push this to-do to post launch, but this is a high priority item, because it will prevent us from allowing legal analysts from adding data directly into the new application.

Harsh , will it be substantial amount of work to expand the Quicklist to include Non-Investment Treaty Dispute Documents?

Thanks,

Morgan

Hi Paul ,

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

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/251

Hello Paul ,

I tested this on staging.islg. I am still not able to select NU UINs under Quick Links on staging.islg. 

Thanks,

Nafiseh

Nafiseh , could you provide a video showing the issue.

Thanks,

Morgan

Hello Morgan and Paul ,

Here is the video that shows NU UINs cannot be found under Quick Links on staging.islg:

6-16-2021 9-56-49 AM.mp4 1.44 MB • Download

Thanks,

Nafiseh

Thanks Nafiseh . Harsh , could you please resolve.

Thanks,

Morgan

Hi Nafiseh ,

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

Hello Piyush ,

I ran a test on staging.islg., and I can confirm that the issue is resolved. However, I noticed that the field (Document Reference (Quick Links)) is upper/lower case letters sensitive, and the results are only found when they are entered exactly the same as what appears under Non-investment Treaty Dispute Documents. As you can find in the video below, in the example of "Salem Case", if I enter it as "salem case", no results are found.

Is it possible to resolve this issue, so that no matter how the reference is entered (in terms of upper/lower case letters), the results show up?

6-17-2021 9-10-45 AM.mp4 3.61 MB • Download

Thanks,

Nafiseh

Hi Harsh and Piyush ,

Let us know if we can get the change Nafiseh has requested done this sprint or if we need to create a new item in the backlog to deal with this in the following sprint.

Also, my expectation is that the Quicklinks search would be case neutral and also have to ability to include results when there are diacritical marks. For example, if I enter "chorzow" into the Quicklinks search field, I would expect "Case Concerning the Factory at Chorzów (Claim for Indemnity) (Merits) (Germany/Poland), Judgment" to appear as a result I can select.

Note the same should apply to the Quicklinks functions for the other research tools (Article Citator, Publication Citator, etc.).

Thanks,

Morgan

Hi Morgan and Nafiseh ,

As per you suggestion, we have develop and upload on staging.islg. Please check again and confirm.

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/251

Great. Thanks Piyush ​.

Nafiseh ​, could you test and confirm.

Thanks,

Morgan

Hello Morgan and Piyush ,

I tested Quicklinks functions in terms of case neutrality as well as the ability to include results when there are diacritical marks. I ensured to include Quicklinks functions for the other research tools (Article Citator, Publication Citator, etc.) in my test.

The only issue that I need to report is that compared to before, it takes more time for the results to show up.

6-18-2021 9-17-01 AM.mp4 1.92 MB • Download

Thanks,

Nafiseh

Ok. Thanks Nafiseh ​.

Piyush ​, could we resolve the speed issue. I don't want to deploy this if it's going to affect the speed of the search, because it affect the productivity of the content team.

Thanks,

Morgan

Hi Morgan and Nafiseh ,

We have resolved speed issue on staging.islg. Please check again and confirm.

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/251

Hello Piyush ,

I checked the speed issue on staging.islg. The issue is now resolved. 

Now that all the outstanding issues are resolved, I'll mark this to-do as complete.

Thanks,

Nafiseh