A few months ago, we announced the addition of a new rejected article tracking module to our PaperStack service. We’ve now added some exciting new visuals to help users review and analyse the data from this module.
The rejected article tracking module was introduced to address the issue that journal publishers often have little knowledge of the ultimate outcome for submissions they reject. When the module is enabled, all rejected articles from a publisher’s entire journal portfolio are automatically tracked in Crossref to identify if they are later published elsewhere and if so when, in which journal, and with which publisher.
A user-friendly flow diagram has now been added to give a clear overview of the fate of all rejected articles. For some, the journey ends after their initial rejection, while others go on to be published either in-house (in the same or a different journal) or by another publisher. Users can see at a glance which of their competitors are most active here, and can also drill down to list specific competitor journals.
This diagram summarises the data for hundreds of thousands of articles, across all of a publisher’s journals, but can also be filtered by journal, as well as other information such as article type, to provide more specific insights. As with all our charts, everything is fully interactive: the user can click down through the levels to see journal lists, then article lists, and finally details of each individual article – allowing them to further explore particular sets of data.
These analytics tools support editorial teams in monitoring their competition, assessing the quality of their peer review processes, and providing hard data to justify suggested changes – as well as having the potential to help in the identification of author and review fraud.
If you’d like to find out more about how PaperStack can help you understand what happens to your articles after rejection – as well as all the other ways in which it can benefit your publishing programme – do get in touch to request a demo.
The DataSalon Blog 