Hi Harsh ,

Further to the issue posted by Nafiseh above, these documents were not flagged as having issues in your tagging report:

Data Migration Tagging Error Report.xlsx 219 KB • Download

and there are no problems with links in the Analysis list. However, the worrying issue is that the paragraph ranges were converted incorrectly from "1.8-1.9" to "1.2" (i.e., it completely altered the data). 

Could you explain how this happened, and is there way to audit and correct these types of errors across the system?

Thanks,

Morgan

Hi Morgan ,

As communicated earlier, There is chance that some tags are not properly converted though automated query and we need to look into manually. There is no other way to resolve this issue.

We need to update those tags manually in databse.

 

Hi Harsh ,

Following up on our call this morning, next week can you please investigate how "1.8-1.9" got converted into "1.2" when the legacy data was processed and migrated to the new application. We need to understand how this error in the data occurred so that we can identify and correct similar problems across the systems.

As we discussed, this may be a problem with all documents that have a decimal paragraph numbering system (where other problems have been identified: Problem with Tags referring to Paragraph Ranges - TOLOGIX - ISLG App Rebuild), but we need to identify the cause of this specific issue and then expand the investigation from there to ensure we come up with a comprehensive solution.

Thanks,

Morgan

Hi Morgan ,

I have sent excel sheet to here Re: Broken Tags - TOLOGIX - ISLG App Rebuild regarding decimal ranges paragraph migrated. we need to manually update those ranges which are not converted properly through automated query.

Great. Thanks Harsh ​. I'll review the report and then we'll continue the discussion under this thread.

Morgan

Hi Harsh ,

Here is an updated version of the Decimal Paragraph Ranges report:

DecimalPragraphRanges.xlsx 65.2 KB • Download

I've highlighted cells in the New Migrated Analysis Data columns where issues have been identified in the data. As you can see the issues are quite widespread, and affect most data where paragraph ranges were used. Here is a summary of the problems:

1. Paragraph range was ignored (yellow highlight)

These are entries where the paragraph range was ignored and the data was migrated without breaking up the range into individual paragraphs. There are two common characteristics among all these entries:

(a) paragraph contain multiple decimals

Paragraph ranges with paragraphs that contain multiple decimals were not broken up.

e.g., 10.3.1-10.3.3

e.g., 3.4.1.32-3.4.1.33

(b) paragraph contains letters or roman numerals

Paragraph ranges with paragraphs that contain letters or roman numerals were not broken up.

e.g., A.44-A.45

e.g., VIII.2.5-VIII.2.6

2. Paragraph range was misinterpreted (green highlight)

These are entries where the paragraph range was broken into separate entries, but errors occurred in the data it generated for those individual paragraphs. The common characteristic among all these entries appears to be presence of more than one character after the decimal.

e.g., "5.06-5.07" converted into "pa5-1"

e.g., "8.8-8.11" converted into "pa8.1;pa8.2;pa8.3;pa8.4;pa8.5;pa8.6;pa8.7;pa8.8"

3. Problem with data in table (red highlight)

These are entries where there appears to be a problem with the way the data was entered into the table or I was unable to identify the source of the issue.

Let me know if you have any questions. Otherwise, let me know how you think best to resolve these issues.

Thanks,

Morgan

Hi Harsh ,

Following up on above, here is the custom paragraph report:

CustomParagrph.xlsx 35.1 KB • Download

I've posted it here, because we'll need to address similar paragraph range issues as the documents above.

Thanks,

Morgan

Hi Harsh ,

Following up on your comments here: Re: Broken Tags - TOLOGIX - ISLG App Rebuild. I'll wait to here from you when you've confirmed that the data has been updated.

Thanks,

Morgan

Hi Morgan ,

As we discussed, The Decimal Paragraph Ranges we need to manually add/update in database.

We are starting this process and first we are focusing on yellow highlight data.

We need to update manually so we are updating on both databse app.islg and staging.islg.

Hope this is fine.

OK. Sounds good Harsh . Let us know if you need any further details to assist.

Morgan

Hi Morgan ,

As per following screenshot, Only few entries of Article Citator tool we have updated on both app.islg and staging.islg. You can check those entries with status column done.

Let me know once you verified so will go further to update data by manually on both app.islg and staging.islg.

image.png 285 KB • Download

Hi Harsh ,

Would it be possible to send us a copy of the spreadsheet itself? It's hard to examine the entries through the screenshot above.

Thanks,

Morgan

Hi Morgan ,

Here, I have attached spread sheet, Please see the data only for AC tool where I marked Done status .

Decimal_ParagraphRanges_16022021.xlsx 65.2 KB • Download

 

Hi Harsh ,

