TOLOGIX - ISLG App Rebuild

New SN entries inserted adding random incorrect UINs

Assigned to
Martin Laporte, CTO at Tologix Martin L.

Comments & Events

Paul Moon
Hi Martin Laporte, CTO at Tologix Martin :

I might have identified a partial issue behind the ongoing SN Master Tree issue. It looks like when admin users insert SN entries (directly under SN Master Tree in the example below, but it still happens when admin users highlight HTML), the system is adding random UINs even though the analyst did not add wrong UINs. It appears to be a bug to me.

Even if I tried to remove random wrong UINs, one gets removed (UN/0304/01), but the other does not even appear (IC/0198/20) as an option for removal similar to Once wrong SN UIN is removed, it becomes a phantom entry - TOLOGIX - ISLG App Rebuild for Tologix. This needs to be addressed as priority, as it affects all new SNs. Please add it to critical/unplanned. The Content Team cannot proceed with new SN entries with this error.

Thanks,

Paul
Harsh Parikh, Tech Lead at DevIT
Hi Paul Moon Paul ,

Did you performed this scenario on app.islg ? Because We haven't found this issue. Could you please do same test case on staging.islg and provide video to us so we can investigate more deeply.
Harsh Parikh, Tech Lead at DevIT
Hi Paul Moon Paul ,

Could you please check now on app.islg and Provide your feedback.

Cc : Martin Laporte, CTO at Tologix Martin  
Paul Moon
Hi Harsh Parikh, Tech Lead at DevIT Harsh :

The problem is not resolved. As you see in the video below, there is a phantom UIN (IC/0256/02) created for the previous entry when I entered an entry under IC/0565/11 as shown in the video below.

This is what you'll see now under  E - Evidence - Witness statements and expert reports.


Can you explain what you actually fixed, so Martin Laporte, CTO at Tologix Martin could explain what you are doing further to me?

Thanks,

Paul
Martin Laporte, CTO at Tologix
Hi Harsh Parikh, Tech Lead at DevIT Harsh ,

As we have discussed yesterday, please make sure to always include a [Tech] comment in the DevOps task, so we can understand the resolution path.

Thanks,
-Martin
Martin Laporte, CTO at Tologix
Hi Paul Moon Paul ,

Harsh Parikh, Tech Lead at DevIT Harsh mentioned in our meeting today that he will be able to investigate this tomorrow.

Thanks,
-Martin
Paul Moon
Thanks, Martin Laporte, CTO at Tologix Martin .

The strangest thing is that when I went back to the branch with a phantom entry (see 2:01 mark of SN Master Tree direct SN entry adding phantom UINs 3 (25-Jan-22).mp4 above) this morning, it no longer exists. It seems the phantom entry disappears after refreshing or reopening the browser.
Harsh Parikh, Tech Lead at DevIT
Hi Paul Moon Paul and Martin Laporte, CTO at Tologix Martin ,

We have investigated this problem and there was an issue in stored procedure while create draft version. It is technical bug.

We have resolved this on staging.islg and our QC is doing testing on it with different different scenarios.

Meanwhile, I would request you to don't  create draft version on app.islg until Monday or Tuesday.

We will update you once testing will be done on staging.islg.
Paul Moon
Hi Harsh Parikh, Tech Lead at DevIT Harsh :

Based on our call today, the Content Team will continue to create draft on app.islg. 
We look forward to your confirmation next Thursday about deleting all erroneous entries. 

Thanks,

Paul
Harsh Parikh, Tech Lead at DevIT
Hi Paul Moon Paul ,

Based on our discussion on Friday call, Today, We have resolved this issue on app.islg. Please check and confirm.

Still there are near about 200 UINs we need to check for SN entries which will try to complete before end of this week.

Cc : Martin Laporte, CTO at Tologix Martin  
Paul Moon
Hi Harsh Parikh, Tech Lead at DevIT Harsh :

