Currently, according to the readme, this plugin will send a job to our service every time an article is uploaded, but will only -- and always -- populate the final "galleys" versions of an article with HTML, XML, and PDF documents (no ePub currently as this plugin predates our ePub support, but it will overwrite any existing galleys) after uploading a typesetting-ready "layout version" during the last phase of the editorial process.
At a minimum, we probably need individual toggles for XML / HTML / PDF / ePub, in cases where journals might not want to publish an article in all available formats, as well as an option for whether or not existing galleys will be replaced on upload of a new layout version.
axfelix
commented
8 years ago
Currently, according to the readme, this plugin will send a job to our service every time an article is uploaded, but will only -- and always -- populate the final "galleys" versions of an article with HTML, XML, and PDF documents (no ePub currently as this plugin predates our ePub support, but it will overwrite any existing galleys) after uploading a typesetting-ready "layout version" during the last phase of the editorial process.
At a minimum, we probably need individual toggles for XML / HTML / PDF / ePub, in cases where journals might not want to publish an article in all available formats, as well as an option for whether or not existing galleys will be replaced on upload of a new layout version.