As shown in the video, certain Terms & Phrases entries are missing on app.islg. I am not sure whether this is a migration issue or something happened to certain entries, but I see orphaned entries that should have its own link back to the applicable instrument and provision or Subject Navigator heading (Catalogued in Subject Navigator).
We need to audit Terms & Phrases to ensure that there are no orphaned entries.
Can you approve and put it at the top of the backlog? We'll make sure to investigate by early next week.
Thanks, -Martin
Notified 4 people
Paul Moon
Hi
Martin
:
I put it as the first item on the backlog, thanks.
Paul
Notified 4 people
Harsh Parikh,Tech Lead
Hi
Paul
,
We have verified the data and found that during the migration time some term phrases doesn't have associated with Dispute Document and Excerpt but they have associated with Agreement or Instrument.
We checked and found that total there are 289 Terms Pharse data.
I have provided the sheet here for those data. You need to provide the last 2 column data.
What is the reason behind this? We had about 500 entries at the time of migration, and this means close to 60% of entries never got migrated. Should we look at other citators as well to see if this problem exists?
Based on your list, I've added column E "Article Provision" and column G (Para/Fn/Page) to make the content team's audit easier.
Nafiseh
: could you fill out columns E to H in the spreadsheet below and re-post it here when you're done? Please complete this by tomorrow.
Will do. I'll post the updated spreadsheet when I am done.
Thanks,
Nafiseh
Notified 4 people
Harsh Parikh,Tech Lead
Hi
Paul
,
Those entries were not exists on legacy application during migration time. Due to that reason entries are not available on app.islg.
Cc :
Martin
Nafiseh
Notified 4 people
Paul Moon
Hi
Harsh
:
I don't believe your explanation is correct. The entries that are currently missing did exist on the legacy site at the time of migration and still does exist on the legacy site.
For example, the entry below that appears in your spreadsheet.
Please find attached the updated spreadsheet. Columns E to H in the spreadsheet are filled out. Please note my comments in column I for the three documents highlighted in yellow.
Thanks for adding the missing data on app.islg. I spot-checked the data, and it looks good to me. As for the spreadsheet (with your comments) that
Harsh
sent, I made all the required updates so you don't need to do anything.
In the meantime, I wanted to report that while spot-checking the data, I noticed that several Terms and Phrases have duplicate entries. I have recorded two videos:
Martin L.
As shown in the video, certain Terms & Phrases entries are missing on app.islg. I am not sure whether this is a migration issue or something happened to certain entries, but I see orphaned entries that should have its own link back to the applicable instrument and provision or Subject Navigator heading (Catalogued in Subject Navigator).
We need to audit Terms & Phrases to ensure that there are no orphaned entries.
If possible, please add to this sprint's unplanned.
Thanks,
Paul
Since
Can you approve and put it at the top of the backlog? We'll make sure to investigate by early next week.
Thanks,
-Martin
I put it as the first item on the backlog, thanks.
Paul
We have verified the data and found that during the migration time some term phrases doesn't have associated with Dispute Document and Excerpt but they have associated with Agreement or Instrument.
We checked and found that total there are 289 Terms Pharse data.
I have provided the sheet here for those data. You need to provide the last 2 column data.
1) Dispute Document
2) Excerpt
What is the reason behind this? We had about 500 entries at the time of migration, and this means close to 60% of entries never got migrated. Should we look at other citators as well to see if this problem exists?
Based on your list, I've added column E "Article Provision" and column G (Para/Fn/Page) to make the content team's audit easier.
Thanks,
Paul
Will do. I'll post the updated spreadsheet when I am done.
Thanks,
Nafiseh
Those entries were not exists on legacy application during migration time. Due to that reason entries are not available on app.islg.
Cc :
I don't believe your explanation is correct. The entries that are currently missing did exist on the legacy site at the time of migration and still does exist on the legacy site.
For example, the entry below that appears in your spreadsheet.
The entry was in fact uploaded to the legacy back in 2015. The attached T&P Master List and the legacy site confirm it.
This is the T&P Master List that
Let me know if I misunderstood something.
Thanks,
Paul
Please find attached the updated spreadsheet. Columns E to H in the spreadsheet are filled out. Please note my comments in column I for the three documents highlighted in yellow.
Please let me know if you have any questions.
Thanks,
Nafiseh
Might be there was minor issue during migration data. We will update the data as per the Nafish sheet.
We will complete this before next sprint
Cc :
We added missing tp data on app.islg. Please check and confirm.
Only attached sheet's TP data haven't display associated dispute document due to reason which I mentioned in comment column.
Cc :
Thanks for adding the missing data on app.islg. I spot-checked the data, and it looks good to me. As for the spreadsheet (with your comments) that
In the meantime, I wanted to report that while spot-checking the data, I noticed that several Terms and Phrases have duplicate entries. I have recorded two videos:
Here are also some more examples:
Could you please look into it, and let us know if there is a way to identify these duplicates, and remove them?
Thanks,
Nafiseh
Do we need to capture this issue in a new DevOps item? If so, I'll create one and include it in Sprint 16.
--Martin
I am working on this item today. still 8 hours work is pending for this item as need to update stored procedure.
Please allocate 8 hour task for next sprint.
I have created DevOps bug https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1728 for Sprint 16.
-Martin
The above duplicate entries issue is resolved on both staging.islg and app.islg. Please check and confirm.
Cc :
I checked both staging.islg and app.islg. The entries look good. I'll mark this to-do as complete.
Thanks,
Nafiseh