After reviewing the data above, it looks like the ranges were maintained, rather than separating them into individual paragraphs.

For example in row 14, the old analysis data was:

3.4.2.5-3.4.2.6;3.4.3.4

and the new migrated analysis date is:

pa3.4.2.5-3.4.2.6;pa3.4.3.4;

However, the new migrated analysis data should be: pa3.4.2.5;pa3.4.2.6;pa3.4.3.4

Similarly for row 20, the old analysis data was:

7.3.10;7.4.1;7.4.4-7.4.7;7.4.26;7.4.31;7.4.42-7.4.46;7.5.1;7.5.23;8.2.1;8.2.8;8.3.19;11.1

and the new migrated analysis date is:

pa7.3.10;pa7.4.1;pa7.4.4-7.4.7;pa7.4.26;pa7.4.31;pa7.4.42-7.4.46;pa7.5.1;pa7.5.23;pa8.2.1;pa8.2.8;pa8.3.19;pa11.1;

However, this should have been turned into the following:

pa7.3.10;pa7.4.1;pa7.4.4;pa7.4.5;pa7.4.6;pa7.4.7;pa7.4.26;pa7.4.31;pa7.4.42;pa7.4.43;pa7.4.43;pa7.4.45;pa7.4.46;pa7.5.1;pa7.5.23;pa8.2.1;pa8.2.8;pa8.3.19;pa11.1

Thanks,

Morgan

Hi Morgan ,

You need to verify the data on application. The New Migrated Analysis Data column data was the previous old data which we provided you. We are not modified data in that column.

You can verify the data directly on Analysis List of that Dispute Document on app.islg.

image.png 230 KB • Download

Please check and confirm.

OK. Understood Harsh . Paul and Irit could you please take a look at this on Monday? You need to examine the examples Harsh has marked in the spreadsheet above as "Done" and confirm that updated data has correctly separated the old paragraph ranges into individual paragraphs within the new application.

Harsh , is this updated data available on app.islg or staging.islg?

Thanks,

Morgan

Yes Morgan . The data is available on both app.islg and staging.islg.

Hi Harsh ​,

I took a look the updated anaylsis data for the Article Citator within app.islg and things look good. The ranges have been separated into individual paragraphs.

When Paul ​ and Irit ​ confirm, please apply the scripts to the remaining entries.

Thanks,

Morgan

Hi Morgan :

I've checked the following UINs: IC/0031/01, IC/0086/10 and SC/0008/01. They all look good on the admin site analysis list.

Irit : please pick three UINs from the spreadsheet above and confirm before Harsh could apply the scripts to the remaining entries.

Thanks,

Paul

Hi Morgan and Paul ,

From the items marked "done" on the spreadsheet, I checked the following Dispute Documents: 

IC/0014/01, IC/0138/02, UN/0070/01

The updated Article Citator analysis list on app.islg looks good. 

Thanks,
Irit

Perfect. Thanks Irit ​ and Paul ​.

Harsh ​, please proceed with updating the other entries.

Thanks,

Morgan

Hi Morgan ,

This process is continue through whole week to update the range data directly though back-end.

Ok. Understood, Harsh ​. Do you have an estimate on what percentage of the entries are complete? I want to understand how many entries will still have issues when we launch tomorrow.

Thanks,

Morgan

Hi Morgan ,

AC & TP module entries will be completed by tomorrow. 
JC will be done on Thursday and SN will be completed before next Monday.

Ok. Understood. Does that mean all the JP Citator entires are still pending or has a certain percentage been completed?

Morgan

Hi Morgan ,

We have updated AC, JC and TP decimal ranges data of all (yellow, green and Red) on app.islg.

We are working on SN Data and will let you know once it will be finished.

Great. Thanks for the update Harsh .

Morgan 

Hi Morgan ,

In SN decimal ranges, There is one range ( 4.1.1-4.4.6). Could you please provide your feedback that we need to split all paragraphs from 4.1.1 to 4.4.6.

Is it possible for you that provide list of splitting paragraph for this range ?

Hi Harsh ,

Could you confirm that this is the following reference from UN/0039/45?

image.png 63 KB • Download

If so please split this into the following individual paragraph references:

pa4.1.1
pa4.2.1
pa4.2.2
pa4.2.3
pa4.2.4
pa4.2.5
pa4.3.1
pa4.3.2
pa4.3.3
pa4.3.4
pa4.3.5
pa4.4.1
pa4.4.2
pa4.4.3
pa4.4.4
pa4.4.5
pa4.4.6

Thanks,

Morgan

Hi Morgan ,

This task is completed on app.islg. 

We have updated the all modules decimal range data as per spread sheet directly on app.islg.

Great. Thanks Harsh . Marking the to-do complete.

Morgan