Annotation Structure Selection via Configuration Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in organizing and selecting appropriate annotation structures for diverse combinations of data types and user roles, leading to inefficiencies in capturing and managing tacit knowledge across heterogeneous data sources.

Innovation Solution

A method and system that retrieve annotation structures from a configuration file based on identifying parameters, allowing for the generation of appropriate forms for entering annotation data, and an annotation server that associates annotation structures with data objects and user roles, enabling effective annotation management across different data types and sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different annotation structures are created for different data types and user roles, then the system can capture diverse tacit knowledge effectively, but the complexity of organizing and selecting the proper annotation structure increases significantly

Engineering Contradiction:
Improveannotation structure diversityVSAvoidorganization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The annotation structure is segmented into multiple independent components: data type definitions, user role definitions, and annotation structure definitions. Each component can be independently configured and selected through the configuration file, allowing the system to handle diverse annotation requirements without creating a monolithic complex structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A configuration file serves as an intermediary layer between the diverse annotation requirements and the system implementation. This intermediary stores predefined mappings between data types, user roles, and annotation structures, automatically resolving the complexity of selecting appropriate annotation structures without requiring manual organization efforts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a comprehensive annotation system supports heterogeneous data sources and multiple user roles, then the system becomes more versatile, but the difficulty of detecting and measuring the correct annotation structure increases

Engineering Contradiction:
Improvedata source compatibilityVSAvoidannotation structure selection difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system performs preliminary action by pre-defining all annotation structure mappings in the configuration file before runtime. When a user requests annotation for specific data, the system simply queries the pre-configured mappings rather than performing complex real-time analysis, making detection and selection straightforward.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses parameter changes to identify annotation structures by matching data type parameters and user role parameters against predefined configurations. This parameter-based matching approach simplifies the detection process compared to analyzing complex structural characteristics.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If the system retrieves annotation structures dynamically from configuration files, then the system becomes more flexible in adapting to different data types, but the processing time increases due to file retrieval operations

Engineering Contradiction:
Improveannotation structure flexibilityVSAvoidretrieval time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The configuration file containing all annotation structure mappings is created and prepared in advance. This preliminary setup allows the system to perform simple query operations during runtime rather than performing complex analysis, significantly reducing retrieval time while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses a configuration file as a copy of the annotation structure definitions rather than storing the actual annotation structures in multiple locations. This copying approach maintains data consistency while enabling fast retrieval through simple file queries.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7900133B2Annotation structure type determination
Publication Date: 2011.03.01 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7900133B2 patent drawing
  • US7900133B2 patent drawing
  • US7900133B2 patent drawing

AI summary

Methods, systems, and articles of manufacture for organizing and selecting structures used to generate forms for capturing information as annotations made for a variety of different type data objects are provided. Some embodiments allow annotation structures to be associated with specific pairings of data object types and user roles via entries in a configuration file. When a user selects a set of one or more data objects for annotation, the configuration file may be accessed to determine a proper annotation structure for use in generating an annotation form based on the selected data objects and a role of the user.