Directoryz

Resolve conflicting values when merging listings

A merge should preserve the best-supported value, not simply the newest row. Conflicting information needs a source check.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

List conflicting fields and their sources. Choose a resolution per field and retain a note explaining uncertain decisions.

Worked example · illustrative

What this looks like

One import says a provider serves three regions while a newer official page lists two. Record the official scope and the review date.

Before you move on

Can you explain why the retained value is more reliable?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Keep an untouched source copy.
  2. Test changes on a small sample.
  3. Compare imported records with the original data.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →