The clean proof that science needs. In recent times, Proof Central has delivered over a million journal articles, for nearly 2000 STM journals, and they have come back twice as quick as PDF proofs used to. Over 90% of authors have favoured our HTML proofs over PDF when given the option to do it either way, consistently, for six years now.
In Proof Central, a journal article equals one URL (for books, a chapter equals one URL). XML-aware publishing systems share this URL with authors as HTML. The authors view the proof as HTML and edit it, do it WYSIWYG, sans code view, in a Freestyle Editing Environment. Once the author finishes, this URL is available to Journal Managers, Editors, Typesetters, or other actors as can be configured. Throughout, the XML remains intact.
Every edit, comment, query and response in Proof Central is recorded by time, actor and the nature of change in an Edit Log, which then becomes a table of contents of sorts to navigate through the edit points in the manuscript. This valuable record is archived, analysed, databased, secured and cloud-hosted. Proof Central has saved publishers a lot of money, has spared them from having to transfer PDF annotations manually; equally from having to face irate authors because a new error got introduced while transferring PDF annotations into the application file. HTML proofing is fast becoming the standard in STM. And Proof Central remains the standard to live up to.
Together with Page Central (see), our browser-based pagination engine, PrC can show the manuscript in the journal's publishing template, with clean pagination, redacting the inline changes made in PrC, to the author and the correction editors in journal production. The corrections are received in HTML. On one click, the browser creates the page. It is the beginning of the end of DTP pagination.
Page Central flips page production upside down. A patent-pending paging engine in Page Central coaxes the browser to render the continuous XML-as-HTML page to neat, cookie-cut pages with publisher logos, footnotes, and page numbers. The floats stay close to their citations. The page is produced only when the user calls it - page on demand, the arrival of zero-inventory page production.
You publish in your style of copy editing, XML, DTD, Schema; in single column or two. It is a feat of auto-pagination on the browser. There is no legacy desktop application. It is one-touch pagination, and it happens in seconds. Ah, it used to take days - Send file to typesetter -> Repaginate -> Regenerate Dataset -> Reload -> and Send a million signals to dozens of workflow systems that all this is happening. Forget it. Now you don’t need a typesetter to paginate and repaginate.
Page Central can be combined and deployed with any or all of the products in the Central suite. Throughout the publishing process, users can revise the page in its intended look and feel. The same XML that is given to DTP is given to the browser instead, and the browser gives the page. The quality is comparable to DTP in appearance. In fact, we have a tough time convincing our experienced customers that what they are seeing is not a typeset PDF. In terms of interactive potential, the quality is way superior to DTP.
PgC went live for an open access journal in August 2015. Since then it has been rolled out to over 1300 journals producing nearly 1.5 million pages. Is it the beginning of the end of DTP? Can we make the page fixed or fluid, print or electronic, for computer or device? Can we cut costs? Can we make the page interactive? Can the page support rich media? Can we generate usage data and analytics? Can we drive engagement? Can we get STM publishing to be on the same page?
Excellent system for fast publication after the acceptance.
Very good process of submission of corrected proof.
Excellent interface. In places where I could not make the changes I needed, I left a comment, which was very helpful.
This is a great tool - way better than other options!