Data Migration #2 Approach

Hi Morgan ,

As discussed, we can do migration of phase 1 again but we need to clean all data along with Legal Analytics data. Technical reason is the mapping of Dispute ID column in table we need to maintain as it is to load legal data which your team entering currently on rebuild.islg. so it is not possible to wipe all data except legal data.

And, second option is, if you want to keep legal data as it is then we need data from 10th June to 15th November in spread sheet so we can migrate only those newly added data.

Hi Harsh ,

Yes, the idea would be that all the data would be wiped, including the Legal Analytics data. However, we would need to back-up and restore the Legal Analytics data after you perform the migration. Is it possible for you back-up the Legal Analytics data in a separate SQL database and then merge it with the newly migrated data? Creating a separate spreadsheet for the data would be a messing process.

Ketan , could you we please schedule a separate call to discuss this and other issues related to the migration (including the updated data migration map: ISLG Data Migration Map - TOLOGIX - ISLG App Rebuild).

Would Wednesday at 8:15am Vancouver time work?

Thanks,

Morgan

Hi Morgan ,

I am not available on Wednesday and Friday. Can we schedule call on Thursday before our status call. 

8:15 PM IST would be fine on Thursday ?

Hi Harsh ,

Another issue to consider for our call tomorrow. If we can deploy the process above where Legal Analytics data is backed-up and then all the data is wiped from rebuild.islg before the migration, it will allow our content team to upload placeholder disputes and dispute documents to perform legal analytics on documents released since the first migration before we perform the second migration. This will give the content team more time to perform their review, and give a little more breathing room to perform the migration before launch in January.

We'll discuss more during the call.

Thanks,

Morgan

Hi Paul ,

Further to a call this morning concerning the migration, could you please provide Harsh and Shrinivas with spreadsheet that provides a list of all the Dispute UIN's and Case Names that we're performing Legal Analytics data capture on.

Thanks,

Morgan 

Hi Harsh and Shrinivas :

Attached is the list of Dispute UINs and case names. Please note that some of them are not currently on rebuild.islg.

Thanks,

Paul

Legal Analytics List (24-Sep-20).xlsx 1.26 MB • Download

Hi Harsh ,

Note that the disputes in Paul 's list above that are currently not on rebuild.islg are disputes that have been added since the migration in June.

As I've mentioned above, assuming we're able to apply the approach described above, we would manually add these documents and applicable dispute documents to rebuild.islg so that we could perform the necessary Legal Analytics data capture.

Please review and then we can discuss again whether this approach will be feasible.

Thanks,

Morgan

Hi Morgan ,

We discussed internally and yes we will go with the approach which you suggested. Following are the steps to we need to follow to migrate master data again.

Steps:-

This exercise will take approximately 2 weeks of time with 2 resources in November.

Hi Harsh ,

The steps above look good to me. Let's proceed with that approach.

Also, could you please confirm that with this approach we can proceed with uploading placeholder Disputes and Dispute Documents to rebuild.islg to perform Legal Analytics data capture for disputes added to the system since the initial migration in June. These Dispute and Dispute Document entries will be uploaded by Paul and Nafiseh with only required data (e.g., UIN and Case Name) and then will be used to populate the Legal Analytics forms. This data will then need to be backed-up under step 1 above, and then restored to system after the second migration is complete. 

This will ensure we can perform the legal analytics analysis before the migration, and eliminate the need to capture all the data between completing the migration and launch, which would be difficult to accomplish under the tight timelines.

However, I want confirm that this process works on your end, particularly with respect to matching Legal Analytics data IDs against associated disputes and dispute documents. Let us know and we'll proceed accordingly. 

Thanks,

Morgan

Morgan ​, my question is how you upload data for dispute document ? Because, Dispute document  required pdf file to upload. After that, you can able to enter required data. if you enter only dispute data and then you will enter the legal data for those disputes then it will be work.

Hi Harsh ,

You don't need to upload a PDF when you create a Dispute Document entries anymore.

Here are the Steps we'd follow:

Step 1: Create the Dispute:

image.png 68.2 KB • Download

Step 2: Create the Dispute Document:

image.png 72.1 KB • Download

image.png 81.5 KB • Download

image.png 87.7 KB • Download

