17 lines
1.3 KiB
Markdown
17 lines
1.3 KiB
Markdown
# Tip #5 — Duplicate-Recipe-Detection
|
|
|
|
**Date:** 2026-06-16
|
|
**Category:** admin
|
|
**Source:** MC-Survival Wiki Daily Tip (backfilled from state.json)
|
|
**Note:** *Title was truncated in the original state.json log. Body matches the 'Search-Synonyms alias table' variant of the same idea.*
|
|
|
|
## Duplicate-Recipe-Detection
|
|
|
|
Duplicate detection runs a normalized-name and normalized-ingredient-set check on every recipe save, warns the editor when a near-duplicate exists, and links straight to the existing entry. It solves the SEO-splitting and user-confusion problem that two recipes for the same item cause: two URLs, two pages, half the traffic on each, and confused players. The signal is the data reality: as the editor base grows, the chance of two people independently documenting the same recipe goes up linearly, and the cost of a duplicate compounds over time. The check should warn, not block — variant recipes are legitimate and forcing a hard merge would lose information.
|
|
|
|
## Implementation tips
|
|
|
|
1. On save, server function checks normalized-name + ingredient-set against existing recipes.
|
|
2. Normalize ingredients: sort alphabetically, lowercase, strip whitespace. Same recipe = same hash.
|
|
3. Warn, don't block — sometimes a near-duplicate is intentional (e.g. recipe variants).
|