Shadow Node for Portal Page Content Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web content management systems lack a means to coordinate the updating of portal page design/layout with its associated content, especially when syndicating changes to different subscribers, such as renaming a portal page or correcting typographical mistakes on published pages.
Innovation Solution
A method involving the creation of a shadow node in the web content management system to associate with portal pages, allowing the coordination of portal page content and design by linking web content with portal content stored in the portal database, enabling synchronized updates and versioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the portal page design and content management are separated, then web content authors can create content without understanding website building, but there is no means for coordinating updates between portal page design/layout and associated content
Solution Approach 1:
The patent introduces a shadow node as an intermediary data structure that bridges the portal page design system and the web content management system. This shadow node stores portal page configuration information (layout, design, metadata) and automatically synchronizes it to the content management system, enabling coordination between separated design and content management without requiring authors to understand website building
Solution Approach 2:
The patent creates a shadow node that copies and stores portal page configuration information from the portal database. This copy contains all necessary metadata and layout information that is then automatically propagated to the content management system, ensuring that design changes are replicated alongside content changes
2Adaptability or versatility
If portal page name is changed in the portal database, then the portal page can be renamed, but the associated content on the portal page cannot be automatically renamed
Solution Approach 1:
The patent implements a feedback mechanism where the shadow node continuously monitors changes in the portal database. When a portal page name or configuration changes, the shadow node detects this change and automatically triggers an update to the content management system, ensuring that associated content is renamed or updated in sync without manual intervention
Solution Approach 2:
The shadow node is pre-configured with templates and associations between portal pages and their content. When a portal page name changes, the preliminary setup allows the system to automatically identify and update all associated content items that need to be renamed, performing the coordination action before the user even requests it
3Ease of manufacture
If a portal page is published with a typographical mistake, then the page can be published, but the mistake cannot be automatically corrected on the published portal page
Solution Approach 1:
The shadow node implements continuous feedback by monitoring both the portal database and content management system for discrepancies. When a typographical mistake is detected in published content, the system compares it against the authoritative source in the shadow node and automatically corrects the error on the published portal page, maintaining content accuracy without preventing the publishing process
Data Source
AI summary
A method, system and computer program product for coordinating the management of portal pages and its associated web content. A node is created in the portal database representing a draft of a portal page, where the node refers to a data structure that holds structured information pertaining to the portal content (e.g., portlet instances, layout, design). A shadow node associated with the portal page is created in the web content management system, where the web content of the portal page is associated with the shadow node. The shadow node refers to a data structure that stores information used to identify the portal page stored in the portal database. The portal page, after completing various tasks in the workflow process, is rendered by linking the web content of the portal page associated with its shadow node with the portal content of the portal page stored in the portal database.