TOLOGIX - ISLG App Rebuild

Problem HTML documents converted from XML documents

Assigned to
Martin Laporte, CTO at Tologix Martin L.
Notes
Further to the video below, on closer inspection of the HTML documents that have been converted from previously existing XML documents from the legacy application, it appears that these documents are missing the H# tags elements to ensure the documents produce TOCs and have other styling properties that are needed for the new application. Note these H# tags were specifically flagged when creating the XML coding manual for creating the XML to HTML converter: Re: XML Coding Manual.doc - TOLOGIX - PDF to HTML Conversion.

Jitesh Dhuravala, DevIT Jitesh and Piyush Rathod, DevIT Piyush , could you please explain what's happened here? I'm concerned that we don't have HTML documents that are fully compatible with the new application.

Thanks,

Morgan

Comments & Events

Morgan Maguire, CEO
Hi Harsh Parikh, Tech Lead at DevIT Harsh ,

The TOC for ICSID Convention (1968) looks fine, but the TOC for ICSID Convention Regulations and Rules (1984-unabridged) only starts at Article 25 and is missing all the chapters and sections:
Also, I see you've inserted the TOC directly into the documents, rather than just inserting the necessary tags so that the TOC is populated once it is integrated into the application. I would like the documents to be similar to the legacy app, where the TOC is generated based on the tags in the documents:

Is this in the requirements of the application?

Melissa Cowell, General Manager at Industrial Melissa and Naomi Joanis, UX Team Lead at Industrial Naomi , could you comment on whether we expected the TOC to be automatically generated within the document view for Treaties and Arbitration rules based on the HTML tags?

Thanks,

Morgan 
Naomi Joanis, UX Team Lead at Industrial
Hi Morgan Maguire, CEO Morgan

Yes this was in the criteria. TOC should be automatically generated based on the heading levels in the treaty/rule documents that create provisions. These should be used as the table of contents to navigate the documents in document view. (see card for reference: https://industrialagency.tpondemand.com/entity/14660-bittreaties-and-arbitration-rules-greater-provisions)

This was tested as well, though of course some documents never generated a TOC due to the HTML structure from the conversion. 
Morgan Maguire, CEO
OK. Thanks Naomi Joanis, UX Team Lead at Industrial Naomi .

Harsh Parikh, Tech Lead at DevIT Harsh , I'll add this to the agenda for discussion tomorrow.

Thanks,

Morgan 
Harsh Parikh, Tech Lead at DevIT
Hi Jitesh Dhuravala, DevIT Jitesh ,

Could you please look into this as we need to discuss today with Morgan.
Jitesh Dhuravala, DevIT
Hi Morgan Maguire, CEO Morgan ,

We have checked XML files for ICSID Convention Regulations and Rules (1984-unabridged) and there is missing attribute "tocdepth" that's why it was missing in TOC.

You can see in below image.


Second point, dynamic TOC generated and display direct into the application rather than into HTML point we will discuss on today call. 


Thanks,
Jitesh