On this page
Read quality in Aurelia
Use the existing sample quality example to connect reported scores with findings and record conditions.
Inspect the installation measurement and check how the customer’s cleaning pipeline treats an incoming phone without changing Aurelia. This keeps the later duplicate exercises reproducible.
Before you begin
Complete Install Aurelia and Follow its data.
Use the initial sample, before edits or duplicate decisions. For these API
steps, set GOLDEN_URL and GOLDEN_TOKEN as in the
API quickstart. Use an ADMIN or STEWARD
credential with access to the sample and install curl and jq.
Read the installation measurement
Open Quality for the customer entity. The initial picture includes all 378 records, with an average score of 96.91. Picture shown identifies its date and time. Use Change to choose the installation measurement if a later one is displayed, then confirm with Show this picture. The initial measurement contains 17 error findings and 149 warning findings; these are occurrences, not necessarily distinct records.
Read Ana’s stored measurement
curl --fail-with-body --silent --show-error \
-H "Authorization: Bearer $GOLDEN_TOKEN" \
"$GOLDEN_URL/api/tables/sample_customer/records/CRM-0001/quality"
Inspect score, storedScore, storedState, findings, and contributions.
The source CSV supplied Ana’s phone as 611000000, but the installed customer
pipeline stores +34611000000. The phone’s old formatting warning is therefore
not an expected finding in this installation. Use the record’s actual
contributions to explain its score rather than assuming a warning from the
source file survived cleaning.
Check a source-form draft
Fetch the record, keep the business fields, and put its original source phone into a local draft. This request sequence saves no record in Golden.
curl --fail-with-body --silent --show-error \
-H "Authorization: Bearer $GOLDEN_TOKEN" \
"$GOLDEN_URL/api/tables/sample_customer/records/CRM-0001" |
jq '{record: (.record | with_entries(select((.key | startswith("_")) | not))
| del(.qualityState, .id) | .phone = "611000000")}' \
> aurelia-quality-draft.json
curl --fail-with-body --silent --show-error \
-H "Authorization: Bearer $GOLDEN_TOKEN" \
-H "Content-Type: application/json" \
--data-binary @aurelia-quality-draft.json \
"$GOLDEN_URL/api/tables/sample_customer/records/check"
The check runs the table’s write pipeline before measuring. In this sample the
cleaner normalizes the draft phone back to +34611000000; compare its findings
and contributions with Ana’s stored measurement. The check writes no record
and creates no table quality measurement. If a pipeline would refuse a draft,
the check reports that refusal instead of giving it a score.
Verify that the sample is unchanged
Read CRM-0001 again. Its stored phone remains +34611000000, and its stored
quality state has not changed. The check was a preview, not a saved correction.
For a lasting correction, change the authoritative source or the configured processing and verify the resulting write. The configuration guide explains that workflow.
Clean up and continue
Delete the local draft when finished:
rm aurelia-quality-draft.json
No reinstall is needed because this exercise changed no sample records. Continue with Search the sample.