SIGMOD Program

PODS Program

Calls For Submissions

SIGMOD 2024 CALL FOR RESEARCH PAPERS

Santiago, Chile, June 11-16, 2024, https://2024.sigmod.org

The PACMMOD issues of SIGMOD 2024 seek contributions in all aspects of data management research. Authors of papers published in the PACMMOD issues of SIGMOD 2024 will be invited to present their work at the SIGMOD conference in June 2024. The annual ACM SIGMOD conference is a leading international forum for data management researchers, practitioners, developers, and users to explore cutting-edge ideas and results, and to exchange techniques, tools, and experiences.

NEW IN 2024

All authors are required to have a registered account with the submission site (CMT).
The submission system will not allow submission of papers that do not satisfy this requirement.
Four paper submission deadlines: January 15 (Round 1), April 15 (Round 2), July 15 (Round 3), October 15 (Round 4)
Submission website: https://cmt3.research.microsoft.com/SIGMOD2024
All Research Track submissions, including the special tracks, must be anonymized and at most 12 pages in length, plus an unlimited number of pages for citations.
Special Track submissions must include the special track name as a subtitle of the title, in parentheses.
Updated conflict of interest policy and conflict declaration on CMT. Note that each author is now required to enter individual domain and PC conflicts on the submission site.
Updated submission eligibility rules: Any rejected submissions to the final round of SIGMOD 2023 (October round) are not allowed to be resubmitted to Round 1 (January round) of SIGMOD 2024. However, such papers may be submitted to subsequent rounds (Rounds 2, 3, and 4).

For all tracks, after the first review, one extra content page is allowed to accommodate the requested revision items. The revised submission should include a cover letter (up to 4 pages) to summarize how the authors have addressed the requested revisions.

TRACKS

There are three research tracks in PACMMOD issues of SIGMOD 2024:

Regular Track
We invite the submission of original research contributions relating to all aspects of data management.
Data Management for Data Science (DMDS) Special Track
We invite the submission of original data science research targeting the data life cycle of real applications, studying phenomena at scales, complexities, and granularities never before possible. This data life cycle encompasses databases/data management/data systems/data engineering often leveraging statistical, machine learning, and artificial intelligence methods and, in many instances, using massive and heterogeneous collections of potentially noisy datasets. Such papers are expected to focus on data-intensive components of data science pipelines; and solve problems in areas of interest to our community (e.g., data curation, optimization, performance, storage, systems). Submissions are expected to describe (a) deployed solutions to data science pipelines and/or (b) fundamental experiences and insights from evaluating real-world data science problems. We expect that the related systems and/or datasets (including possibly query logs) will be accessible for the data management research community in order to promote future research directions.
Data-intensive Applications (DIA) Special Track
We invite the submission of papers describing applications, systems, and datasets (e.g. content, creation, quality), along with the underlying practical data management problems and related research challenges. These applications may stem from outside the core data management community (e.g., computer graphics, computer networking) or even from outside computer science (e.g., astronomy, genomics, healthcare), but have clearly demonstrated non-trivial data-centric challenges necessitating novel systems and technologies. Submissions may describe fundamental experiences and insights gained from deployment or detailed evaluation of data-intensive systems in particular application domains. We expect that the related systems and/or datasets (including possibly query logs) will be accessible for the data management research community in order to promote future research directions.

All research track papers (including special track papers) are subject to double-anonymity requirement.

TOPICS OF INTEREST

Topics of interest include but are not limited to the following:

Benchmarking, database monitoring, performance tuning, and self-driving databases
Blockchains and distributed ledgers
Cloud data management and HPC
Crowdsourced and collaborative data management
Data exploration, visualization, query languages, and user interfaces
Data integration, information extraction, and schema matching
Data models and semantics
Data provenance and workflows
Data quality, data cleaning, and database usability
Data security, privacy, and access control
Data sparsity, boosting, simulated data, and digital twins
Data systems for knowledge discovery, data mining, machine learning, and artificial intelligence
Data warehousing, OLAP, SQL analytics
Distributed, decentralized, and parallel data management
Embedded databases, IoT and Sensor networks
Emerging hardware for data management
Graphs, social networks, web data, and semantic web
Machine learning and artificial intelligence for data management and data systems
Multimedia and information retrieval
Natural language processing for databases
Query processing and optimization
Responsible data management and data fairness
Semistructured, partially structured, and unstructured data
Spatial and temporal data management
Storage, indexing, and physical database design
Streams and complex event processing
Transaction processing
Uncertain, probabilistic, and approximate databases
User-centric and human-in-the-loop data management

SIGMOD welcomes submissions on inter-disciplinary work, as long as there are clear contributions to management of data.

IMPORTANT DATES

New development for SIGMOD 2024: There are 4 submission rounds (January, April, July, and October). Authors of submissions with a revision decision will be given approximately one month to submit a revised version. While we strive to adhere to the published timeline, we note that author feedback and notification dates may vary slightly. Submission deadlines are not expected to be altered.

As we have moved to quarterly deadlines, maintaining consistency is important, both to avoid confusion, and to better manage and plan the workload of the PC. We realize that deadlines may occasionally fall on holidays or weekends. However, we note that holidays are not common across different countries and cultures, and there is variability in which days of the week are considered workdays. We encourage authors to plan ahead and aim to submit a few days early if they wish to avoid a particular holiday or weekend.

IMPORTANT NOTE ON RESUBMISSION ELIGIBILITY: Papers rejected in one round of SIGMOD 2024 are not allowed to be re-submitted in subsequent rounds of the same year. Further, any rejected submissions to the final round of SIGMOD 2023 (October round) are not allowed to be resubmitted to Round 1 (January round) of SIGMOD 2024. However, such papers may be submitted to subsequent rounds (Rounds 2, 3, and 4).

RESEARCH PAPER SUBMISSION ROUND 1 (All Deadlines are 11:59 PM Pacific Time)
January 15, 2023: Paper submission
February 26-28, 2023: Author feedback phase
March 20, 2023: Notification of accept/reject/review again
April 20, 2023: Revised paper submission
May 23, 2023: Final notification of accept/reject

RESEARCH PAPER SUBMISSION ROUND 2 (All Deadlines are 11:59 PM Pacific Time)
April 15, 2023: Paper submission
May 26-30, 2023: Author feedback phase
June 20, 2023: Notification of accept/reject/review again
July 20, 2023: Revised paper submission
August 23, 2023: Final notification of accept/reject

RESEARCH PAPER SUBMISSION ROUND 3 (All Deadlines are 11:59 PM Pacific Time)
July 15, 2023: Paper submission
August 26-30, 2023: Author feedback phase
September 20, 2023: Notification of accept/reject/review again
October 20, 2023: Revised paper submission
November 23, 2023: Final notification of accept/reject

RESEARCH PAPER SUBMISSION ROUND 4 (All Deadlines are 11:59 PM Pacific Time)
October 15, 2023: Paper submission
November 26-30, 2023: Author feedback phase
December 20, 2023: Notification of accept/reject/review again
January 20, 2024: Revised paper submission
February 23, 2024: Final notification of accept/reject

PRESENTATION AND DISSEMINATION

All accepted papers will be treated equally in the conference proceedings, which are the persistent record of the conference. Authors of all accepted papers will have an opportunity to disseminate their works in person as part of the conference program.

The rights of all ACM published authors are detailed at:
https://authors.acm.org/author-services/author-rights

PROCEEDINGS AVAILABILITY

In addition to moving to a quarterly rolling submission and review process, the SIGMOD Executive Committee has decided to move to a model where accepted papers are published in a timely manner in an archival journal.

As a result, all accepted research and industrial track papers in SIGMOD, from SIGMOD 2023 onwards, will appear in the Proceedings of the ACM on Management of Data (PACMMOD), whose URL is https://dl.acm.org/journal/pacmmod. Other conference-related publications such as keynote talk abstracts, demonstration papers, tutorial abstracts, and invited industrial papers will also appear in the companion volume of PACMMOD.

We will provide more information on publication dates once the publication processes are ironed out.

SUBMISSION GUIDELINES

All aspects of the submission and notification process will be handled electronically. Submissions must adhere to the paper formatting instructions. All papers will be judged for quality and relevance. Submissions should be uploaded at:
https://cmt3.research.microsoft.com/SIGMOD2024

Once the paper is submitted, SIGMOD does not accept any changes in the title and/or authorship list, with the rare exception of title changes requested as part of the revision request by the Associate Editor.

DUPLICATE SUBMISSIONS AND NOVELTY REQUIREMENT

Following the ACM guidelines a research paper submitted to SIGMOD 2024 cannot be under review for any other publishing forum or presentation venue, including conferences, workshops, and journals, during the time it is being considered for SIGMOD. Furthermore, after you submit a research paper to SIGMOD, you must await the response from SIGMOD and only re-submit elsewhere if your paper is rejected—or withdrawn at your request—from SIGMOD. This restriction applies not only to identical papers but also to papers with a substantial overlap in scientific content and results.