When you said you resolved this issue, did you mean the phantom entry creation part or deleting all erroneous SN entries?

For erroneous SN entries, I still see issues as shown below in  J - Judicial (or procedural) economy - Bifurcation - Findings in specific cases. The highlighted UINs are incorrect ones with SN branch repeating after the previous correct entry.


Should the Content Team wait until you finish your audit on Friday before we test erroneous entries? 

Thanks,

Paul
Paul Moon
Hi Harsh Parikh, Tech Lead at DevIT Harsh :

Please respond as we received the first client complaint about the SN mix up on the live site. I attach further observations so far. 

Martin Laporte, CTO at Tologix Martin : the video below shows how some corrections have gone wrong. Should I post it as a separate item? I think Harsh Parikh, Tech Lead at DevIT Harsh still needs to be aware of this issue when auditing/fixing the SN Master Tree.

Thanks,

Paul
Paul Moon
 Consolidating to DevOps 1449
Irit Weinfeld
Hi Harsh Parikh, Tech Lead at DevIT Harsh , I have two questions.

Referring to this video Paul posted above (Feb-2-2022):


Paul is referring to this SN entry:
E
>European Union (relationship of investment treaties, EU law and EU member States)
>Relationship between EU law and Energy Charter Treaty
>Watkins v. Spain Award, based on an interpretation of Article 26 in light of Article 1(10), and in conformity with customary rules of treaty interpretation, concludes it has jurisdiction as the dispute in question opposes investors of several ECT contracting parties (i.e., Luxembourg and the Netherlands) to another contracting party (i.e., Spain); citing the ECJ’s Micheletti decision, the tribunal observes European citizenship is based on superimposition on the nationality of an EU member State, which does not take out any élément d’extranéité

Screen capture below from app.islg live site Subject Navigator.  As Paul pointed out in his video, the wrong UIN is listed. AF/0023/14 Mobil and Murphy v. Canada is the wrong entry.  
  1. The correct entry is: IC/0422/01 - Watkins v. Spain Award. However, it is no longer on app.islg admin site or live site. Question for Harsh Parikh, Tech Lead at DevIT Harsh : was this correct entry deleted from app.islg admin site during your audit?
  2. This SN entry is not included in the spreadsheet provided by Harsh Parikh, Tech Lead at DevIT Harsh   (Jan-25-2022). Harsh, does this spreadsheet include all the duplicate SN entries you found?
***
Let's look at this entry on legacy.islg admin site.  The correct UIN (IC/0422/01) is entered. Paragraph 186, 188 are entered.
Now let's look at this entry on app.islg admin site.  The wrong UIN (AF/0023/14) is entered. And the wrong paragraph numbers are entered (pa216-225).  

***
If we were to edit the entry on app.islg admin site, we would have to change the UIN and the paragraph numbers.  I'm confused as to why those incorrect paragraph numbers appear.  If we look at the UIN for AF/0023/14 SN Analysis on app.islg admin site, we see this. 
There is another entry for AF/0023/14 that has these same paragraph numbers (pa216-225)  listed. The bottom entry (Watkins v Spain) is the "phantom" entry and needs to be deleted.

Screen capture for app.islg admin site

Irit
Harsh Parikh, Tech Lead at DevIT
Hi Paul Moon Paul ,

The "phantom" entries and wrong UIN's entries removal tasks is going on. We are in the middle of this task.

so, please wait till this sprint. We will update you once all erroneous entries will remove from SN Master Tree.

Irit Weinfeld Irit , You are right. By mistake, I was removed right entry from database because this task we are doing manually through database. I correct that entry on app.islg.

I will take care now before remove the entry.

Cc : Martin Laporte, CTO at Tologix Martin  
Paul Moon
Thanks, Harsh Parikh, Tech Lead at DevIT Harsh .
Paul Moon
 Marked as resolved under DevOps 1449
Paul Moon
Paul Moon completed this to-do.