✔ Adding Provision Codes to HTML
Completed by Paul M.
- Assigned to
-
Harsh P.
- Notes
-
app.islg Admin Site:
FTA/0041, Master Lists, Treaties, Document Text, Edit Provisions List
The following headings need provision codes (tags) in the HTML so that they appear in the Provision list.
I don't know how to add Provision tags in the HTML.
Capítulo 1: Disposiciones Iniciales (PDF, page 2)
Capítulo 2: Definiciones Generales (PDF, page 3)
Capítulo 3: Comercio de Mercancías (PDF, page 5)
Capítulo 5: Facilitación del Comercio (PDF, page 22)
Capítulo 6: Medidas Sanitarias y Fitosanitarias (PDF, page 29)
Capítulo 7: Obstáculos Técnicos al Comercio (PDF, page 34)
Capítulo 9: Inversión (PDF, page 44)
Capítulo 10: Comercio Transfronterizo de Servicios (PDF, page 68)
Capítulo 11: Entrada Temporal de Personas de Negocios (PDF, page 78)
Capítulo 12: Comercio Electrónico (PDF, page 86)
Capítulo 13: Contratación Pública (PDF, page 89)
Capítulo 14: Transparencia (PDF, page 117)
Capítulo 15: Administración (PDF, page 119)
Capítulo 16: Solución de Controversias (PDF, page 121)
Capítulo 17: Laboral (PDF, page 130)
Capítulo 18: Ambiental (PDF, page 133)
Capítulo 19: Cooperación (PDF, page 136)
Capítulo 20: Disposiciones generales (PDF, page 140)
Capítulo 21: Excepciones (PDF, page 142)
Capítulo 22: Disposiciones Finales (PDF, page 145)
Anexo 9(C): Expropiación
cc
Paul
Nafiseh
Thank you,
Irit
Were the provisions above captured in the provision list within the legacy app? If so, could you provide more detail to compare to how the data was migrated to the new application.
Thanks,
Morgan
These provisions listed above were recently added to the provision list in the legacy app.
FTA/0041 was part of the migration. Along with provisions/ provision descriptions. However, a few Chapters/Sections were missing in the Provision list on the legacy admin site and had to be added. They were added just a few days ago. I'd like to add them to app.islg but I don't know how to do that.
Ok. Thanks. As we discussed today, could you please upload a test document with a new version of the HTML that has been converted from the update XML from the legacy application. If this resolves the issue, we'll get DevIT to replace the HTML and provision list for FTA/0041. If not, we'll get DevIT manually update the HTML and provision list.
Thanks,
Morgan
Thanks,
Irit
Thanks,
Morgan
XML for updated FTA/0041. This version was recently updated on the legacy Admin Site. It includes provision codes (tags) in the XML for the Chapter headings listed above.
PDF for FTA/0041
Thanks,
Morgan
BIT/1196 PDF and HTML will also require updating on app.islg. Some provisions migrated already.
The following text highlighted yellow will need to be added to the PDF and the HTML.
The following Articles need provision codes (tags) in the HTML so that they appear in the Provision list:
Article 1
Article 1(1)
Here is a copy of the XML:
Here is a copy of the HTML:
Thank you,
Irit
Morgan
Further to the discussion above and my video below, we are having difficulty generating the appropriate Provision List for the following HTML when it is uploaded to the staging.islg:
This HTML was generated by converting the XML into the an HTML document with the XML to HTML conversion tool: http://dev.convertortool.com/Home/XmlToHTML
Could you please explain why the appropriate Provision List is not getting generating after uploading the HTML: http://staging.investorstatelawguide.com/Admin/ContentTypeData/TreatiesList
Note that the example in the video was uploaded under FTA/9999 - Chile-Colombia FTA test in the Treaties master list of staging.islg.
Thanks,
Morgan
Did we ever look into the issue above?
Thanks,
Morgan
Following up on call from last week, could you please confirm whether we can manually migrate the provision list for a document from the legacy application to the new application for newly added Treaties and Arbitration Rules?
Thanks,
Morgan
Did you want a list of all instruments (arbitration rules and treaties, etc.) that we have XML'd on the legacy site with provision lists?
Based on
Thanks,
Paul
Let's have a chat tomorrow to discuss, but yes, this would only be those post-migration instruments that currently do not have provision list and will be needed to complete your pre-launch anaylsis.
Thanks,
Morgan
Sure, let's chat tomorrow.
Based on what
Thanks,
Paul
Attached is the list of instruments where we need to transfer existing provision descriptions from the legacy site to app.islg.
Please note the first 5 BITs on the list have been migrated as placeholders on 3 December 2020, but they have been XML'd post-migration (and they have provision descriptions on the legacy site now), so they currently exist on app.islg as placeholders.
BIT/1357 was uploaded directly to app.islg as a test case, but we have an issue where provisions descriptions have not been properly extracted.
All instruments have been converted from XML to HTML. They are saved in the converter.
Thanks,
Paul
Thanks,
Morgan
I discussed this issue with
Thanks,
Morgan
That's great to hear!
Thank you,
Irit
The instruments I've included in the spreadsheet are needed for analysis transfer. New instruments to be added could wait until post-launch, but could we at least get those 8 instruments' provision descriptions migrated asap?
Paul
Based on our discussion, I'm going to move this to-do to post-launch.
Thanks,
Morgan