Book Isle data tables: distinguish zero, blank, dash and unspecified values

A dash or blank can affect a conclusion more than a printed number. Read a small table in Book Isle, checking the author’s conventions before deciding which values are comparable or calculable. This differs from percentage-denominator checks and assumes no automatic table recognition, missing-value filling or statistical analysis. The reader verifies relationships and meanings.

Preserve title, headers and notes

Choose an authorised table and record book, edition, section, number and page, retaining title, row/column labels and notes. Do not crop just numbers because units and symbols may be below or overleaf. Start with three to five rows and clear cell relationships. Check continued tables’ headers and distinguish PDF file pages from printed numbers. Resolve wrapping or extraction-order problems against a readable source rather than pairing nearby labels and values by proximity.

Record each symbol’s actual stated meaning

Find stated meanings for zero, dash, dot, blank and less-than notation, with scope. Conventions differ, so an absent legend does not make a dash zero or every blank unmeasured. A table-specific note need not apply throughout the book. Distinguish dash, minus and deletion marks against the source where needed. Log undefined symbols as unspecified and preserve them rather than replacing them with zero or deleting them for calculation.

Practise with an explicit invented legend

For this invented exercise only, a dot means unmeasured, a dash inapplicable, numeric zero an explicitly stipulated exact zero in this exercise, and less than one a positive value below one. These are not universal standards. Let rows A–E contain 2, 0, dot, dash and less than 1 in exercise units. A/B are explicit numbers, E is bounded information, and C/D are not zeros. State the legend first and never transfer it to actual sources without their own explanations.

Check units, multipliers and rounding

Check whether headers specify thousands, millions, percentages or per-person units, and whether notes describe rounding and decimal precision. A displayed zero can be rounded and need not establish an exactly zero quantity; the exercise’s explicit zero definition does not transfer to real tables. Do not add unlike units or casually replace ranges with midpoints. Distinguish numeric negatives from inapplicable dashes. Keep displayed value, unit, meaning and precision together rather than mistaking a neat transcription for understanding.

Decide which calculations are supported

A+B equals two exercise units, but that is not a complete five-row total: E is not exact, C unmeasured and D inapplicable. An average needs an explicit inclusion rule and denominator, not zeros substituted for blanks. Published totals can be compared with checkable components, but discrepancies may reflect rounding, scope or definitions rather than arithmetic error. Stop unsupported calculations and state known portions and missing information without expecting automatic imputation.

Check how the prose uses the table

Read the referencing paragraph and test claims such as no change, never occurred or all samples. No data is not no event; unmeasured is not measured zero; inapplicable does not belong in a numeric ranking. Audit a specific sentence rather than condemning a book from one uncertain note. Include supplementary prose, identifying it as additional support rather than table-only information. Preserve the same limits in your paraphrase instead of compressing unavailable into zero.

Keep source symbols beside your classification

Keep table, cell, note and prose locations through supported references or an external log. Recheck copied/exported dashes and collapsed blanks against the source rather than trusting an output as a faithful data table. Include explanatory headers/notes in authorised screenshots without exposing a private book. Recheck conventions and units after edition changes, even with matching row names. Separate displayed symbols from interpretation so later revisions identify transcription versus understanding changes.

Finish without inventing values

Finish by distinguishing zero, unknown, inapplicable and bounded information under this table’s conventions. A dash may mean something else, a rounded zero may conceal a small quantity, and an additive subset is not automatically a full total. Missing notes remain unspecified rather than guessed from a supposed standard. State one supported comparison and its limits, retaining conditions for further checking instead of producing a fictitiously complete numeric table.

Related guides and sources

Read statistical claims in Book Isle: restore denominators, time windows and source tables; Book Isle figure references: connect numbers, pages and reading notes.

Checked on November 5, 2026: Apple public version information lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the official App Store description and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and reading analysis is not presented as an existing automatic application feature.