The exact comparison
Compare set, number, language, finish and variant. If one of those attributes differs, keep the records separate. If one is missing, the result is possible or pending; a shared name is only a clue to review.
- Shared name: a reason to check, not to merge.
- Complete, equal attributes: a comparable exact reference.
- Incomplete attributes: review pending.
Quantity and duplicates are different indicators
Quantity expresses how many physical copies a record represents. To count additional copies of a confirmed reference, that reference must be checked first. Three copies of the same reference have two additional copies; three records with similar names do not prove that result.
Review before any grouping
Open the photographs and compare attributes. Complete what can be verified and leave the rest pending. The app should not destructively merge records because they share a name; review preserves differences and provenance.
Practical questions
Are holo and reverse cards duplicates?
If finish differs, they do not share the same complete inventory reference. Check the finish on the card: glare in a photo does not confirm it.
What happens when variant is empty?
The reference is incomplete for an exact comparison. Leave it pending and inspect the photo or catalogue when a verifiable source exists; do not assume a default variant.
Local recognition is being validated. The demo is predetermined; it saves no cards and uses no quota. Review attributes against the physical card: condition and authenticity are not certified.