Duplicate Identification Procedures

This subsection covers the system-defined identification procedures used to determine whether two entities, of the same entity type, might be duplicates.

 

These types of entities aren't used in the duplicate identification procedure:

  • Document

  • Image

  • Media

  • Offence

  • All the miscellaneous types of entities that are inherited from the previous list

 

This table lists the duplicate identification procedures for the entity types.

Entity type Two entities are duplicates if…
Contact number (free format)

The Number field isn't blank

One of the words or numbers, of more than four characters in length, are an exact match

Contact number (default)

The Number field isn't blank, and the Number fields are an exact match

The Country field isn't blank, and the Code fields are an exact match

Event

The Begin Date fields are the same

At least one word in both Description fields is the same (case- sensitive)

Location

The Building Name fields aren't blank and close-matched.

One location has a blank Street Number, or both Street Number fields are close-matched, and:

The Street Name fields are close-matched

One location has a blank Country field, or both Country fields are the same

One location has a blank State field, or both State fields are the same

One location has a blank City field, or both City fields are close- matched

One location has a blank Suburb field, or both Suburb fields are close-matched

Miscellaneous

The entity type for both entities is the same

At least one word, in the first three words, of both Title fields is the same (case-sensitive)

If the entity type is inherited from a system-defined entity type, the entities are handled the same way as the entity types they're inherited from.

Organisation

One organisation has a blank Country field, or both Country fields are the same

One organisation has a blank State field, or both State fields are the same

The Name fields are close-matched.

Person

The first set or second set of conditions apply:

First set of conditions:

One person has a blank or unknown Gender field, or both Gender fields are close-matched.

Both Surname fields are blank, and one of the following applies:

  • The Given name 1 fields are close-matched

  • The Given name 2 fields are close-matched

    • The Given name 1 field of one person is close-matched with the Given name 2 field of the other person

    • The Given name 2 field of one person is close-matched with the Given name 1 field of the other person

  • One person has a blank D.O.B. field, or both D.O.B. fields are close-matched (within a range of one year), and one of the following:
    • The Given Name 1 fields are reasonable-matched (for the first two characters), or both names are missing

    • The Given Name 2 fields are reasonable-matched (for the first two characters)

    • The Given Name 1 field of one person is close- matched with the Given name 2 field of the other person

    • The Given Name 2 field of one person is close- matched with the Given name 1 field of the other person Second set of conditions (which must all apply):

One person has a blank or unknown Gender field, or both Gender fields are close-matched.

The Surname fields are close-matched.

The D.O.B. fields are close-matched (within a range of six months).

Transaction

The Date fields are the same.

One transaction has a blank Value field, or both Value fields are close- matched (within a ten percent range).

At least one word, in the first three words, of both Description fields is the same (case-sensitive).

Vehicle

The Registration Number fields are close-matched (ignoring embedded non-alphanumeric characters and spaces).