We are trying to figure out what is causing this inconsistency of separate opinion appearing or not appearing on the new admin site.
Thanks,
Paul
Notified 1 person
Morgan Maguire,CEO
Hi
Harsh
,
Further to
Paul
's description above, we can't figure out way these two documents were treated differently when the data was migrated. Both appear to have similar source data, but with UN/0151/30 the Separate Opinion fields were populated, and then with AF/0012/01 no data was populated in the Separate Opinion fields. Could you please explain the reason why data was populated in one document, but no the other?
Thanks,
Morgan
Notified 3 people
Harsh Parikh,Tech Lead
Hi
Morgan
,
We are not migrated Separate Opinion data in Dispute Documents as per our Migration sheet.
The above UIN data entered by
Nafiseh
on 22th October 2020. so you are able to see these. as we don't need to migrate those fields so we keep those field data as it is.
The
Notified 3 people
Morgan Maguire,CEO
Hi
Nafiseh
,
Is this true? Were you the one who added the data to the Separate Opinion fields UN/0151/30? If so, that might explain the discrepancy (i.e., the field was not populated by migration data, but by legal analytics review prior to the migration).
Thanks,
Morgan
Notified 4 people
Nafiseh Arghandehpour,Legal Content Manager
Hi
Morgan
,
Yes, I think so. I added data to the Separate Opinion field for a few documents after the first round of migration, and it could be one of them.
Thanks,
Nafiseh
Notified 4 people
Morgan Maguire,CEO
Ok. Thanks for confirming
Nafiseh
.
Paul
, It sounds like this resolves the discrepancy. The question is what should we do to resolve this across the document collection. Should we attempt to apply this across all Separate Opinions before we launch?
Perhaps this is a project
Katrina
could assist with.
Morgan
Notified 4 people
Paul Moon
Ok, this explains the discrepancy.
Yes, there is already an internal content to-do about this (Separate Opinions - TOLOGIX - ISLG App Rebuild), so I'll organize this task with
Nafiseh
and
Katrina
and update the rebuild admin site as necessary.
As discussed, UN/0151/30 on the new admin site shows the separate opinion related to it (UN/0151/31)
The legacy admin site for UN/0151/30 also lists UN/0151/31 as a related decision shown below.
https://www.investorstatelawguide.com/CoreComponents/AddDocumentStep3Type2?docId=12425
However, AF/0012/01 doesn't show its related separate opinion listed below on the new admin site
The legacy admin site confirms that AF/0012/01 is not entered any differently from UN/0151/30, and AF/0012/02 is entered as a related decision.
https://www.investorstatelawguide.com/CoreComponents/AddDocumentStep3Type2?docId=151
We are trying to figure out what is causing this inconsistency of separate opinion appearing or not appearing on the new admin site.
Thanks,
Paul
Further to
Thanks,
Morgan
We are not migrated Separate Opinion data in Dispute Documents as per our Migration sheet.
https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0
The above UIN data entered by
The
Is this true? Were you the one who added the data to the Separate Opinion fields UN/0151/30? If so, that might explain the discrepancy (i.e., the field was not populated by migration data, but by legal analytics review prior to the migration).
Thanks,
Morgan
Yes, I think so. I added data to the Separate Opinion field for a few documents after the first round of migration, and it could be one of them.
Thanks,
Nafiseh
Perhaps this is a project
Morgan
Yes, there is already an internal content to-do about this (Separate Opinions - TOLOGIX - ISLG App Rebuild), so I'll organize this task with
Thanks,
Paul
I'll complete this to-do then.
Morgan