Indexing and Data Matching
Complete notes for SSC Combined Graduate Level examinations
1The Big Picture — Graphic Mind Map
Indexing
Arrange or locate records using a key. Compare the first decisive character, digit or field; if tied, move to the next.
Data Matching
Compare corresponding fields in a fixed order. Exact match requires all relevant fields to agree under the stated rules.
Mismatch Detection
Identify substitution, omission, insertion or transposition. Count mismatched positions only after aligning the records correctly.
Classification
Place a record into the unique class whose complete condition it satisfies. AND narrows; OR broadens; NOT excludes.
case & format
same with same
chunks then detail
match / class
2The Foundation — Records, Fields and Exact Comparison
Record and Field
A record is one complete row or entry. A field is one labelled component such as name, house number, date, city or centre code.
Compare \(f_i\) only with the corresponding \(f_i\).
Exact Match
Two records match exactly if they have equal length and the character at every relevant position is the same after any explicitly permitted normalisation.
Mismatch Count
For aligned strings of equal length, mark \(1\) where characters differ and \(0\) where they agree.
This is positional mismatch count, not edit distance.
Four Error Types
Substitution
One symbol replaces another: 7 → 2. Length stays equal.
Omission
A symbol is absent. From that point, naive position-by-position scanning produces false mismatches.
Insertion
An extra symbol shifts the remaining sequence. Re-align at the insertion point.
Transposition
Two characters exchange places. It commonly creates two positional mismatches.
Indexing Rules
Alphabetic / Lexicographic Order
- Compare first letter.
- If equal, compare second, then third, and so on.
- At first difference, earlier alphabetic character comes first.
- If one word is a complete prefix of another, the shorter word comes first: RAM before RAMAN.
Numeric Indexing
Decide whether entries are numbers or codes.
- As numbers: \(7=007\).
- As fixed-width codes: 007 and 7 differ in format.
- For equal-length digit strings, compare leftmost unequal digit.
- Do not drop leading zeros in roll numbers or centre codes.
| Field | Compare in this order | Normalisation only if allowed | Frequent distractor |
|---|---|---|---|
| Name | Letters, spaces, initials, order | Case; optional punctuation | Same letters but swapped initials |
| Address | House/flat, street, locality, city, PIN | Standard abbreviations only if rule says | Road vs lane; digit reversal |
| Date | Day, month, year in stated format | Leading zero may be cosmetic only if specified | \(03/07\) confused with \(07/03\) |
| City | Full spelling and qualifier | None by default | Similar names; old/new spelling assumed equal |
| Centre / roll code | Character, block and position | Usually none | O/0, I/1, B/8, S/5 |
| Compound record | One labelled field at a time | Apply field-specific rule | Matching overall appearance |
Address Matching
Segment the address before comparing: unit → building → street → locality → city → postal code. A mismatch in a high-information field such as house number or PIN is immediately decisive.
Date Matching
Fix the format before comparing. Compare year, month and day as labelled fields—not as one visual string. Validate ranges only if the task asks whether the date is possible.
City Matching
Compare the complete city name, suffix/prefix and state when supplied. Do not infer that two names are equivalent from real-world knowledge unless the instructions explicitly permit aliases.
Multi-Field Classification Logic
AND condition
Every clause must be true. If class X requires city = Delhi and code ending in 4, one failed clause rejects X.
OR / NOT conditions
OR needs at least one true clause; NOT removes specified records. Respect brackets and precedence in the written rule.
3Short Tricks & High-Speed Protocols
Two-Way Scan
Scan once left-to-right in chunks, then confirm right-to-left. The reverse pass catches changed suffixes and transpositions missed by anticipation.
Chunk the Code
Insert mental separators at natural blocks: prefix | centre | year | serial. Compare block lengths first, then internal characters.
Edge–Middle Sweep
Check first and last blocks before the dense middle. Test designers often hide a mismatch at an edge while central digits look identical.
One-Field Lock
Cover all but one field mentally. Compare name with name, then date with date, and so on. This prevents cross-column alignment errors.
Stop Rule
For “same or different,” stop at the first decisive mismatch. For “how many differences,” continue and mark each mismatch; do not use the stop rule.
Condition Ladder
Apply the most selective condition first, then the next. A rare prefix or exact city eliminates more classes than a broad condition such as “even digit.”
Alphabetic Tie Breaker
Underline the common prefix. Compare only the next character: KARAN and KARIM share KAR; compare A with I. No need to rescan the prefix.
Transposition Detector
If exactly two adjacent positions mismatch and the pair in one record is reversed in the other—AB versus BA—classify it immediately as a transposition.
| Task | First pass | Second pass | Decision trigger |
|---|---|---|---|
| Exact record match | Length and chunks | Reverse character scan | Any significant mismatch rejects |
| Address match | House/PIN/city | Street and locality spelling | One unequal required field |
| Date match | Format and year | Month and day | Different labelled component |
| Index order | Common prefix | First unequal symbol | Earlier symbol decides |
| Code comparison | Prefix, suffix, block length | Middle digits | First unequal significant character |
| Classification | Most restrictive rule | Remaining clauses | All AND clauses / one OR clause |
4The SSC / TCS Traps — Red Flags
Trap 1: Transposed Digits
728 versus 782 feels familiar because all digits occur. Position matters; same character inventory is not exact match.
Trap 2: Look-Alike Symbols
Distinguish O/0, I/1/l, B/8, S/5, Z/2 and G/6. Use surrounding block type: an alphabetic prefix and numeric serial provide context.
Trap 3: Leading Zero
Numerically \(007=7\), but fixed-width identifiers can differ. Treat codes as strings unless the question defines them as numerical values.
Trap 4: Cross-Field Match
A city in one row may visually align with another row after line wrapping. Lock the row and field; never borrow agreement from a neighbouring record.
Trap 5: Date Format Switch
03/07 and 07/03 can both look valid. Fix DD/MM/YYYY versus MM/DD/YYYY before interpreting; do not use familiarity.
Trap 6: AND Treated as OR
A record satisfying two of three AND conditions still fails. Tick every clause separately before selecting the category.
5Memory Hooks & Mnemonics
RACE
Read rules → Align fields → Compare chunks → End with verification.
SOAT Error Box
Substitution, Omission, Addition, Transposition—the four boxes for explaining nearly every mismatch.
Snake Scan
First row left→right, next verification right→left. The snake does not skip the dangerous suffix.
Address Ladder
House → Street → Locality → City → PIN. Climb in the same order every time.
One Box at a Time
Imagine each field inside a box. Open, compare and close one box before touching the next. This defeats row drift.
Prefix Pencil
Draw an imaginary line under the shared prefix; the first letter outside that line decides alphabetic order.
Classify in Three
Filter by rare condition → test every remaining clause → confirm that no competing class also fits.