Hi Harsh :

Please see the issue below, thanks.

Applicable Instruments missing from certain disputes (16-Sep-20).mp4 3.88 MB • Download

Paul

Thanks Paul ​.

Harsh ​, I'll add this to the agenda for discussion tomorrow.

Thanks,

Morgan

Hi Morgan   and Paul ,

We gone through into data and found that there was 2 issues.

1) The Treaty UIN contains extra  space or tab in old islg database. Hence those Treaty UIN were not captured by our script while we migrated data in June.

There are near about total 287 dispute which contains this kind of mismatch Applicable Treaty data. (For example, IC/0389)
  - We updated only those 287 dispute's Applicable Treaty data on rebuild.islg and update query is executed successfully. (You can check dispute UIN IC/0389)
(This issue is resolved on rebuild.islg.)

2) The second issue is in UIN Master list spread sheet that following Treaty UIN separated with "and"  & "," in sheet. Hence, our script were notable to matched those Treaty UIN data because as described in Mapping Sheet we separated Treaty UIN with ";".

Also, The Following Dispute has Treaty UIN but those Treaty UIN data does not exists in our UIN Master List Spread Sheet.

We will discuss in today's call.

 

Hi Harsh :

Thanks your explanation. We will make sure the UIN Master List for the next migration doesn't contain "and" or "," in entries. I've manually entered applicable instruments(s) for all 8 disputes you've identified above.

Paul

Hi Harsh ,

Something to note about issue #1 above. The spaces entered into the fields in the existing application were not the result of admin user error. For some reason, the spaces get inserted when data is added to certain fields on the admin site on the existing application. Therefore, when we perform the next migration, this problem should be noted, and a step should be taken when exacting the data from the existing application that removes any unwanted spaces from fields where the problem occurs.

Thanks,

Morgan 

Hi Harsh :

Another issue that might be related to your explanation is BIT/0887. It is an instrument that exists on rebuild.islg as shown below.

image.png 26.3 KB • Download

It applies to UN/0170, and existed before the June migration. However, the applicable instrument(s) section is left blank. When I try to add BIT/0887, it doesn't appear as an option. Unlike #2 you described above where I could manually add the applicable instrument(s), I am unable to add it.

image.png 11.9 KB • Download

When I look at the file name, this is how appears.
BIT-0887 - Iran - Korea Republic BIT (1998) + Exchange of Notes [English].pdf 
Is the "+" in the file name causing this issue? It is one thing for me to be able to manually add the instrument, but this is a different issue where I cannot manually add the instrument even though the instrument exists on rebuild.islg. How could I address this issue?
 
Thanks,

Paul

Hi Paul ,

As per requirement, We pull only Primary language data for Treaties, Arbitration and Dispute Document.

Hence, BIT/0087 is not a Primary language document. so you are not able to see that document in Applicable Instrument(s) field for any dispute.

Hi Harsh and Paul ,

Taking a closer look at this it appears that no document was marked as the Primary document in rebuild.islg:

image.png 129 KB • Download

This appears to be a result of an error in UIN master list. Further to the instructions concerning Primary documents in the ISLG Data Migration Map: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0

image.png 110 KB • Download

a document would be marked as "Primary" if indicated as such in the UIN master list under column P. However, as the screenshot below shows, this wasn't done for BIT/0887:

image.png 236 KB • Download

Paul and Nafiseh , it appears that this may be problem with other documents as well. We'll need to perform an audit on when this was missed, and correct things accordingly within the UIN master list and within the application.

Thanks,

Morgan 

Hi Paul and Nafiseh ,

Could you confirm whether the data capture issue above is resolved, and then I'll mark this to-do complete.

Thanks,

Morgan 

Hi Morgan :

Nafiseh and I will make sure that we audit the primary version of BIT and Treaties before the next migration.

Thanks,

Paul 

Ok. Great. Thanks Paul . I'll keep this to-do open until you confirm.

Thanks,

Morgan

Hi Morgan and Paul ,

The audit of column P on the UIN Master List is complete. The required changes have been made and time-stamped.

Thanks,

Nafiseh

Perfect. Thanks Nafiseh . I'll mark this to-do complete.

Morgan 

Thank you,  Morgan .