Resolve a moderation decision

REQUESTED CHANGE

Quality documentation incomplete

The file may be usable, but its documentation or measured quality does not yet support an informed user decision.

What to do

1. Read the moderator note and automatic processing findings for the affected version.
2. Correct missing schema descriptions, coverage, freshness, collection method, limitations, or malformed/null-value explanations identified by the reviewer.
3. Replace the private file only when the data itself must change; otherwise edit the listing fields named by the moderator.
4. Confirm the processing report completes without the cited blocker, then resubmit.

Return to My data

REQUESTED CHANGE

Provenance information incomplete

The reviewer could not confirm that the author has sufficient authority to collect, submit, excerpt, license, or distribute the data.

What to do

1. Identify the source, collection method, owner, and the party granting distribution authority.
2. Correct the legal-basis or consent summary and identify covered geography and collection period.
3. Provide the requested private evidence through the approved evidence workflow, including relevant expiry dates and third-party restrictions.
4. Do not upload contracts, credentials, personal records, or privileged legal advice into ordinary listing text or support messages.

Return to My data

REQUESTED CHANGE

Data does not match the selected policy

The selected category, declared fields, intended user uses, evidence, or license conflicts with the active marketplace policy.

What to do

1. Compare the moderator note with the selected category and every detected field.
2. Correct an inaccurate category or sensitive-field declaration; never relabel data merely to avoid a stricter rule.
3. Remove prohibited material or choose an approved license and user-use restriction when the policy permits correction.
4. If the active policy does not allow the data, do not resubmit until the underlying data or approved policy changes.

Return to My data

REQUESTED CHANGE

User preview needs safety changes

The proposed user excerpt may expose personal, sensitive, confidential, rare, uniquely identifying, or otherwise restricted values.

What to do

1. Review the specific columns or values named by the moderator.
2. Correct sensitive-field declarations and remove prohibited or unnecessary fields from the private source when required.
3. Reprocess the corrected private version so a new candidate is generated; do not manually copy source rows into a public preview.
4. The final preview remains limited to three approved records and may require redaction or suppression before publication.

Return to My data

Request changes versus denial

Changes requested means the same private version can be corrected and resubmitted as directed. Denied means the reviewer concluded that the submitted version cannot proceed through ordinary correction. Follow the denial note and contact support if a reconsideration path is offered.