To enforce this requirement, the high-level metadata of submissions (title, abstract, list of authors), may be shared with the Program Chairs / Editors of other conferences and journals.

Every research paper submitted to SIGMOD 2024 must present substantial novel research not described in any prior publication. In this context, a prior publication is (a) a paper of five pages or more, presented, or accepted for presentation, at a refereed conference or workshop with proceedings; or (b) an article published, or accepted for publication, in a refereed journal. If a SIGMOD 2024 submission has overlap with a prior publication, the submission must cite the prior publication (respecting the double anonymity requirement), and clearly indicate which parts of the work appeared in prior publications and which parts are novel to the current submission.

Any violation of this policy will result in the immediate rejection of the submission, as well as in notification to the members of the SIGMOD Executive Committee, the members of the SIGMOD PC, and the editors or chairs of any other forums involved.

ACM PUBLICATIONS POLICY ON RESEARCH INVOLVING HUMAN PARTICIPANTS AND SUBJECTS

As a published ACM author, you and your co-authors are subject to all ACM Publications Policies, including ACM's new Publications Policy on Research Involving Human Participants and Subjects.

LENGTH, FILE TYPE, AND FORMATTING

Length for submitted papers: All submitted research papers must be formatted according to the instructions below. The main content of the paper must be no more than 12 pages in length for all Research Track papers, although we allow an unlimited number of pages for the bibliography. No appendix will be allowed.

Length for revised and camera ready papers: For all SIGMOD Research track papers, authors are allowed one extra page to help address reviewer comments in the revised version. Therefore, the length of camera ready papers can be up to 13 pages (+ unlimited references).

File type: Each research paper is to be submitted as a single PDF file, formatted for 8.5" x 11" paper and no more than 10 MB in file size. (Larger files will be rejected by the submission site.) Submitted papers must print without difficulty on a variety of printers, using Adobe Acrobat Reader. It is the responsibility of the authors to ensure that their submitted PDF file will print easily on simple default configurations.

Formatting: Research papers must follow the 2-column ACM Proceedings Format, using either the sample-sigconf.tex or Interim layout.docx template provided at https://www.acm.org/publications/proceedings-template for LaTeX (version 2e) or Word, respectively. If you plan to use ACM's official Overleaf template, please use the 2-column template available at https://www.overleaf.com/latex/templates/association-for-computing-machinery-acm-sig-proceedings-template/bmvfhcdnxfty

Please make sure you are using the latest version of the ACM template. The font size, margins, inter-column spacing, and line spacing in the templates must be kept unchanged. Any submitted paper violating the length, file type, or formatting requirements will be rejected without review.

Additional requirements for the Special Track papers: The PDF submission needs to contain the special track name as a subtitle of the title, in parentheses.

PACMMOD format: We note that accepted papers will need to be ported into the PACMMOD format for final publication. However, please do not use the PACMMOD format for submission. Submissions will continue to follow the ACM Proceedings Format for the remaining cycles of this year to maintain consistency.

INCLUSION AND DIVERSITY IN WRITING

We value Diversity and Inclusion in our community and professions. Both are important in our writing as well. Diversity of representation in writing is a simple but visible avenue to celebrate and ultimately help improve our community's diversity. Be mindful in your writing of not using language or examples that further the marginalization, stereotyping, or erasure of any group of people, especially historically marginalized and/or under-represented groups (URGs) in computing. Be vigilant and guard against unintentionally exclusionary examples.

Please visit this page for many examples of both exclusionary writing to avoid and inclusive writing that celebrates diversity to consider adopting: https://dbdni.github.io/pages/inclusivewriting.html. Authors are further encouraged to follow the tips and guidelines provided at: https://dbdni.github.io/#materials. Reviewers will be empowered to monitor and demand changes if such issues arise. Going further, also consider actively raising the representation of URGs in writing. * Please see https://www.acm.org/diversity-inclusion/words-matter for inclusive alternatives for some of the terms commonly used in the computing profession.

ACM POLICY ON AUTHORSHIP REQUIREMENTS

