5.50 - Landing pages, secure deep links, article history for authors, production workflow 21 March 2024 🌻🌼🌹 Landing page behaviour The behaviour of Nestor at login has been refined according to your profile and activity. Depending on the following priorities, you will either land on the author, referee or editor dashboard: If you are editor of the journal, you will always land on the editor dashboard Otherwise, if you have pending articles as referee, landing on the referee dashboard Otherwise, if you have active articles as author, landing on the author dashboard Otherwise, if you have active articles as coauthor, landing on the coauthor dashboard Finally, if none of the above apply, you will land on the author dashboard. This behaviour will help people to easily identify actions they have to undertake. Secure deep links Referees and co-authors are the people likely to receive invitations via Nestor deep links. When using those, users will now be restricted to the action page they are invited to. If they want to check their whole Nestor activity, those users will be prompted to log in, using their credentials. Disconnection warnings, autosaved referee reports Nestor will now warn you if you have been disconnected while performing an action. This will help prevent data loss. In the same vein, referee reports are now saved automatically during the course of the drafting. Referee contact form Referees can now contact the editor directly from the report page: Article history now available to authors Authors now have access to a summary of the article history. For the moment, only statuses relevant to authors are displayed. New production statuses The production workflow has been refined again with three new statuses, triggered by specific actions. This will help authors and editors to get a better understanding of the article history during the production process. Action Old status New status Author sends corrections on proof --> In production Proof correction EO sends corrections on proof --> In production EO proof correction EO validates proof --> In production EO proof validation