# Resolve Duplicate Options

<p class="callout info">The **Resolve Duplicates** feature in OPSCOM allows administrators to identify and merge duplicates by email, student number, staff number and vehicle (plate) in the system. This is crucial for maintaining data accuracy, preventing operational errors, and ensuring that enforcement and permit management processes are based on clean, unique vehicle data. This article focuses on resolving duplicates by vehicle, however, the concept is the same for other data types.</p>

1. Click on **Tools**, hover over **Resolve Duplicates**, then click **By Vehicle.**

---

### Using this Feature

On the **Resolve Duplicates By Vehicle** page, you will be presented with options to define the criteria for identifying potential duplicate vehicle records.

##### <span style="text-decoration: underline;">Duplicate Identification Options</span>

There are two choices to generate a list of potential duplicates:

**Strict Duplicate**

<p class="callout info">**Purpose**: This option generates a list of vehicles where all three primary unique identifiers are **identical.** This is for finding exact, unambiguous duplicates. Unique identifiers are:</p>

- **Plate**
- **State/Province**
- **Plate Type**

**Include Different Plate Types**

<p class="callout info">**Purpose**: This option generates a list of vehicles where the **Plate** and **State/Province** are identical, but the **Plate Type** may differ. This is particularly useful for identifying potential input errors where a vehicle might have been entered twice with the correct plate and province, but an incorrect or unspecified plate type was initially used.</p>

**Example**: If a vehicle is a beige BMW sports car with plate **ABC123**, province **Ontario**, and an **unspecified** Plate Type, but there's another record for a beige BMW sports car with plate **ABC123**, province **Ontario**, and Plate Type **Passenger**, it is highly probable that these are the same vehicle entered as a duplicate. Comparing the vehicle description (make, model, color) can help confirm such cases.

##### <span style="text-decoration: underline;">Resolving Duplicates</span>

Once a list of potential duplicates is generated based on your chosen criteria:

1. Review the list carefully, paying close attention to vehicle descriptions and other details to confirm actual duplicates.
2. For each pair of duplicate records you wish to merge, click the **Merge** button provided next to the entries.
3. Clicking **Merge** will take you to the merge function window, where you can select which information to retain from the duplicate records and then finalize the merge.

[![2024-08-13_14-41-29.png](https://opscom.wiki/uploads/images/gallery/2024-08/2024-08-13-14-41-29.png)](https://opscom.wiki/uploads/images/gallery/2024-06/UZrimage.png)

---

### <span style="color: rgb(22, 145, 121);">Best Practices &amp; Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Core Vehicle Identification**: In OPSCOM, vehicles are uniquely identified by three key pieces of information: **License Plate**, **Province / State**, and **Plate Type**. All three details are essential for a vehicle to be considered unique within the system (e.g., "ABC123" could be a passenger plate and also a commercial plate in the same province, requiring the plate type for distinction).</span>
- <span style="color: rgb(22, 145, 121);">**Careful Review**: Always thoroughly review potential duplicates before merging. Merging incorrect records can lead to data loss or inaccuracies.</span>
- <span style="color: rgb(22, 145, 121);">**Common Reasons for Duplicates**: Be aware of common scenarios that lead to duplicates:</span>
    - <span style="color: rgb(22, 145, 121);">**Mismatched vehicle information** (e.g., slight variations in plate number or state entry).</span>
    - <span style="color: rgb(22, 145, 121);">**Incorrectly entered plate numbers** or manual data entry errors.</span>
    - <span style="color: rgb(22, 145, 121);">**Orphaned vehicles** that are not properly linked to a user profile.</span>
    - <span style="color: rgb(22, 145, 121);">**Orphaned violations** that should be associated with a specific vehicle but are linked to a duplicate record.</span>
- <span style="color: rgb(22, 145, 121);">**Proactive Data Entry (Prevention)**: The more information included when adding a vehicle to the system, the better. Providing additional details helps the system recognize potential duplicates and reduces errors. In addition to the three key identifiers, it is highly recommended to include:</span>
    - <span style="color: rgb(22, 145, 121);">**Vehicle Colour**</span>
    - <span style="color: rgb(22, 145, 121);">**Vehicle Make**</span>
    - <span style="color: rgb(22, 145, 121);">**Vehicle Model**</span>
    - <span style="color: rgb(22, 145, 121);">**Vehicle Year** These details help to clearly identify specific vehicles and ensure they are properly recorded.</span>
- <span style="color: rgb(22, 145, 121);">**Data Retention**: When merging, OPSCOM typically allows you to select which data fields from the duplicate records you wish to preserve. Ensure you retain the most accurate and complete information.</span>
- <span style="color: rgb(22, 145, 121);">**Regular Maintenance**: Periodically run the **Resolve Duplicates** report to maintain a clean and accurate vehicle database, especially after periods of high user registration or manual data entry. **Duplicate vehicles can cause significant confusion, especially when multiple drivers are associated with the same vehicle, impacting permit management and enforcement accuracy.**</span>
- <span style="color: rgb(22, 145, 121);">**User Training**: If duplicate entries are a recurring issue, consider reviewing user training or data entry procedures to minimize future occurrences.</span>