We follow the ACM policy on authorship requirements. Specifically on the use of generative AI tools and technologies, the guidelines note that: "Generative AI tools and technologies, such as ChatGPT, may not be listed as authors of an ACM published Work. The use of generative AI tools and technologies to create content is permitted but must be fully disclosed in the Work. For example, the authors could include the following statement in the Acknowledgements section of the Work: ChatGPT was utilized to generate sections of this Work, including text, tables, graphs, code, data, citations, etc.). If you are uncertain about the need to disclose the use of a particular tool, err on the side of caution, and include a disclosure in the acknowledgements section of the Work."

ANONYMITY REQUIREMENTS FOR ALL RESEARCH TRACK SUBMISSIONS

Research track submissions (including special track submissions) are subject to the double-anonymity requirement.

Every research track paper submitted to SIGMOD 2024 will undergo a double-anonymous reviewing process, following the three principles put forward in (Snodgrass 2007): authors should not be required to go to great lengths to anonymize their submissions; comprehensiveness of the review trumps anonymizing efficacy. AEs retain flexibility and authority in managing the reviewing process.

PC members and referees, except the Associate Editors, who review the submission will not know the identity of the authors. To ensure anonymity of authorship from the PC members and referees, authors must at least do the following:

Authors' names and affiliations must not appear on the title page or elsewhere in the submission.
Funding sources must not be acknowledged anywhere in the submission.
Research group members, or other colleagues or collaborators, must not be acknowledged anywhere in the submission.
The paper’s file name must not identify the authors of the submission.
Source file naming must also be done with care, to avoid identifying the authors' names in the submission's associated metadata. For example, if your name is Jane Smith and you submit a PDF file generated from a .dvi file called Jane-Smith.dvi, your authorship could be inferred by looking into the PDF file.

To avoid compromising the double-anonymity requirement, we request that the authors refrain from publicizing and uploading versions of their submitted manuscripts to pre-publication servers, such as arXiv, and other online forums during the reviewing period. If a version of a submission already resides on a pre-publication server, such as arXiv, the authors do not need to remove it before submitting to SIGMOD.

You must also use care in referring to related past work, particularly your own, in the paper. For example, if you are Jane Smith, the following text gives away the authorship of the submitted paper:

In our previous work [1, 2], we presented two algorithms for ... In this paper, we build on that work by ...

Bibliography
[1] Jane Smith, "A Simple Algorithm for ...," Proceedings of ACM SIGMOD 1997, pp. 1 - 10.
[2] Jane Smith, "A More Complicated Algorithm for ...," Proceedings of ACM SIGMOD 1998, pp. 34 - 44.

The solution is to reference one's past work in the third person. This allows setting the context for your submission, while at the same time preserving anonymity:

In previous work [1, 2], algorithms were presented for ... In this paper, we build on that work by ...

Bibliography
[1] Jane Smith, "A Simple Algorithm for ...," Proceedings of ACM SIGMOD 1997, pp. 1 - 10.
[2] Jane Smith, "A More Complicated Algorithm for ...," Proceedings of ACM SIGMOD 1998, pp. 34 - 44.

Despite the anonymity requirements, you should still include all relevant work of your own in the references, using the above style; omitting them could potentially reveal your identity by negation. However, self-references should be limited to the essential ones, and extended versions of the submitted paper (e.g., technical reports or URLs for downloadable versions) must not be referenced.

Common sense and careful writing can go a long way toward preserving anonymity without diminishing the quality or impact of a paper. The goal is to preserve anonymity while still allowing the reader to fully grasp the context (related past work, including your own) of the submitted paper. In past years, this goal has been achieved successfully by thousands of papers.

It is the responsibility of authors to do their very best to preserve anonymity. Papers that do not follow the guidelines here, or otherwise potentially reveal the identity of the authors, are subject to immediate rejection.

No exceptions will be made to the double anonymity requirement for Research Track papers. If the authors of a submission feel that double anonymity needs to be violated, for example to reveal the identity of a system, they may consider submission to a SIGMOD track that does not impose a double anonymity requirement, such as the Industry Track.

ARTIFACTS and REPRODUCIBILITY

SIGMOD strives to establish a culture where sharing research artifacts (data, results, code, and scripts) is the norm rather than an exception. SIGMOD reproducibility has three goals: (a) Highlighting the impact of database research papers; (b) enabling easy dissemination of research results; and (c) enabling easy sharing of code and experimentation set-ups. In this context, we expect all papers to make their code, data, scripts, and notebooks available if this is possible. Although it is not mandatory for acceptance, providing this extra material can help reviewers evaluate your work more thoroughly. Papers published at SIGMOD which have been successfully reproduced are also recognized and highlighted as such in the ACM Digital Library.

