Matching objects using match rules and lookup key

US10235476B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10235476-B2
Application numberUS-201514723866-A
CountryUS
Kind codeB2
Filing dateMay 28, 2015
Priority dateMay 28, 2015
Publication dateMar 19, 2019
Grant dateMar 19, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Some embodiments of the present invention include a method for identifying match candidates in a database object and may include generating, by a database system, a match key associated with a lookup field of a database object. The method may further include activating, by the database system, a matching rule associated with the match key, and receiving, by the database system, a request to search for duplicate candidates in the database object. The request may include an input entity. The duplicate candidates in the database object may be identified by using the input entity and the matching rule.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method comprising: generating, by a database system, a match key associated with a lookup field of a database object and associated with another field of the database object; activating, by the database system, a matching rule associated with the match key; receiving, by the database system, a request to search for candidates in the database object that are duplicates, the request including a probe entity; and identifying, by the database system, the duplicate candidates in the database object by: creating a plurality of candidate keys by applying the match key to a corresponding plurality of candidates in the database object, and creating a probe key by applying the match key to the probe entity, determining whether the probe key matches any of the plurality of candidate keys, and determining, when the probe key matches any of the plurality of candidate keys, whether the probe entity matches any of the plurality of candidates corresponding to the matched candidate keys by applying the matching rule to the probe entity and to the candidates corresponding to the matched candidate keys. 2. The method of claim 1 , wherein the duplicate candidates in the database object are identified based on a lookup value associated with each of the duplicate candidates. 3. The method of claim 2 , wherein the duplicate candidates in the database object are identified based on a lookup key associated with each lookup value. 4. The method of claim 3 , wherein the duplicate candidates in the database object are identified based on a lookup key of each of the duplicate candidates and based on a field value of the probe entity. 5. The method of claim 4 , wherein the field value of the probe entity corresponds to the lookup field. 6. The method of claim 5 , wherein the other field of the database object comprises a non-lookup field of the database object. 7. The method of claim 6 , wherein the duplicate candidates in the database object are identified based the lookup field and the non-lookup field. 8. An apparatus for identifying duplicate candidates in a database object, the apparatus comprising: a processor; and one or more stored sequences of instructions which, when executed by the processor, cause the processor to: generate a match key associated with a lookup field of a database object and associated with another field of the database object; activate a matching rule associated with the match key; receive a request to search for candidates in the database object that are duplicates, the request including a probe entity; and identify the duplicate candidates in the database object by: creating a plurality of candidate keys by applying the match key to a corresponding plurality of candidates in the database object, and creating a probe key by applying the match key to the probe entity, determining whether the probe key matches any of the plurality of candidate keys, and determining, when the probe key matches any of the plurality of candidate keys, whether the probe entity matches any of the plurality of candidates corresponding to the matched candidate keys by applying the matching rule to the probe entity and to the candidates corresponding to the matched candidate keys. 9. The apparatus of claim 8 , wherein the duplicate candidates in the database object are identified based on a lookup value associated with each of the duplicate candidates. 10. The apparatus of claim 9 , wherein the duplicate candidates in the database object are identified based on a lookup key associated with each lookup value. 11. The apparatus of claim 10 , wherein the duplicate candidates in the database object are identified based on a lookup key of each of the duplicate candidates and based on a field value of the probe entity. 12. The apparatus of claim 11 , wherein the field value of the probe entity corresponds to the lookup field. 13. The apparatus of claim 12 , wherein the other field of the database object comprises a non-lookup field of the database object. 14. The apparatus of claim 13 , wherein the duplicate candidates in the database object are identified based the lookup field and the non-lookup field. 15. A non-transitory machine-readable medium carrying one or more sequences of instructions for identifying match candidates, which instructions, when executed by one or more processors, cause the one or more processors to: generate a match key associated with a lookup field of a database object and associated with another field of the database object; activate a matching rule associated with the match key; receive a request to search for candidates that are duplicates in the database object, the request including a probe entity; and identify the duplicate candidates in the database object by: creating a plurality of candidate keys by applying the match key to a corresponding plurality of candidates in the database object, and creating a probe key by applying the match key to the probe entity, determining whether the probe key matches any of the plurality of candidate keys, and determining, when the probe key matches any of the plurality of candidate keys, whether the probe entity matches any of the plurality of candidates corresponding to the matched candidate keys by applying the matching rule to the probe entity and to the candidates corresponding to the matched candidate keys. 16. The non-transitory machine-readable medium of claim 15 , wherein the duplicate candidates in the database object are identified based on a lookup value associated with each of the duplicate candidates. 17. The non-transitory machine-readable medium of claim 16 , wherein the duplicate candidates in the database object are identified based on a lookup key associated with each lookup value. 18. The non-transitory machine-readable medium of claim 17 , wherein the duplicate candidates in the database object are identified based on a lookup key of each of the duplicate candidates and based on a field value of the probe entity. 19. The non-transitory machine-readable medium of claim 18 , wherein the field value of the probe entity corresponds to the lookup field. 20. The non-transitory machine-readable medium of claim 19 , wherein the match key is further associated with a non-lookup field of the database object, and wherein the duplicate candidates in the database object are identified based the lookup field and the non-lookup field.

Assignees

Inventors

Classifications

  • Physics · mapped topic

  • Physics · mapped topic

  • Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors · CPC title

  • Query processing · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10235476B2 cover?
Some embodiments of the present invention include a method for identifying match candidates in a database object and may include generating, by a database system, a match key associated with a lookup field of a database object. The method may further include activating, by the database system, a matching rule associated with the match key, and receiving, by the database system, a request to sea…
Who is the assignee on this patent?
Salesforce Com Inc
What technology area does this patent fall under?
Primary CPC classification G06F17/30979. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 19 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).