Hi Harsh ,

Can you resolve the issue above?

And can we get more details as to why this entry was missed?
As Irit asked, should we do an audit to ensure other entries have not been missed?

Thanks,
--Martin

Hi Harsh :

Please let Martin know how much of an audit project it would be before we determine whether we audit the whole SN Master Tree or not.

Thanks,

Paul

Hi Paul and Irit ,

This issue is resolved on app.islg. Please check and confirm.

Cc : Martin  

Hi Harsh ,

I see that the missing data has been added to the two fields.  The entry now appears in the SN Analysis for UN/0170/03.  I do not yet see the entry on the SN Live Site.  I will check again tomorrow.  Perhaps this is an indexing issue.  I will not mark this to do complete just yet as I want to make sure it's on the live site.

Martin , as for this particular issue being resolved - how should we proceed?  Do we mark this to-do as complete knowing there may be other SN entries with unexplained missing data?  Missing data means the entry is not appearing on the Live Site.
Do we look into seeing if there is a way to audit the SN Master Tree and search for blank fields?

Thank you,
Irit

Hi Irit , let's leave this particular item open. Harsh and I will come up with a plan tomorrow and we will circle back in this thread.
Thanks!

--

Hi Harsh ,

Let's discuss the audit process (including rough estimates for effort) during our daily scrum tomorrow.

Thanks,
--Martin

Just a quick update (Harsh will give more details by tomorrow): we believe that the discrepancies between Legacy and app.islg are found in documents that were in Draft version during the migration. Harsh will query the database and produce a list of documents that were in that state during the migration. He will then share that list in this thread.

We can then discuss how we want to proceed next with the list. The easiest way to audit would be to manually go through the list and compare Legacy vs. app.islg. I am not certain how much work would be required to automate that part of the process, but we can further discuss if the consensus is that a manual comparison would be too time consuming.

More to come by tomorrow.

Hi Martin :

Thanks for the update. When you say documents that were in draft version during the migration, do you mean the documents that were inactive on legacy admin? Legacy admin site didn't have "draft" like we do on app.islg. On legacy, each document was either active (appeared on subscriber site) or inactive (did not appear on subscriber site). Please clarify.

Thanks again,

Paul

Hi Paul ,

Harsh will provide more details tomorrow. 

Thanks,
--Martin

Hi Paul ,

The issue was created on 28th December 2020 after we migrated SN data from leagcy to app.islg. Due to one bug there was issues which we resolved but for some tagging entries it was not resolved.

We have audited following UIN's which your team need to check those UIN's SN tag data with leagcy and app.islg.

AF/0014/03
AF/0014/05
AF/0044/01
AF/0044/02
IC/0098/01
IC/0111/01
IC/0111/02
IC/0117/02
IC/0117/03
IC/0117/10
IC/0117/12
IC/0117/15
IC/0117/17
IC/0118/02
IC/0118/03
IC/0120/05
IC/0120/06
IC/0130/09
IC/0130/10
IC/0263/01
IC/0290/01
OT/0022/01
UN/0031/74
UN/0039/01
UN/0039/02
UN/0121/04


Please check above UIN's SN data on app.islg and compare to legacy data and let us know if you found any issue.

Hi Irit :

Could you compare the SN entries for the 26 UINs above between legacy and app.islg  and report back here?

Thank you,

Paul

Hi Paul ,

Yes.  I've added it to my audit to-do list.  I'll set a deadline date to get this complete.

Thanks,
Irit

Hi Irit :

Could you update us on your progress?

Thanks,

Paul

Hi Paul,

Progress is very slow. I'm finding mistakes in every UIN that I check.  I have only gone through six so far.  The due date I set for myself is for December 20th.

Hi Martin :

I know it is slightly different, but could this be addressed together with https://dev.azure.com/tologix/ISLGRebuild/_backlogs/backlog/ISLGRebuild%20Team/Backlog%20items/?workitem=1250 or is it going to complicate the task?

Please let me know.

Thanks,

Paul

Hi Paul ,

I would prefer keeping this item separate from the others, since we do not quite know how much effort will be required to address the issues (depending on how many are found).

What I suggest is that once we have a list of items to correct, we evaluate whether this could be addressed in the current sprint (via Unexpected/Critical issues), or if it should be added as a new item in the next sprint.

Thanks,
--Martin 

Ok, Martin .

Irit has gone through a few UINs that Harsh provided, and every UIN has an issue so far. She has a few left that will be done by December 20th.

Thanks,

Paul

Hi  Harsh , Martin and Paul  

I am almost done this audit.  Harsh , most of the UINs in your list had issues.  I did not keep track under which SN branch the issues were found. In the future, I'll keep track of this when doing a SN audit.

Thank you,
Irit

Hi Irit :

Could you update us on this item?

Thanks,

Paul

Hi Paul ,

The only one left in my audit is AF/0014/03.  The SN shows 191 results on legacy.  The SN shows 80 results on app.islg.

Irit

Hi Martin and Harsh :

It seems like most UINs have issues. Could you audit all the UINs below to make sure that corresponding entries have both the UIN and the paragraph/fn location?

AF/0014/03
AF/0014/05
AF/0044/01
AF/0044/02
IC/0098/01
IC/0111/01
IC/0111/02
IC/0117/02
IC/0117/03
IC/0117/10
IC/0117/12
IC/0117/15
IC/0117/17
IC/0118/02
IC/0118/03
IC/0120/05
IC/0120/06
IC/0130/09
IC/0130/10
IC/0263/01
IC/0290/01
OT/0022/01
UN/0031/74
UN/0039/01
UN/0039/02
UN/0121/04

Thanks,

Paul

Hi Paul ,

When I did the audit, I made sure to fill in any missing UINs and missing paragraph numbers.
As I mentioned above, the only UIN left for me to audit is AF/0014/03.  

Thanks,
Irit

Another Subject Navigator entry that was migrated from legacy to app.islg is missing entries in the fields for "Document UIN" and "Destination Codes" on app.islg.

The UIN is UN/0045/69.  This UIN was not included in Harsh's list in this post that was provided on 19-Nov-2021 (if you scroll up, the list is found in this thread).

I posted the issue here:

Subject Navigator missing entries in the fields for "Document UIN" and "Destination Codes" (UN/00... - TOLOGIX - ISLG App Rebuild for Tologix

 

Hi Paul ,

The last UIN left for me to audit (AF/0014/03) is complete. 

Thanks,
Irit