CardSense data documentation

Checklist Data Methodology

How CardSense turns structured release data into consistent, browsable checklist guides.

Source Scope

Each release guide is generated from structured checklist data supplied to CardSense for that product. Unless a guide explicitly says otherwise, it should not be interpreted as a manufacturer-issued or manufacturer-verified checklist. Source data can be incomplete, revised after publication, or use naming conventions that differ from packaging and promotional materials.

Normalization and Consolidation

The generator preserves the source card number, player, team, position, set, and sequence fields while normalizing whitespace and display formatting.

  • Rows are first grouped by their supplied card-set name.
  • Closely matching set names may be consolidated only when they share the same structural card type and each proposed parallel shares at least 90% of its card-number, player, team, and position identities with the family’s shortest, most complete anchor set.
  • The remaining name portion is displayed as a parallel label under the consolidated parent set.
  • Indistinguishable duplicate rows are counted and displayed once; available sequence information is retained.
  • Multi-player and multi-team values are normalized for matching without discarding their display values.
  • Source placeholders such as “TBD” remain visible in checklist tables but are excluded from unique-player, team, position, and frequency summaries.

Understanding the Counts

“Total cards indexed” reports rows in the supplied source data, including rows that represent named parallels. Checklist tables consolidate matching parallel families, so the number of displayed table rows can be lower than the source-row total. Player and team summaries are also computed from source rows and can therefore include repeated appearances across parallels.

Updates and Corrections

The date on each guide identifies when its checklist data was generated. A later page-modified date may reflect navigation, methodology, accessibility, or presentation changes rather than a new source checklist. CardSense reviews reported discrepancies before incorporating them into a future source-data build.