icde-artifact-evaluationUse when packaging IEEE ICDE code, data, workload generators, and logs as supplemental material whose availability reviewers score, and for any post-acceptance reproducibility or badge process the edition runs. Covers what a builder-heavy committee inspects first, making a data-systems benchmark tur
icde-author-responseUse when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under the 4-week window, coordinating with area chairs, addressing systems-reviewer pushback on baselines and cost, and deciding
icde-camera-readyUse when preparing an accepted IEEE ICDE paper for camera-ready and IEEE Xplore publication: IEEE eCopyright and PDF-eXpress validation, the IEEE double-column final format, integrating required changes without scope creep, final artifact release, registration and presentation, and the TKDE extended
icde-experimentsUse when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency with declared variance, mechanism-isolating ablations, cost/loss disclosure, and hardware reporting that satisfies a buil
icde-related-workUse when positioning an IEEE ICDE submission against the database canon and neighboring venues, running a reinvention audit across SIGMOD, VLDB, EDBT, and shipping systems, handling two-round concurrency, distinguishing engineering delta from genuine novelty, and covering both the literature and pro
icde-reproducibilityUse when strengthening reproducibility evidence for an IEEE ICDE data-engineering paper: pinning hardware, storage devices, software versions, datasets and workload generators, seeds, and variance protocol; ensuring baseline-tuning fairness; tracing figures to raw logs; and packaging supplemental ma
icde-review-processUse when explaining or planning around IEEE ICDE peer review: the two-round-per-edition structure, area-chair-coordinated assignment with at least three reviewers, two-phase reviewing with a possible Revise & Resubmit, single-blind dynamics, how a builder-heavy committee reads a systems paper, and h
icde-submissionUse when auditing an IEEE ICDE research-track submission for round choice, Microsoft CMT setup, conflict declarations, the IEEE 12-page format, single-blind requirements, supplemental-material availability, the June/November two-round calendar, desk-reject triggers, and final-week sequencing for a d
icde-supplementaryUse when preparing IEEE ICDE supplemental material for the CMT submission: what belongs in the 12-page body versus the supplement, the runnable artifact package (README, run_all.sh, run_small.sh, generators), extended experiments, and single-blind packaging that lets a reviewer assess availability w
icde-topic-selectionUse when deciding whether a project is a strong IEEE ICDE fit, routing among the three database venues from ICDE's seat (SIGMOD's quarterly rounds vs PVLDB's monthly deadlines vs ICDE's two rounds), choosing ICDE research vs industry track, applying the data-management-primitive test, and comparing
icde-workflowUse when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera
icde-writing-styleUse when revising an IEEE ICDE paper for the first-page data-engineering contract, a reconstructable mechanism description, the running-example device, performance claims scoped to the workloads actually run, single-blind first-person phrasing, and 12-page IEEE two-column compression that survives a