ACM TAPS moved my camera-ready to support, deadline is in 2 days. Anyone been through this? [D]

The anxieties of academic publishing are rarely discussed with the candor found in online forums like Reddit, but the recent post from /u/channel_hopper_ highlights a systemic frustration that resonates deeply with researchers: the unpredictable nature of automated publishing pipelines. Their experience with ACM’s TAPS (The Association for Computing Machinery’s Templates and Publishing System) – a common tool for camera-ready submission – underscores a critical tension in modern academic workflows. While the promise of automation is increased efficiency and reduced errors, the reality often involves unexpected technical hurdles and a reliance on often-slow support systems, particularly when deadlines loom. This isn’t merely a one-off issue; it's a symptom of a broader trend where complex systems, designed to streamline processes, can ironically introduce new points of failure and stress for researchers. We’ve seen similar issues raised regarding IEEE’s Xplore platform, where usability and support responsiveness have been consistent concerns IEEE Xplore Issues. The situation also mirrors discussions around ORCID iDs and their integration into various publishing platforms, demonstrating a consistent struggle to bridge human workflows with automated systems ORCID Integration Challenges.

The core problem, as articulated by /u/channel_hopper_, isn’t necessarily the "source to HTML conversion issue" itself – these are technical glitches that can arise – but the *lack of agency* it creates for the author. Having addressed the problem and submitted the corrected files, the researcher is now entirely dependent on TAPS Support, a system notoriously known for its turnaround times. The removal of the upload option from their dashboard further exacerbates the situation, effectively locking them out of their own submission process. This highlights a fundamental flaw in many automated publishing systems: they often prioritize process over user control. While these systems aim to enforce standardization and quality control, they can inadvertently create bottlenecks and increase anxiety, particularly when deadlines are tight. The publication chairs’ potential willingness to grant extensions is a welcome possibility, but the uncertainty inherent in the situation remains a significant source of stress. The fact that support tickets for similar issues can take 72 hours or more, as the author notes, is a stark reminder of the disconnect between the urgency of academic deadlines and the often-slow pace of technical support.

Beyond the immediate frustration for /u/channel_hopper_, this incident points to a larger need for greater transparency and control within academic publishing workflows. Researchers deserve to understand *why* these conversion issues occur, what steps are being taken to prevent them, and what recourse they have when they arise. A more robust system would offer real-time feedback during the compilation process, allowing authors to identify and address potential issues *before* submission. It would also provide clearer communication channels with support teams, ensuring that researchers are kept informed of the status of their submissions and have access to timely assistance. Furthermore, the ability to resubmit corrected files directly, rather than relying solely on support intervention, would empower authors and reduce the risk of missed deadlines. The reliance on automated systems shouldn’t come at the expense of researcher agency and control; instead, it should be leveraged to *enhance* their workflow, not hinder it.

Ultimately, the experience of /u/channel_hopper_ serves as a cautionary tale. While the adoption of automated publishing systems is undoubtedly a step forward, it’s crucial that these systems are designed with the user – the researcher – at their core. The future of academic publishing hinges on finding a balance between efficiency and control, ensuring that technology serves to empower, rather than frustrate, the scholarly community. A critical question to watch is whether publishers will proactively address these systemic issues and prioritize user experience within their automated publishing platforms, or if researchers will continue to navigate a landscape of unpredictable technical hurdles and opaque support processes.