Workbook Composer Metadata Service Decoupling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application development frameworks face challenges in allowing end users to provide runtime customizations of documents developed using desktop integration frameworks, particularly in managing metadata independently of local caches and workbook definition files, which limits flexibility and user interaction.

Innovation Solution

The implementation of a method that receives metadata associated with integrated documents, generates a user interface for customization, and stores customized metadata, enabling users to add, remove, or modify components and properties of published documents, with metadata management handled by a metadata service for independent updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If metadata is stored in local caches and workbook definition files, then document rendering is efficient, but user customization flexibility is limited

Engineering Contradiction:
Improveuser customization flexibilityVSAvoidmetadata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments metadata management into two independent parts: (1) local caches and workbook definition files for efficient document rendering, and (2) a separate metadata service for centralized customization management. This segmentation allows users to customize metadata through the service without affecting local rendering performance, resolving the contradiction between customization flexibility and system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a metadata service as an intermediary between users and local metadata storage. This service acts as a mediator that receives customization requests, processes metadata updates, and synchronizes changes to local caches and workbook definition files. The intermediary approach enables user customization while maintaining efficient local rendering, as the service handles the complexity of metadata management centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If metadata management is centralized in a metadata service, then user customization is enabled, but integration with local caches requires additional synchronization

Engineering Contradiction:
Improveuser customization capabilityVSAvoidmetadata synchronization time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the metadata service pre-process and validate customization requests before synchronizing to local caches. The service prepares metadata updates in advance, ensuring they are ready for efficient synchronization. This preliminary preparation reduces the actual synchronization time when changes need to be applied to local workbook definition files and caches.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the metadata service monitors changes in local caches and workbook definition files, automatically triggering synchronization when updates occur. This feedback loop ensures that centralized metadata management stays in sync with local changes without requiring continuous manual intervention, reducing the time loss associated with metadata synchronization by making it event-driven rather than continuous.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9916157B2Workbook composer for application development framework
Publication Date: 2018.03.13 ORACLE INT CORP
  • US9916157B2 patent drawing
  • US9916157B2 patent drawing
  • US9916157B2 patent drawing

AI summary

In various embodiments, methods, systems, and non-transitory computer-readable media are disclosed that allow users to specify runtime customizations of documents developed using a desktop integration framework. Workbook metadata is a set of information that describes how a given workbook is integrated with a particular web application. When a workbook is being published, metadata may be written into a local cache in the published workbook as well as a workbook definition file. Metadata management may be handed by a metadata service allowing updates and customization of published workbooks independently of a local cache in the published workbook and the workbook definition file. A workbook composer enables users to customize the metadata and store the customizations using the metadata manager.