domains / families / research / kdd-related-work
kdd-related-work
separate
Use when positioning a KDD submission against the data-mining lineage (prior KDD volumes, ICDM, SDM, WSDM, CIKM, WWW) and the ML flagships, handling venue misattribution traps, cross-cycle resubmission overlap, concurrent arXiv work, and the mechanism-contrast style of novelty argument that ACM SIGKDD reviewers expect.
When to use
- positioning a KDD submission against the data-mining lineage
- handling venue misattribution traps
- managing cross-cycle resubmission overlap
- addressing concurrent arXiv work
- crafting mechanism-contrast novelty arguments
- auditing positioning before the writing freeze
- identifying and contrasting the nearest KDD ancestor
- triangulating positioning for LLM-era mining papers
When not to use
- journal register related-work sections that survey families instead of stating deltas
- silently resubmitting a prior cycle's rejected paper as new
- submitting the same paper to both research and ADS tracks in one cycle
- making priority claims reviewers cannot check
Skill page
Source