Why CSV Has Both Rating and Circle—and Why They Can Disagree

SlateX CSV uses one row per camera and still writes one row when a take has no camera. Its header and column order are fixed, and new columns can only be appended to the existing sequence. Rating, Circle, and Circled On Set can look like overlapping on-set judgments, but all three derive from the same rating value under different rules, so one record can produce a combination that appears to disagree.

Rating, Circle, and Circled On Set are all derived from the same rating value under different rules; they are not three independent on-set states.

CSV rows are expanded by camera first

A take with several cameras is expanded into corresponding CSV rows; a take with no camera still produces one row, and the camera-related columns do not share one missing-value shape: some stay empty while others fall back to a default, so a receiver should check them column by column. The header uses fixed English column names, and the column order is defined as a constant rather than changing with the app’s interface language.

That is consistent with What a CSV Handoff Carries That an ALE Does Not: the CSV structure has to be checked from the file itself rather than inferred from another handoff format that may carry different columns.

Rating turns the rating number into fixed English text

The Rating column carries text: Circle, Keep, Hold, or N/G, and an unmarked take stays empty. The neighbouring Circle column is not a second on-set judgment: it writes TRUE only when the rating itself is Circle. These handoff values are fixed English and do not change with the interface language.

Rating is therefore the text form of the on-set mark, not a separate read of on-set state. Chinese, English, and other interface languages can display their own localized labels, while this CSV field continues to write the fixed English words.

Circle is true only for the Circle rating

The Circle column uses a narrow rule: it writes TRUE only when the rating value is Circle; an unmarked take, Keep, Hold, and N/G all write FALSE. It is not a second on-set judgment.

Circled On Set uses a broader derivation rule

Circled On Set is derived from the same rating value, but treats both Circle and Keep as circled on set and writes TRUE for those two ratings; the other ratings write FALSE. A Keep take therefore produces Rating=Keep, Circle=FALSE, and Circled On Set=TRUE. This is not three on-set states contradicting one another; it is one rating value exported through three different rules.

All three columns are derived from the same rating value

Rating turns the rating number into fixed English text; Circle is true only for the Circle rating; Circled On Set is true for the Circle and Keep ratings. All three derive from the same on-set mark under different rules. A receiver should not treat them as independent sources that validate one another or substitute one column for another.

A Keep take can produce Rating=Keep, Circle=FALSE, and Circled On Set=TRUE; the pattern comes from three derivation rules applied to the same rating value.

Two CSV-shape boundaries belong with this explanation

The header is not passed through field escaping. Newlines and tabs inside data fields are flattened to spaces before quoting rules are considered, rather than preserving those line breaks inside quoted fields. The output should therefore not be described as “RFC4180 compliant.” This describes the file’s actual shape and does not predict how any particular downstream spreadsheet or editing system will interpret the file.

The column names are also fixed English and do not follow the app’s language. The receiving principle from Where Each ALE Column Comes From and What to Check Before Using an ALE for Matching applies here as well: a receiver should verify the literal column names, value shapes, and sources against the receiving template.

FAQ

Does Rating change with the interface language?

No. The CSV rating text is a fixed set of English constants, while an unmarked take writes an empty Rating string.

Does an empty Circle cell mean the take was not circled?

The Circle column never comes back empty: it reads TRUE for a circled take and FALSE for every other case.

Why does Keep produce Circle=FALSE?

Circle is true only for the Circle rating, so Keep writes FALSE. Circled On Set uses the broader rule and writes TRUE for both Circle and Keep.

Can Circle be read as the on-set circled state?

No. Circle is true only for the Circle rating. Circled On Set is broader (Circle and Keep are true), but both are different rules over the same on-set mark. Check all three columns against your receiving template.

Axiom One LLC — SlateX