TD-4394: Publishing catalogues needs to update referencing catalogues

[sarathlal-sarangadharan]

JIRA link

https://hee-tis.atlassian.net/browse/TD-4394

Description

Publishing catalogues needs to update referencing catalogues

Screenshots

Scenarios checked:

1. Created 2 Catalogues Ext1 and Ext2
   

2. Created a new folder under Ext2
   

3. Added external reference of 10-Level1 (Ext1) to Ext2
   

4. After publish created new folder 11-Level2 under 10-Level1
   

5. Renamed child folder 11-Level2 to Level2Rename which reflected under Ext1 too.
   

6. Added again new folder under 10-Level1 (Ext2) which reflects under Ext1 too.
   

7. Moved up folders which also reflected in Ext1
   
   

8. Contributed a new Resource to Ext2 > 10- Level1 which reflected in Ext1 > 100 -Level1 > 10 -Level1
   

---

Developer checks

(Leave tasks unticked if they haven't been appropriate for your ticket.)

I have:

• Run the formatter and made sure there are no IDE errors
• Written appropriate unit tests for the changes, including:
  • accessibility tests for new views
  • tests for new controller methods
  • tests for new or modified API endpoints
• Manually tested my work with and without JavaScript
• Tested any Views or partials created or changed with Wave Chrome plugin and addressed any valid accessibility issues
• Updated/added documentation in Confluence and/or GitHub Readme. List of documentation links added/changed:
  • doc_1_here
• Updated my Jira ticket with information about other parts of the system that were touched as part of the MR and have to be sanity tested to ensure nothing is broken
• Scanned over my pull request in GitHub and addressed any warnings from the GitHub Build and Test checks.

[DRJTechnology]

After further invistigation and conversations the following scenario is not handled by the change.

If a section of content is referenced from one catalogue to another, the referenced content is correctly showing in the target catalogue in both the AdminUI and the WebUI.
After publishing, if a resource in the source catalogue in moved to a different position in the folder structure, the target catalogue (after publish) shows the resource correctly in the AdminUI but the WebUI doesn’t show the resource (in either it’s original position or it’s new position).

Investigation of the data reveals that the ResourceReference records are not updated correctly. New ResourceReference records should be created for the resource’s new position in the structure with an OriginalResourceReferenceId set to the initial OriginalResourceReferenceId. The original ResourceReference record should be marked aas deleted.

Note: In these scenarios ResourceReference records are created by the stored procedures HierarchyEditMoveResource & HierarchyEditMoveNode

[DRJTechnology]

Extra scenario handled by work other ticket