TOLOGIX - ISLG App Rebuild

Certain Treaties Inactive on the Rebuild Admin site

Assigned to
Harsh Parikh, Tech Lead at DevIT Harsh P.
Notes
Hi Morgan Maguire, CEO Morgan ,

Attached is the list of inactive Treaties on the rebuild admin site (I exported them from the rebuild admin site).

The BITs that are highlighted green are the ones related to this to-do: XML Files Not available - TOLOGIX - ISLG App Rebuild (which still should not be inactive, but as Harsh has not confirmed whether they applied your instructions, I separated them).
The BITs that are highlighted red are non-English BITs with the status "Published" which should not be kept inactive as keeping them inactive prevents these BITs from appearing under "Treaties and Rules" on the rebuild live site.

Please let me know if this is something we want to fix internally or we want to ask DevIt to take care of.

Thanks,

Nafiseh

Comments & Events

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

Further to the to-do above, we'll resolve the issues with the documents highlighted in green in the other to-do: XML Files Not available - TOLOGIX - ISLG App Rebuild. However, for the documents highlighted in red, why have these documents been uploaded as "Inactive", but are in published status? Was there something in the migration instructions that caused these documents to be marked as inactive?

Thanks,

Morgan
Harsh Parikh, Tech Lead at DevIT
Hi Morgan Maguire, CEO Morgan and  Irit Weinfeld Irit and Nafiseh Arghandehpour, Legal Content Manager at ISLG Nafiseh  

Those UIN are InActive in legacy application. Hence we set Document state is published but Status we set Inactive.

Please provide the UIN List which you need active status so we can update on rebuild.islg.
Nafiseh Arghandehpour, Legal Content Manager at ISLG
Hi Harsh Parikh, Tech Lead at DevIT Harsh ,

Please note the difference between the status of documents on the legacy admin site and the rebuild admin site. In the new application, all the BITs and Treaties should be active so that all the versions of the BITs (whether primary or non-primary) appear under "Treaties and Rules" on the Rebuild live site.

Here is the example of a BIT that appears correctly on the new application in terms of the status:
In "Egypt-Germany BIT", as you see in the screen captures below, the status for non-primary versions on the legacy admin site is inactive (which was our way to prevent non-primary BITs from appearing on the Article Citator on the legacy live site)

The status of all the versions of the BIT are active on the rebuild admin site as they should be:

The reason why all the versions of Egypt-Germany BIT appear under "Treaties and Rules" on the Rebuild live site is that the status of all the versions of this BIT is active.

And only the primary version appears under Article Citator on the rebuild live site:


This is how we expect to see all the BITs and Treaties on the new application.
The BITs highlighted red in the spreadsheet attached to this to-do are the ones whose state is "published" but their status is inactive, and should be changed to active.

Thanks,

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

To follow-up on Nafiseh Arghandehpour, Legal Content Manager at ISLG Nafiseh 's comment above, the status of documents within the new application should have been determined by what was indicated in the UIN Master List as outlined in the ISLG Meta Field Map: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=0

Therefore, with BIT/0737 above, the UIN Master List indicated the following:


which means that the document should have been uploaded to the application as follows:
  • Set the status to "Active"
  • Set the document state to "Published"
Thanks,

Morgan
Harsh Parikh, Tech Lead at DevIT
Hi Morgan Maguire, CEO Morgan and Nafiseh Arghandehpour, Legal Content Manager at ISLG Nafiseh ,

We have updated the Active status as per UIN master sheet. But the status will be display blank for those UIN which we treated as Placeholder document. it mean in new application we are considering those UIN under skip upload  functionality.
Morgan Maguire, CEO
Ok. That's fine Harsh Parikh, Tech Lead at DevIT Harsh .

Nafiseh Arghandehpour, Legal Content Manager at ISLG Nafiseh , please confirm that everything is appearing as expected on the Subscriber site.

Thanks,

Morgan
Nafiseh Arghandehpour, Legal Content Manager at ISLG
Nafiseh Arghandehpour completed this to-do.
Morgan Maguire, CEO
Ok. Thanks Nafiseh Arghandehpour, Legal Content Manager at ISLG Nafiseh .

Morgan