Step 3: Add Legal Analytics data

image.png 78.1 KB • Download

Let us know if you see any issues with this process given the proposed approach for the migration above. If this works, we'll get started on uploading the relevant Disputes and Dispute Documents to rebuild.islg.

Thanks,

Morgan

Hi Morgan ,

We need to discuss this thing because we found one challenge as per screen shot if we wipe out all master data.

Suppose, you added  relevant Dispute Document data for Legal Analytics. The Relevant Dispute Document meta field data is fetching from Dispute Document Data.

If we  wipe all master data then Dispute Document master data will be removed and the linkage of Relevant Dispute Document in Legal Analytics create issue if the mapping id will be differ when we again migrate all master data.  This thing will happen with so many field which pull the data from mastes.

As per following example,

Legal Analytics have some meta fields which pulls the data from Pepole, Dispute Document etc.. You add the Legal Analytics Data with select relevant people or dispute document data.

 In our database the People and Dispute Document Ids are associated against Legal Analytics Meta Field.

If we wipe all master data then all associated mapping ids will be wiped out from datable. 

Hi Harsh ,

Understood. Note that the only data linked in Legal Analytics is Disputes and Dispute Documents data. People and other data are linked through Proceeding Details of the Dispute form, which will be integrated into the migration and will not need to be backed up with Legal Analytics.

For mapping IDs to restore the backed up Legal Analytics data, wouldn't it be possible to create a table similar to the following when we back-up the Legal Analytics data:

image.png 11.4 KB • Download

and then using the common UIN we can match up the old IDs with new IDs, update the Legal Analytics data, and then restore it to the migrated application?

I assume your going to use a similar process for the Dispute IDs, so we would expand this to include the Dispute Document IDs as well.

Thanks,

Morgan

Hi Morgan ​,

Can we take call on this thurshday prior to our status call to discuss this thing?

Would 8:15 PM IST fine for you?

Sure, Harsh .

I'll setup the meeting at that time.

Morgan

Hi Morgan ,

Prior to our call, Could you please make list of which meta field you will use in legal analytics data which pull from Dispute Document master(ex. Relevant Dispute Document meta Field).

Hi Harsh ,

I'm not sure it would be helpful to create is list of every meta field that pulls from the Dispute Document master list, because it occurs so frequently across the Legal Analytics form. Further to the video below, almost every field set within Legal Analytics eventually leads to a field labeled "Relevant Document(s)", which pulls entries from the customized Related Dispute Documents value list. Therefore, I think it would be easier to identify the relevant fields by isolating it to fields that have the following characteristics:

Field Label: Relevant Document(s)
Value List: Related Dispute Documents

Any field in Legal Analytics that fits these criteria are fields that are pulling dispute document master list entries.

Thanks,

Morgan

Relevant Document(s) fields within Legal Analytics (29-Sep-20).mp4 6.8 MB • Download

 

Hi Morgan ,

My question is that only Relevant Document(s) meta field you are using for Legal Analytics which pull from Dispute Document Master ?

Do you use any other meta field except Relevant Document(s) which are pulling data from other master (for example, People, Country, Organization etc..) Because we need to know all those meta field name in Legal Analytic where data pulling from other masters.

We will discuss more in tomorrow's call.

Hi Harsh ,

I'll add this tomorrow's meeting agenda; however, yes, the Relevant Document(s) fields are the only fields pulling data from the other master lists, and all these fields pull data from the Related Dispute Documents value list.

Paul , should probably confirm this, but to my knowledge, no other fields in Legal Analytics pull data from other master lists.

Thanks,

Morgan

Yes, the Relevant Document(s) fields are the only fields pulling data from the other master lists as far as I am aware.

Paul

Hi Morgan ,

We had discussed internally this task to remove all master, All miscellaneous list except Legal Analytics and again need to re-migrate all masters data and update all associated master id and miscellaneous id with Legal data.

This task is challenging task for us and we need approx. 20 to 25 days work with 2 resources. (Note: The testing is more required after this kind of migration).

Hi all,

Following-up on the discussions today, we've confirmed that the re-migration approach will be used to update all the relevant master list data, and that all Legal Analytics data will be captured in the application in advance of the migration. As a result, the following actions are needed:

Thanks,

Morgan