Jev CSV destination field mapping

Map a CSV column to the right destination field

Supply a column definition, sample values and destination fields. Compare buyer, company and delivery-country meanings, then review an ambiguous or unmatched column.

CSV destination field mappingLive API
Try an example

The source definition specifies purchaser residence.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Map the source column to the supplied destination schema.

Decision rules and labels
Buyer countryCompany countryDelivery countryNo fieldReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Headers are useful clues, but two columns can share the same name and refer to different entities. Sample values such as country names do not settle whether the field belongs to a buyer, company or delivery.

No field preserves a clearly unmatched concept. Review preserves ambiguity among plausible destinations. A full importer still needs deterministic one-to-one mapping, required-field checks and user approval.

The linked table-import mapper assesses source/destination pairs. This original single-choice adaptation shows one column at a time; it does not upload a CSV, infer an entire schema or write records.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for csv column mapping.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Supply a column definition, sample values and destination fields.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Buyer country, Company country, Delivery country, No field, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Buyer residenceBuyer country97.0%
Registration locationCompany country99.0%
Shipping destinationDelivery country84.0%
Unmatched conceptNo field98.0%
Generic header aloneReview94.0%
Contradictory ownershipReview100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

CSV column mapping: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing a mapping suggestion against explicit field definitions.
  • Distinguishing near-neighbour destination fields before import.
  • Keeping unmatched columns visible for manual mapping.

Outside this demonstration

  • Treating one column choice as validation of a whole CSV import.
  • Dropping an unmatched column or writing records automatically.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Why are the country values not enough?

The same country names could occur in all three destination fields. The column definition needs to identify the entity or address role.

Can it map an entire spreadsheet here?

This example maps one supplied column. A full import interface needs additional schema validation and review of the complete mapping.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.