Dataset Recommendation via Local and Global Density Metrics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data recommendation systems fail to adequately consider a data user's specific interests when recommending dataset subsets, often prioritizing globally popular data categories over those that are relatively more important to the user, leading to obscure recommendations.

Innovation Solution

A system that determines provider and user dataset densities for specific data values, calculates relative densities, and uses a combination of these metrics to evaluate recommendations, ensuring that data users acquire datasets that align better with their interests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a recommendation system uses global popularity (provider dataset density) to recommend datasets, then it can identify commonly useful data categories, but it fails to account for the user's specific interests and may recommend obscure or irrelevant data subsets

Engineering Contradiction:
Improverecommendation accuracyVSAvoiduser-specific relevance
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by computing user database density (local popularity) for each data value based on the user's specific database characteristics, rather than using a single global metric. This allows the recommendation system to adapt to local user needs while considering both global availability and local relevance, resolving the contradiction between global popularity and user-specific relevance

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent combines multiple density metrics (provider dataset density and user database density) into a composite recommendation score. This composite approach integrates both global and local perspectives, enabling the system to balance commonly useful data categories with user-specific interests, thereby improving recommendation accuracy while maintaining adaptability

Inventive Principle:
Principle #40Composite materials

2Reliability

If a recommendation system prioritizes globally popular data categories, then it ensures broad applicability, but it overlooks relatively more important data categories specific to the user's needs

Engineering Contradiction:
Improverecommendation consistencyVSAvoiduser interest alignment
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent changes the evaluation parameter from solely global density to a combination of global density and local density. By introducing user database density as an additional parameter and computing their relationship, the system maintains reliability through consistent global metrics while adapting to user-specific interests through local density variations

Inventive Principle:
Principle #35Parameter changes

3Productivity

If a system recommends dataset subsets based on density metrics, then it can identify relevant data categories, but it may still recommend subsets that do not align with the user's specific data interests

Engineering Contradiction:
Improverecommendation efficiencyVSAvoidrecommendation relevance
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent incorporates feedback by comparing provider dataset density with user database density. This feedback mechanism allows the system to evaluate whether globally popular data categories actually align with the user's specific database characteristics, thereby improving recommendation relevance while maintaining efficient density-based evaluation

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10817479B2Recommending data providers' datasets based on database value densities
Publication Date: 2020.10.27 SALESFORCE INC
  • US10817479B2 patent drawing
  • US10817479B2 patent drawing
  • US10817479B2 patent drawing

AI summary

Recommending data providers' datasets based on database value densities is described. A database system determines a provider dataset density for a value by identifying a frequency of the value in a dataset that is provided by a data provider. The database system determines a user database density for the value by identifying a frequency of the value in a database used by a data user. The database system determines a relative density based on a relationship between the provider dataset density and the user database density. The database system determines an evaluation metric for the value, based on a combination of the relative density and the user database density. The database system causes a recommendation to be outputted, based on a relationship of the evaluation metric relative to other evaluation metrics for other values, which recommends that the data user acquire at least a part of the dataset.