Hi Harsh ​,

Nafiseh ​ has provided an example of the issue above, but let's ensure this is resolved across the system.

Thanks,

Morgan

Hi Morgan and Nafiseh ,

We checked and found that Pa228 was tagged 2 times. In Generally and also Paragarph 279.

As per requirement, We are displaying all tagging reference under All Reference  in rebuild.islg. Hence, The All tagging data will be display under All References. That's why it will display multiple times and this things we already conveyed with Melisa.

Hi Harsh ,

First, for some reason I can't access the analysis data within rebuild.islg or staging.islg for IC/0295/03:

image.png 121 KB • Download

Should I be able to access this if the document has been marked as "HTML pending complete"?

Second, looking at a different example of this issue in the Publication Citator raised here: Re: Duplicate References in Publication Citator on the Staging Live Site - TOLOGIX - ISLG App Rebuild with the references to PUB/1273/3302 within IC/0274/01, we appear to have a problem in the way the data was migrated from the legacy application to the new application in both the Jurisprudence Citator and Publication Citator.

Using the example in IC/0274/01, here is how the data referring to PUB/1273/3302 was entered: https://www.investorstatelawguide.com/CoreComponents/PublicationsReferredTo?docid=6884

image.png 71.2 KB • Download

This shows both specific reference to "Page 1" of PUB/1273/3302 and an All Citations references to PUB/1273/3302.

As we've discussed previously, in the legacy application, in order for a specific reference to appear in both Specific References and General References:

image.png 191 KB • Download

image.png 163 KB • Download

both a specific reference and All Citation reference need to be created for each entry:

As you've pointed out, the new application does not required separate data to generate the All References reference. When a Specific Reference is entered, it automatically gets includes as an All Reference.

As a result of this difference in the way data is stored in the applications, appropriate changes should have been made to the legacy application data before it was uploaded into the new application. For example, with the reference above, there should have only been a specific reference to "Page 1" to PUB/1273/3302 and no general reference to PUB/1273/3302:

image.png 96.6 KB • Download

In addition, in the example original posted above, for references to IC/475/02 contained within IC/0295/03:  https://www.investorstatelawguide.com/CoreComponents/JurisprudenceReferredTo?docid=12768

image.png 53.2 KB • Download

the legacy data is further complicated by the fact that it contains both specific references and general references to IC/475/02, which are combined in the All Citation references. Specific references are represented by both a specific reference and All Citation reference:

image.png 79.8 KB • Download

Whereas the general references are only represented with the All Citation reference:

image.png 78.4 KB • Download

This means that the data in the IC/0475/02 should have been altered and then uploaded into the new application as follows:

which would have eliminated the double reference within All References.

Now, I'm certain that this issue was raised in preparation for the data migration, but it appears the issue was not addressed and we are going have this problem across both the Jurisprudence Citator and Publication Ciator (this shouldn't be an issue for the Article Citator, because the legacy data was stored differently). As a result, we'll need to fix the problem with data across the system. 

I'm going to add this to the agenda for discuss during our meeting on tomorrow. In the meantime, could you please investigate the issue and come up with some possible solutions for discuss during the meeting.

Thanks,

Morgan

Because the issue above is a data problem, I'm moving the to-do to ISLG Migration Feedback - TOLOGIX - ISLG App Rebuild.

Thanks,

Morgan

Hi Harsh ,

Following up on our discuss this morning, this issue in the Jurisprudence Citator and Publication Citator needs to be resolved by changing the Analysis data in the new application as follows:

Here is the Analysis list for AF/0001/02, which contains my mark-ups above in the Jurisprudence Citator tab:

AF-0001-02-Analysislist.xlsx 35.4 KB • Download

Please review and let me know how we should resolve the issue in both the Jurisprudence Citator and Publication Citator.

Thanks,

Morgan

Hi Harsh ​,

After reviewing the issue in the Article Citator where this issue is present as well: https://3.basecamp.com/3691577/buckets/5559242/todos/3385820164, I'm wondering if the simpler solution is to modify the requirements for "All References" so that it automatically combines references from the same paragraph or footnote. In other words, when the location paragraph/footnote is the same between two references, the application automatically suppreses or combines them into a single reference.

This might be simpler than trying to modify the analysis data, and modifying the analysis data wouldn't resolve the issue in the Article Citator.

Let me know your thoughts.

Thanks,

Morgan

Hi Harsh ,

Further to my comment above and our discussion last week about the duplicate references that are appearing within the Article Citator, Jurisprudence Citator and Publication Citator within "All References", I've created the video below to try and explain my proposed solution to this problem across all the different tools.

