vldb-artifact-evaluationUse when preparing a PVLDB artifact for the pVLDB Reproducibility Evaluation or the ACM availability badge, covering the mandatory participation rule for EA&B papers, the four artifact surfaces evaluators rebuild, packaging for a rerun by strangers, and positioning for the Best Reproducible Paper Aw
vldb-author-responseUse when a PVLDB paper receives a revision verdict and the response package must be built, covering the one-shot revision rule, the three-month window, reading the reviewers' required-changes list, planning new experiments against the clock, and writing the change document that VLDB reviewers re-eva
vldb-camera-readyUse when producing the final PVLDB version of an accepted VLDB paper, covering the volume-specific template, PDF/A compliance and font embedding, figure legibility floors, the availability paragraph and artifact URL, proceedings file naming and copyright steps, and planning presentation at the match
vldb-experimentsUse when designing or auditing the evaluation of a VLDB paper, covering workload and dataset realism at scale, competitor tuning fairness, scalability curves versus single points, tail-latency and throughput reporting, ablations that isolate the mechanism, and the loss-case disclosure PVLDB reviewer
vldb-related-workUse when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations
vldb-reproducibilityUse when engineering reproducibility into a VLDB paper before submission, covering hardware and configuration disclosure, dataset and workload provenance, run-to-run variance in systems measurements, competitor-version pinning, figure-to-raw-data traceability, and the disclosure floor PVLDB reviewer
vldb-review-processUse when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch
vldb-submissionUse when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards
vldb-supplementaryUse when deciding what lives outside a PVLDB paper's page budget, covering the rule that appendices count against the limit, the extended technical report on arXiv under single-blind review, proof and algorithm placement, artifact repositories as the extra-results home, and keeping the paper self-co
vldb-topic-selectionUse when deciding whether a project belongs at VLDB and in which PVLDB category, applying the data-management-primitive test, choosing among Regular, EA&B, Scalable Data Science, and Vision papers, and routing against SIGMOD, ICDE, CIDR, EDBT, PODS, KDD, systems venues, and The VLDB Journal.
vldb-workflowUse when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm
vldb-writing-styleUse when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.