Subject Navigator entries are not appearing correctly on app.islg admin and subscriber sites. The two dispute documents (IC/0256/02 and UN/0092/69) below show incorrect Subject Navigator entries under Analysis List.

UN/0092/69: every single Subject Navigator entry should start with South American Silver v, Bolivia Award. However, there are a few entries starting with MetLife and Mobil Exploration v. Argentina.

image.png 74.3 KB • Download

The first example from above (MetLife) on the subscriber site of app.islg shows the correct link to MetLife pa24, as well as the incorrect South American Silver pa648 link.

image.png 75.6 KB • Download

Another example of IC/0256/02: RREEF v. Spain Subject Navigator entries showing Bau v. Thailand, CEF Energia v. Italy, Churchill and Planet v. Indonesia, etc.

image.png 83.8 KB • Download

Please see the video.

Subject Navigator entries incorrectly appearing (14-Apr-21).mp4 21.6 MB • Download

Hi Paul ​,

Is this a problem with migrated Subject Navigator data from the legacy app?

Morgan

Hi Morgan :

Yes, this is a problem with migrated Subject Navigator data from the legacy app. Was there a deployment to app.islg on Monday? I have noticed a few things that are different on app.islg since Monday (including what I've posted and you triaged today), and I don't recall migrated Subject Navigator data having this issue when I looked at a few other examples in the past few weeks.

Paul

OK. Thanks Paul ​

Harsh ​​, I'll add this to the agenda for our meeting today. As Paul ​ mentioned he's noticed a few regression issues with the Subject Navigator since the latest deployment to app.islg. Would it be possible to run some tests to confirm whether these have impacted the Subject Navigator or other aspects of the application?

Morgan  

Hi Morgan and Paul ,

We have updated the query for SN Analysis List on admin side on app.islg. Please check and confirm.

Great. Thank you, Harsh ​ .

Paul ​, could you confirm whether this is resolved as well as the other issues you reported in the other to-do's. Note these have all been move to the Post-launch Issues list.

Thanks,

Morgan

Hi Harsh and Morgan :

The issue is not resolved yet as you can see in the video.

Subject Navigator entries incorrectly appearing 2 (15-Apr-21).mp4 11.5 MB • Download

Thanks,

Paul

Hi Paul ,

Could you please provide whole path of SN tree to reach out that level on app.islg.

For Example,

A > ABC > ABC1>  ABC2 

so we can check and find what is the issue because currently we are not getting that under which path you are going to show that document is missing.

Hi Harsh :

The issue is found in D > Discrimination > Under other investment treaties.

The red circled entries from the legacy admin site are missing on app.islg Subject Navigator Master Tree.
https://www.investorstatelawguide.com/MasterTree/index?rootNodeID=&expandList=1,26562,26786,59302#59302

image.png 50.9 KB • Download

image.png 50.4 KB • Download

Thanks,

Paul

Hi Paul ,

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

Hi Harsh :

The issue is still not fully resolved. I do see the three SN entries  (two South American Silver and one RREEF) under  D > Discrimination > Under other investment treaties that were initially missing are there now, but when I look at the analysis lists of IC/0256/02 and UN/0092/69 as I mentioned at the beginning of this post, the issues identified are still there. 

Subject Navigator entries incorrectly appearing 3 (20-Apr-21).mp4 14.5 MB • Download

Hi Paul ,

We have resolved this issue on app.islg. Please check and confirm.

It is resolved, thank you.

Hi Harsh :

There is a regression issue.

Under F > Fair and equitable treatment > Tribunals (and dissenting arbitrators) finding a breach of the fair and equitable treatment provision (https://app.investorstatelawguide.com/SubjectNavigator/Index?branchid=v0ru1h-ahh0%3D), users see SolEs Badajoz v. Spain Award entry twice: once with correct citation and once with incorrect IC/0181/01 citation.

Deutsch Bank v. Sri Lanka Award IC/0181/01's Subject Navigator Analysis list incorrectly shows duplicate texts of SolEs Badajoz v. Spain Award IC/0418/01 SN entries but cite IC/0181/01 as shown in the video.

Subject Navigator entries incorrectly appearing 4 (24-Jun-21).mp4 11.6 MB • Download

Could you check all UINs again to ensure no other dispute documents are affected? I suspect this issue is related to Ghost entry without any document citation under Subject Navigator - TOLOGIX - ISLG App Rebuild. 

This is a medium to high priority item, as it affects the users. 

Thanks,

Paul

Hi Harsh ,

Can we please add the issue above as an Unplanned/Critical task.

Thanks,

Morgan

Hi Paul ,

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

Thanks, Harsh . 

This is a regression issue with a slightly different twist. The examples used in the video are found under SN Master Tree C - Costs - Treatment of Costs under the ICSID Convention - Tribunal discussions and D - Damages - Interest - Tribunals holding that "full reparation" requires the payment of interest. It has to be addressed throughout the SN Master Tree and fully audited, so users are not presented with wrong data.

SN Master Tree dupliate entries with wrong dispute document UINs.mp4 18.1 MB • Download

app.islg
https://app.investorstatelawguide.com/SubjectNavigator/Index?branchid=Bneh9zfnK-Y%3D&docid=y13oO7-lVnE%3D

image.png 63.3 KB • Download

Hi Harsh and Martin ,

Could you please resolve the above as an Unplanned/Critical task. It appear some erroneous data is getting associate with certain branches in the SN master tree.

Thanks,

Morgan 

Hi Morgan and Paul ,

The above issue is resolved on app.islg and we are doing auditing to find this type of entries in SN Tree and will update you soon.

Hi Harsh ,

The following UN/0170/03 SN entry needs to be fixed as well as part of your audit.  This SN entry appears twice under Master Tree and Reports. And you'll see that the wrong UIN is entered -> IC/0106/02.  The correct UIN is UN/0170/03.

Screen capture from app.islg SN Analysis List for UN/0170/03:

image.png 23.9 KB • Download

Screen capture from app.islg SN Master Tree and Reports:

image.png 38.2 KB • Download

Thanks,
Irit

Hi Harsh :

We will leave this item open until you confirm you've done a full audit throughout the SN Master Tree.

Thank you,

Paul

Hi Harsh and Martin ,

Could you please discuss how an audit could be performed and report back to us.

Thanks,

Morgan

Hi Irit ,

Could you please provide whole SN master tree hierarchy where you find UN/0170/03 and IC/0106/02 entries.

Hi Harsh ,

The two entries can be found here in SN:

J >
Jurisdictional issues under investment treaties >
"investment" and "investor" (definitions) >
Treaty definitions of "investment" and "investors" >
General discussions and findings by specific tribunals

Dayyani v. Korea Judgment of the English High Court of Justice accepts that an asset for the purposes of the BIT definition of investment must have value, but disagrees that it should be marketable - IC/0106/02 - Toto Costruzioni v. Lebanon Award - 07 June 2012

Dayyani v. Korea Judgment of the English High Court of Justice accepts that an asset for the purposes of the BIT definition of investment must have value, but disagrees that it should be marketable - UN/0170/03 - Dayyani v. Korea I Judgment of the English High Court of Justice - 20 December 2019

Thanks,
Irit

Hi Irit ,

The above mentioned wrong entry issue is solved on app.islg. Please check and confirm.

Hi Harsh ,

The wrong entry is still on app.islg.  This has not been resolved. 

Irit

Hi Irit ,

I have checked on app.islg admin side and as per your above comment I have removed the following branch.

Dayyani v. Korea Judgment of the English High Court of Justice accepts that an asset for the purposes of the BIT definition of investment must have value, but disagrees that it should be marketable - IC/0106/02 - Toto Costruzioni v. Lebanon Award - 07 June 2012


You can see following screenshot.

image.png 190 KB • Download

Please check again let me know if i am wrong.

Hi Harsh ,

When I enter "Dayyani" in the search field of the Subject Navigator, I still see the duplicate entry.

image.png 93.9 KB • Download

See video:

2021-11-16 2-13-58 PM.mp4 2.74 MB • Download

However, when I open each SN branch, I do not see it.
J >
Jurisdictional issues under investment treaties >
"investment" and "investor" (definitions) >
Treaty definitions of "investment" and "investors" >
General discussions and findings by specific tribunals

image.png 67.6 KB • Download

cc Martin  

Hi Irit ,

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

Cc : Martin  

Great, thank you Harsh.
Irit

Hi Irit :

When you check specific entries, please do not mark this complete, as we need to come up with the way to audit this problem as I specified below.

image.png 10.3 KB • Download

Harsh and Martin : the latest example is found under A - Annulment under the ICSID Convention - Stay of enforcement of award during annulment proceedings - General discussions on stay of enforcement of the award.

SN Master Tree dupliate entries with wrong dispute document UINs-2 (24-Nov-21).mp4 4.23 MB • Download

Thanks,

Paul

Hi Paul Irit and Martin ,

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

Also, As per above video, I audited some more deeply in database and found the UIN's list which we need to check for SN entries. As per my knowledge the following list is final UIN list which we need to check.


AF/0005/03
AF/0006/05
AF/0012/02
AF/0014/03
AF/0020/02
AF/0023/14
AF/0031/02
AF/0033/30
AF/0044/04
AF/0045/24
AF/0045/25
AF/0053/09
AF/0058/01
AF/0058/02
IC/0005/03
IC/0018/04
IC/0020/02
IC/0023/04
IC/0025/02
IC/0025/05
IC/0025/06
IC/0026/01
IC/0026/03
IC/0029/03
IC/0038/11
IC/0045/03
IC/0046/01
IC/0048/03
IC/0062/06
IC/0062/07
IC/0064/02
IC/0067/02
IC/0067/04
IC/0068/03
IC/0068/04
IC/0068/29
IC/0068/32
IC/0069/01
IC/0069/02
IC/0077/03
IC/0082/02
IC/0086/16
IC/0090/05
IC/0091/184
IC/0095/01
IC/0097/01
IC/0097/06
IC/0108/13
IC/0111/01
IC/0111/02
IC/0117/02
IC/0117/12
IC/0118/02
IC/0118/03
IC/0130/09
IC/0148/01
IC/0148/05
IC/0156/01
IC/0156/03
IC/0160/34
IC/0160/40
IC/0165/17
IC/0173/01
IC/0173/03
IC/0177/05
IC/0177/06
IC/0177/07
IC/0179/09
IC/0179/13
IC/0184/04
IC/0210/05
IC/0216/03
IC/0223/01
IC/0231/01
IC/0231/04
IC/0232/01
IC/0236/07
IC/0236/08
IC/0247/05
IC/0250/09
IC/0252/02
IC/0252/03
IC/0256/02
IC/0256/04
IC/0256/06
IC/0259/02
IC/0263/03
IC/0267/34
IC/0273/02
IC/0278/11
IC/0284/05
IC/0284/06
IC/0293/04
IC/0299/02
IC/0300/01
IC/0300/03
IC/0300/05
IC/0301/01
IC/0301/05
IC/0301/07
IC/0304/02
IC/0307/02
IC/0310/03
IC/0311/01
IC/0311/03
IC/0324/03
IC/0324/04
IC/0324/06
IC/0324/09
IC/0380/01
IC/0380/02
IC/0389/08
IC/0389/09
IC/0394/01
IC/0396/01
IC/0396/02
IC/0404/01
IC/0405/01
IC/0405/02
IC/0408/01
IC/0408/02
IC/0408/03
IC/0417/01
IC/0417/03
IC/0418/01
IC/0419/01
IC/0423/01
IC/0431/01
IC/0457/01
IC/0467/01
IC/0484/01
IC/0484/02
IC/0496/01
IN/0001/01
IN/0001/02
IN/0019/01
IN/0019/03
IN/0019/05
IN/0046/01
IN/0046/02
IN/0059/01
IN/0059/03
IN/0074/03
IN/0086/03
IN/0086/14
IN/0087/01
IN/0088/08
IN/0088/10
IN/0089/01
IN/0089/02
IN/0090/05
IN/0090/12
IN/0093/01
IN/0093/03
IN/0093/04
IN/0093/05
IN/0093/09
IN/0101/02
IN/0101/05
IN/0101/06
IN/0107/04
IN/0135/01
IN/0135/02
OT/0003/02
OT/0005/01
OT/0022/01
SC/0004/03
SC/0011/01
SC/0012/02
SC/0015/01
SC/0015/58
SC/0015/62
SC/0021/01
SC/0027/01
SC/0028/04
SC/0028/05
SC/0032/02
SC/0032/03
SC/0034/01
SC/0034/02
SC/0042/01
UN/0028/09
UN/0031/74
UN/0039/02
UN/0040/02
UN/0041/02
UN/0045/69
UN/0049/10
UN/0072/15
UN/0082/02
UN/0087/02
UN/0092/69
UN/0095/62
UN/0095/64
UN/0095/66
UN/0097/06
UN/0097/08
UN/0101/09
UN/0101/10
UN/0101/11
UN/0156/06
UN/0171/02
UN/0172/01
UN/0177/18
UN/0188/01
UN/0188/02
UN/0192/03
UN/0242/01
UN/0243/01
UN/0245/01
UN/0248/03
UN/0248/04
UN/0254/01
UN/0265/01
UN/0294/01

Hi Harsh :

The specific example above is resolved. However, there are still two issues:

Martin : we will need to accurately capture the UINs with this issue, so when we actually do audit the UINs, we catch all problematic entries. 

Thanks,

Paul

Hi Paul , Irit and Martin ,

We have removed those 2 entries which shown in above video on app.islg.

Paul ,  You are right that we need to audited more accurately to capture all these wrong entries.

I did update my automated query to find those UIN's for inaccurate SN tag entries. Here, I have attached spread sheet for those UINs.

I found total 624 UINs.  It is not like all 624 UIN's SN tag entries are inaccurate but we need to check those UIN's entries for confirmation.

I am thinking on how will check through query and will update you once get any idea.

Meanwhile, if you found this kind of entries on SN tree then let us know so we can remove from database.

SN_Incorrect_entries_UIN_26112021.xlsx 36.9 KB • Download

Hi Harsh ,

If you feel this project will require some effort (>4 hours), I can create a backlog item that would focus on auditing and correcting the issues found. We can then add this item to our next sprint.

Thanks,
--Martin

Hi Martin ,

Yes. you can create new item for next sprint for 8 hours effort time o audit SN entries.

Hi Harsh ,

I just want to confirm: will the 8 hours be sufficient to audit and fix issues found?

Thanks,
--Martin

Harsh and I further discussed this.

I have created backlog item 1250 and put it at the top of our backlog, which means it will be picked up at our next sprint.

Within this item, we will build a query that will identify the incorrect entries.
Once we have a narrowed down list, we will then manually fix the incorrect entries.

Hi Harsh and Martin :

The Backlog item 1250 looks good to me. Yes, please include this item in the next sprint.

Thanks,

Paul

Hi Paul , Irit ,

Is there any chance that SN branch have multiple Document Reference data ? if yes, then is it possible for you to provide those SN branches ?

Hi Harsh :

Yes, some SN entries will have more than one UIN.

Nafiseh : could you coordinate with Irit and provide Harsh with UINs that we enter together on SN? For example, I am referring to some of the UN/0039, UN/0040 and UN/0041 documents that we entered together in terms of SN entries (one narrative and three UINs tagged). Some other examples that come to mind are AWG/Suez awards and Pezold/Border Timber documents.

Thanks,

Paul

Hi Paul ,

Sure, will do.

Thanks,

Nafiseh

Hi Harsh , please see the list of UINs that are entered together on Subject Navigator:

SN Entries with More than One UIN (1).xlsx 16.1 KB • Download

In this list are Subject Navigator entries that have more than one UIN.

For example, SN entries for the following have one narrative but three UINs tagged:

Issue:

If you look at Dispute Documents AH/0005/01, IC/0051/48 and SC/0027/01 ->Analysis List -> Subject Navigator, you will see that these three have SN entries that need to be removed. (From these three, only SC/0027/01 is in Harsh's audit list above from November 25th).

Hi Irit :

Could you check this and report back here?

Thanks,

Paul

Hi Paul,

The specific example I shared above (on December 16th) has been resolved. But there are still issues from the spreadsheet I attached that day.

Another example, SN entries for the following have one narrative but three UINs tagged:

See app.islg admin site, Master Tree and Reports, Subject Navigator
B > Bad faith > Elements of bad faith

Hulley Enterprises v. Russia, Yukos v. Russia, Veteran Petroleum v. Russia Judgments of English High Court of Justice observe it is not unusual for defendants or award respondents to be unwilling to pay unless and until forced to do so, even following a final judgment or award against them; that is (along with inability to pay) one of the reasons why enforcement processes are necessary; it is not accurate to conclude that it means that any challenge such a party may make – even one brought on reasonable grounds and with a genuine belief in its prospects – is to be regarded as made in bad faith

The Short Titles of the three UINs are placed together in one entry.   

image.png 32.6 KB • Download

On app.islg admin site, Master Tree and Reports, Subject Navigator, this entry should appear three times, with the UINs UN/0039/54, UN/0040/61, and UN/0041/54.  Instead it appears four times.  Incorrect UINs include IC/0430/01

image.png 88 KB • Download

LIVE SITE
See app.islg live site, Research Tools, Subject Navigator
B > Bad faith > Elements of bad faith

Hulley Enterprises v. Russia, Yukos v. Russia, Veteran Petroleum v. Russia Judgments of English High Court of Justice observe it is not unusual for defendants or award respondents to be unwilling to pay unless and until forced to do so, even following a final judgment or award against them; that is (along with inability to pay) one of the reasons why enforcement processes are necessary; it is not accurate to conclude that it means that any challenge such a party may make – even one brought on reasonable grounds and with a genuine belief in its prospects – is to be regarded as made in bad faith

Again, you will see four Dispute Documents appearing instead of just the three.

image.png 95.5 KB • Download

Issue:

If you look at Dispute Documents IC/0430/01 ->Analysis List -> Subject Navigator, you will see that it has SN entries that need to be removed. (I do not see IC/0430/01 in Harsh's audit list above from November 25th).

Hi Martin and Harsh :

DevOps #1250 was marked as installed on Production, but the problem persists, and I found new issues as shown below. 

SN Master Tree showing phantom UIN IC-0125-03(12-Jan-22).mp4 4.93 MB • Download

Martin : I am getting quite concerned about this issue. When you talk to Harsh next, could you figure out what he did, so we can try to address this lingering problem?

Thanks,

Paul

Hi Paul ,

I think it would be best if you, Harsh and I have a meeting next week to discuss this.
Would Tuesday 8:15am your time work for you?

Thanks,
-Martin

Sure, Martin . Please send me the meeting invitation.

Thanks,

Paul

Another example of a type of audit required that is not addressed by Subject Navigators entries displaying incorrectly - TOLOGIX - ISLG App Rebuild for Tologix.

SN audit erroneous result 3 (20-Jan-22).mp4 2.15 MB • Download

Hi Irit   and Paul ,

We have audited SN Entries and prepared the following attached sheet. 

We added whole path of SN entries so please check on app.islg and mentioned the Wrong UINs number in Wrong UIN columns.

If the branch is OK then you set blank in Wrong UIN column. I also discuss same thing with Martin so you can also ask to Martin if you have any question.

Cc : Martin

SN_Wrong_Check_Entries_25012022.xlsx 161 KB • Download

Hi Harsh :

Are you asking the content team to fill out column C of the spreadsheet (Wrong UIN)?

There are over 900 SN entries on the list, and the content team cannot manually check each SN entry to identify which UIN(s) should be deleted.

Martin : can DevIT compare the identified SN entries on the spreadsheet against the legacy admin site and delete incorrect one(s) after?

Thanks,

Paul

I have scheduled a meeting for Friday morning so we can further discuss this point.

Thanks,
-Martin

During the call on Friday, the following should also be considered together:

IC/0106/02 SN Analysis List entries (phantom entries) - TOLOGIX - ISLG App Rebuild for Tologix;
Subject Navigators entries displaying incorrectly - TOLOGIX - ISLG App Rebuild for Tologix;
Once wrong SN UIN is removed, it becomes a phantom entry - TOLOGIX - ISLG App Rebuild for Tologix; and
New SN entries inserted adding random incorrect UINs - TOLOGIX - ISLG App Rebuild for Tologix.

Thanks,

Paul

 Consolidating to DevOps 1449

Hi Paul , Irit , Nafiseh and Martin  

Today, We have completed the audited of SN Wrong, Duplicate and Phantom entries on app.islg.

We have removed those Wrong, Duplicate and Phantom entries from database. Now you can not see those entries anywhere in application. if you still able to see this kind of entries then please let us know without delete it.


Also, Please read the following 2 points and provide your feedback.


1)   There are 61 SN Branches where we haven't an idea that these entries are right or                wrong. Please go through the attached sheet and check those 61 SN branches on            app.islg and let us know which associated UIN we need to remove.

SN_61-Branch_Check.xlsx 17.3 KB • Download

2)  One more thing that we haven't checked those SN branches which associated more       than one Dispute Document references. These document's UIN list provided from           your team on 17th December as per following screenshot.

    Hence, for your reference here I have again attached sheet of those Dispute                     Document UIN's which we didn't check.

image.png 141 KB • Download

UIN_NotCheck_ForSN_Phantom_Entries.xlsx 12.1 KB • Download

 

Now, we are done with this task except those 61 branches which you need to check and confirm to us weather is it correct or wrong.

Hi Harsh ,

I found an incorrect deleted entry in the SN. It is not part of your 61 SN Branches spreadsheet provided today. I posted the incorrect deleted entry here.
Subject Navigator incorrect deleted entry (UN/0128/53) - TOLOGIX - ISLG App Rebuild for Tologix


Harsh ,

In your spreadsheet of 61 SN Branches that need our attention, what are the empty  rows?

image.png 35.3 KB • Download

 Marked as resolved under DevOps 1449