Essentially the idea is to change the requirements of "All References" under all three tools so that when there are multiple references to an instrument within the same paragraph of a dispute document (example from AF/0003/05):

image.png 124 KB • Download

the systems would identify the redundancy, and only create one paragraph reference within "All Reference":

image.png 206 KB • Download

and would combine all the applicable excerpts into one excerpt:

image.png 321 KB • Download

I know this isn't a simple solution, but it would avoid the need to alter any of the migrated data within the Jurisprudence Citator and Publication Citator, and would resolve the issue across all three tools (rather than just the Jurisprudence Citator and Publication Citator).

Could you and Ketan please discuss the viability of this solution compared to altering the data within the Jurisprudence Citator and Publication Citator, and we'll discuss during tomorrow's call.

Thanks,

Morgan

Possible solution to duplication references within Citators (17-Feb-21).mp4 18.3 MB • Download

Hi Morgan ,

As discussed, Here, I have attached Excel Sheet which contains 2 tab JC & PC.

These all are the tagged data which we found same Paragraph tagging data in Specific Reference as well as in All References.

The Spread Sheet data contains All References tagged data.


Please review the Sheet and confirm to us. If it is Ok then will remove this Excel Sheet data from database.

JC PC Dupliate Excerpt List.xlsx 941 KB • Download

Great. Thanks Harsh .

Let me coordinate with Paul on getting this list verified and then we'll get back to you with feedback later this week.

Thanks,

Morgan

Hi Morgan :

Irit has checked the following UINs, and it seems like Harsh 's solution caught everything. 

JP Citator

Pub Citator

Thanks,

Paul

Perfect. Thanks Paul .

Harsh , looks like we are ready to delete the entries in your spreadsheet above. As we discussed, please remove the data on staging.islg first, so that we confirm it worked as expected, and then we'll perform the same on app.islg.

Thanks,

Morgan 

Hi Morgan and Paul ,

We have removed  duplicate all references data from JC & PC module on staging.islg.

Please check and confirm.

Great. Thanks Harsh ​.

I'll review the data on staging.islg and confirm whether there are any issues.

Morgan

Hi Morgan :

It looks like the references that had to be kept are deleted and what had to be deleted are kept as shown in the video.

JP Duplicate Staging results (1-Mar-21).mp4 10.6 MB • Download

Thanks,

Paul

Hi Harsh ,

Further to the Paul 's comments above and my video below, it looks like the problem has been created by the fact that all of the location references contained within any of the generally referenced flagged in your spreadsheet above were deleted, rather than only the deleting the location references flagged in the spreadsheet. This resulted in deleting "pure" general references where no specific reference exists, and now we have missing data in the tools (as pointed out by Paul 's comments above).

Could you please reperform the fix, but ensure only references to the locations flagged in the spreadsheet are deleted, which means that any other location references contained in the same generally reference would be maintained.

Problems with updated analysis data (1-Mar-21).mp4 5.33 MB • Download

Thanks,

Morgan

Hi Morgan and Paul ,

I see the problem and we revert back the data and again execute query after modification.

As per Paul 's First document example,  We have removed only those duplicate generally Paragraph/footnote tagging data which references to both citation type (specific & generally).

Please see my attached screen shot and checked again on staging.islg.
 

 

Duplicate-JC-PC.png 232 KB • Download

Great. Thanks Harsh . Let us know when the data is updated and we'll check again.

Thanks,

Morgan

Hi Morgan ,

The data is updated on staging.islg for both jc and pc tool on staging.islg. please check and confirm.

Hi Harsh ,

Thanks for turning that around so quickly.

Paul , after my initial look at the analysis, everything looks good, but could and Irit take a look to confirm.

Thanks,

Morgan

Hi Harsh :

The issue is resolved for JC and PC only when I checked IC/0092/02 analysis list. Irit : please randomly pick a few UINs and confirm as well.

Thanks,

Paul

Hi Morgan , Paul and Harsh ,

For JP Citator, I picked three UINs to test (IC/0042/01, IC/0046/02 and UN/0140/01). The issue is resolved.  You can implement the updates on app.islg.

Thank you,
Irit

Hi Morgan , Irit and Paul ,

We have updated the duplicate data on app.islg. Please check and complete this task.

Great. Thanks Harsh .

Paul and Irit , could you please confirm that everything looks good on app.islg for both the JP and PB Citators.

Thanks,

Morgan

Hi Morgan , Paul and Harsh ,

Both JP and PB Citators look good on app.islg.  This issue has been resolved. 

Thank you,
Irit