Please include a link with your materials in the text box provided in the submission form at the time of submission. For all Research Track submissions, the link and materials should preserve anonymity. For example this may be an anonymous GitHub repository. You may want to make sure that the link you provide is not indexed by search engines. On GitHub, you can do so by adding the following to the page head:

We recognize that at the time of submission authors focus on fine-tuning the paper, and so we expect this link to be live within two weeks from submission. Reviewers that may need to look at the materials will not do so earlier than that. We do not expect a fully polished submission in terms of automatically reproducing results, but rather a reasonably clean version of the state of the code when submitting the paper. Please, do not use a shortened link which traces who accesses it.

In the event that you are not able to submit your code, data, scripts, and notebooks please explain in the text box provided in the submission form why this is the case.

CONFLICTS OF INTEREST (Updated in 2024)

During submission of a research paper, the submission site will request information about conflicts of interest of the paper’s authors with program committee (PC) members. It is the full responsibility of all authors of a paper to identify all and only their potential conflict-of-interest PC members, according to the definition below. Papers with incorrect or incomplete conflict of interest information as of the submission closing time are subject to immediate rejection.

Definition of Conflict of Interest: A paper author has a conflict of interest with a PC member when, and only when, one or more of the following conditions holds:

The PC member is a co-author of the paper.

The PC member has been a co-worker in the same company or university within the past five years.¹

The PC member has been a collaborator within the past five years.²

The PC member is or was the author's primary thesis advisor, or post-doctoral advisor, no matter how long ago.

The author is or was the PC member's primary thesis advisor, or post-doctoral advisor, no matter how long ago.

The PC member is a relative or close personal friend of the author.

¹Short-term associations, such as summer internships do not constitute institutional COIs. E.g., a student who interned at Microsoft should declare as conflicts any individuals in the group they worked with and other collaborators on their projects, but they should not declare a domain conflict with microsoft.com.

²Collaborations are indicated by prior co-authorships, shared grant funding, and close research relationships, even if those have not yet resulted in common publications. Publications (typically with a large set of authors) that fall outside the traditional sense of research collaborations (e.g., “The Seattle Report on Database Research”, “ Diversity and Inclusion Activities in Database Conferences: A 2021 Report”, etc.) do not in themselves constitute a COI.

To identify any potentially spurious conflicts, PC members may be asked to confirm declared conflicts with submitting authors.

Conflict declaration on CMT: Conflicts will no longer be declared per submission. Rather, each author is now responsible for entering their own individual domain and PC conflicts on CMT. You can mark your conflicts by clicking on your name (upper right-hand side on CMT) and selecting ''Domain Conflicts'' and ''Individual Conflicts''. An author's declared conflicts will be automatically applied to all of their submissions.

REVIEWING PROCESS AND REVISIONS

Number of reviews: Each submission will first receive at least three reviews. At the discretion of the AE and the PC chairs, additional reviews may be procured.

Author Feedbacks: Before the discussion phase starts between reviewers and decisions are made, authors will have a few days to read the reviews and submit optional brief feedback. The sole purpose of the author feedback is to clarify misunderstandings and factual errors through pointers to specific text in the submitted paper. As an example, a reviewer may have overlooked a part of the discussion in the paper and state that the paper fails to compare with a certain method; an example feedback will be of the form "see Section 2.4, paragraph 3". If no factual errors exist in the reviews, author feedback is not needed.

Revisions: Some authors will be invited to submit a revised version of their paper. Authors will have one month to implement the revision items. The revision process is intended to be a constructive partnership between reviewers and authors. To this end, reviewers will be instructed to request revisions only in constructive scenarios with specific requests. In turn, authors bear the responsibility of attempting to meet those requests within the stated time frame, or of withdrawing the paper from submission. Common revision requests can include ''justify a crucial assumption'', ''present a real(istic) scenario where the defined problem occurs'', ''clean up notation'', ''tighten presentation'', ''compare against some relevant previous system'', ''show experimental results with better data, such as at larger scale or from a real system''. Revisions will not be requested to address lack of technical depth or novelty or where the revised paper will address a substantially different problem from the original.

For all tracks, one extra content page is allowed after the first review to accommodate the requested revision items. The revised submission should include a cover letter (up to 4 pages) to summarize how the authors have addressed the requested revisions. Authors are encouraged to highlight parts of their revised manuscripts that are edited in a different color to ease their identification by the reviewers.

VENUE MAPS

Welcome

Special Events

Organization

Participant Information

PROGRAM OVERVIEW