Hi Harsh ,

Further to the description above, it appears we have another issue with an HTML document similar to what occurred here: IC/0416/01 - Issues on the Live Site - TOLOGIX - ISLG App Rebuild. Is there something happening within PDF to HTML conversion process that is causing this problems?

I've added Jitesh and Akash to this thread in case they can provide more insight.

Thanks,

Morgan

Hi Morgan and Nafiseh ,

There so many times we changed the html and tagging particular this document hence there is same problem occurs that Html Co-ordinates is changed after the updated the html. (HTML reference issue UN-0101-14 - TOLOGIX - ISLG App Rebuild)

I recommended that first will check this UIN's document IC/0416/01 - Issues on the Live Site - TOLOGIX - ISLG App Rebuild. after retag of AC tools. Once it will be done successfully with all tags then will do same thing for this document.

Nafiseh , Please check IC/0416/01 - Issues on the Live Site - TOLOGIX - ISLG App Rebuild this document tags once you done the tagging and published and let us know.

Hi Harsh ,

Yes, I think that makes sense if we check whether creating tags after removing them in IC/0416/01 HTML will resolve the issues before we try it for UN/0101/14 as the issues with UN/0101/14 and IC/0416/01 are the same. I will get back to you after I create tags for IC/0416/01, and check it on the live site.

Thanks,

Nafiseh

Ok. Sounds good, Harsh and Nafiseh . However, I'm wondering if there is anything further we could be doing within the HTML review process to identify problems with the HTML before they are uploaded to the application. That way we're not trouble shooting these issues and eating up valuable development resources.

Harsh is there a common problem with IC/0416/01 and UN/0101/14 that can be identified so that Jitesh and Akash can ensure the issue is integrated into the technical HTML review process?

Thanks,

Morgan

Hi Morgan ,

I assume this issue is occurred due to change the html after analyzing has started. Due to replace the html the co-ordinates of html has changed and some tagged already saved before replace the html. so the html co-ordinates are not matching with html file's data-key and hence highlight the portion is not occurred on proper place.

Let's complete the re-tagging process for UIN : IC/0416/01 by Nafiseh and check on subscriber side then will do same for this UIN also.

To avoid this issue in future I told that please check html file before start analyze/tagging process. 

Right. Understood, Harsh . However, what is the issue that needs to be checked in the HTML before analysis/tagging? My point is that this check should be done by Akash and the technical review team during the technical HTML review process, not by the content team.

Thanks,

Morgan

Hi Morgan ,

The issue for UIN IC/0416/01 is resolved. so will do same process for this UIN also.

Actually, The issue is mismatch the tagged co-ordinate which saves in database and html file data-key after it changed it. The PDF & HTML team can't able to verify this thing as the co-ordinates are mismatched with databases saved co-ordinates.

For Example,  When Content team saved any tag then will save the the start and end co-ordinate in database by using html data key. so in this issue after saved some tagging then html file was replaced and that time the data-key will be changed due to change the html file. so when application going to load tag  that time it goes to match the html coordinate with database co-ordinate and it it will be mismatch then it will be not load or not loaded at proper place.
 
To avoid this issue again, We need to verify the html file before start the tagging process because after doing some tagging and then change the html then data-key will be generated again and then it was mismatched with saved data-key in database.

Hence, let us know your content team to check html file first before start tagging  if there will be an issue regarding content then first do change the html from PDF to HTML team and then start tagging on this.

Hi Nafiseh ,

We will remove AC, JC & PC tool's tagging data for this document and you will re-tag again.

Please confirm so we will proceed. 

Hi Harsh ,

I'll let Nafiseh confirm whether to proceed with deleting the existing tagging data. 

However, in response to your comment above, what exactly needs to be checked in the HTML file? Could you please outline some requirements on what exactly needs to be checked and we will integrate this into the review process. As I've mentioned above, if it's anything technical, this check should be done technical review team, not the content team. Please outline the specific requirements, and we'll decide next steps. Perhaps use screenshots from a sample HTML to illustrate the problem.

Thanks,

Morgan 

Hi Harsh ,

Please go ahead and remove the tagging data for UN/0101/14 so I could create the tags again to resolve the outstanding issues.

Thanks,

Nafiseh

Hi Nafiseh ,

We have removed AC, JC & PC tags entries for this UIN  and update the status for Ready for Analysis Status on app.islg so you can re-tag.

Hi Harsh ,

Thanks for letting me know. I'll create tags again and confirm if the outstanding issues are resolved. 

Nafiseh

Hi Nafiseh :

Could you confirm whether the issues still exist or not?

Thanks,

Paul

Hi Paul ,

The issues have been resolved. I'll mark this as complete. 

Thanks,

Nafiseh