Global Entity Management in Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software applications face inefficiencies in data input and management, particularly when dealing with entities that already exist within global data collections, as users must manually re-enter data and lack tools for editing or controlling entity records across multiple applications, with textual representations being cumbersome and not visually engaging.

Innovation Solution

A system that allows users to search and retrieve entity records from a global collection, copy data into a non-global collection, and display entities in a visually helpful manner, such as a pictorial graphic format, enabling users to efficiently manage and edit entity data across applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If users manually enter entity data into software applications, then data can be stored and accessed, but time is wasted and redundant data entry occurs

Engineering Contradiction:
Improvedata entry efficiencyVSAvoidtime for manual data entry
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically searching for and retrieving entity data from external sources (social media, business databases, consumer databases) before the user needs to enter it. This advance preparation eliminates the need for manual data entry by having the data ready and available when the user initiates a search or data retrieval request.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of entity data from external sources and stores them in the application's database. Instead of requiring users to re-enter data, the system copies relevant information from social media networks, business databases, and consumer databases, making it immediately available for use while the original data remains in its source location.

Inventive Principle:
Principle #26Copying

2Ease of operation

If users manually enter entity data, then data can be stored, but the process is tedious and inefficient

Engineering Contradiction:
Improveease of data inputVSAvoidtime for data input
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs self-service by automatically searching for, retrieving, and populating entity data without requiring manual user input. When a user searches for an entity, the system independently queries external databases, retrieves relevant information, and populates the data fields automatically, eliminating the tedious manual entry process while maintaining ease of operation.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If entity data is stored in global collections, then data sharing is enabled, but users lack control to edit or manage records across applications

Engineering Contradiction:
Improvedata sharing capabilityVSAvoiduser control over entity records
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system segments entity data into two distinct layers: a global collection for data sharing and a user-controlled local collection for management. The global collection enables data sharing across applications and users, while the user's local collection provides control over editing, appending, and deleting records. This segmentation allows both data sharing and user control to coexist without conflict.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer (the user's local collection) between the global data sources and the user's direct control mechanisms. This intermediary allows users to manage and control entity records locally while still maintaining connections to global data sources, enabling both sharing and control functions to operate effectively.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If entity data is displayed in textual format, then information can be conveyed, but users may miss data fields and spend more time absorbing information

Engineering Contradiction:
Improvecompleteness of data presentationVSAvoidtime to absorb displayed data
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system transitions from one-dimensional textual data presentation to multi-dimensional visual presentation by incorporating graphical elements, icons, and spatial organization. This dimensional change allows users to perceive data relationships and field information more quickly and comprehensively, reducing the time needed to absorb information while maintaining completeness of data presentation.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

5Adaptability or versatility

If users need to edit and control entity records, then data management flexibility is improved, but the system complexity increases

Engineering Contradiction:
Improvedata management flexibilityVSAvoidsystem complexity for data control
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments data management functions into distinct operational layers: global data storage, user-local data control, and automated retrieval processes. This segmentation allows the system to provide comprehensive data management flexibility (editing, appending, deleting records) while keeping the complexity localized and managed through clear separation of concerns, rather than requiring complex integrated systems.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10019519B2Methods and systems for utilizing global entities in software applications
Publication Date: 2018.07.10 SEAY GORDON E
  • US10019519B2 patent drawing
  • US10019519B2 patent drawing
  • US10019519B2 patent drawing

AI summary

Disclosed are methods and systems to utilize entities from global collections in software applications. An example method comprises providing an application to receive a search request for entities within a global collection, displaying retrieved records, receiving user input including a selected entity, and copying data from a selected entity into a non-global collection of data. Another method comprises displaying a pictorial graphic depicting a business card, and synchronizing the graphical elements with a global entity record. Examples of systems generally comprise a data storage, a server, a first application configured to receive first user input and insert user input into a global collection of entities, a second application configured to display data associated with at least one entity record from a global collection of entity records, receive second user input, and copy data associated with a selected global entity record to a non-global collection of entities.