Create Striking images page

[naushinthomson]

• [x] Create page
• [x] Add description of what is being covered
• [x] Add description of checks required on this content, compiled from current protocol documents
• [x] Add examples covering correct and incorrect scenarios, as required to support checks
• [x] Review house style document to ensure all requirements are covered by GitBook and schematron
• [x] Becky approved page
• [x] Melissa approved page
• [x] Fred approved page
• [x] James approved page
• [x] Naushin approved page

Definition of done

• [x] Page completed
• [x] Team reviewed and approved page?

[Melissa37]

If you have multiple images to upload with captions, you may prefer to upload these all together through the Kriya dashboard. To do this, you should download any existing images and .txt files (if these contain any captions) from the bucket and upload these along with the new images as shown in the previous section.

suggest changing to:

If you have multiple images with captions to add to existing images provided by the author, you may prefer to use the Kriya dashboard. You will need to re-upload the old images at the same time as the new images to prevent overwriting. To do this, you should download any existing images and .txt files (if these contain any captions) from the bucket and upload these along with the new images as shown in the previous section.

[Melissa37]

However, if you are in eJP look at 'More Manuscript Info and Tools' on the right-hand side of the page

Suggest changing to:

However, if you are already in eJP look at 'More Manuscript Info and Tools' on the right-hand side of the page

[Melissa37]

The Features team work...

Change to

The Features team works...

[Melissa37]

The Features team work with authors to write Digests and often, during this correspondence the authors will send them striking images. Features will then forward on these emails to us.

There is a comma missing:

The Features team works with authors to write Digests and often, during this correspondence, the authors will send them striking images. Features will then forward on these emails to us.

[JGilbert-eLife]

Suggest changing

"Occasionally, eLife authors contact us expecting to see their striking image on the personalised poster which they can download from their 'The full version of your eLife article is now available' email they receive upon publication."

to

"Occasionally, eLife authors contact us expecting to see their striking image on the personalised poster which they can download from the publication notification email ('The full version of your eLife article is now available')."

[JGilbert-eLife]

Other than that, and the above comments, seems good to me.

[naushinthomson]

In the 'Uploading a striking image' section:

'The most efficient way to do this is to search the Production inbox for the XML notification, which informs production an article has been exported from eJP.'

Can you add a link to the email from the managing inbox page like you've done in the 'Uploading via eJP' section?

[naushinthomson]

Just a minor point but you can delete the following text from the changelog:

'After Exeter has fed back on the page and it has been updated, any further changes to the page should be listed in order from oldest to most recent. '

[naushinthomson]

That's all from me!

[naushinthomson]

Just had a thought - do we need to cover what to do when an article has been PoA'd but not yet loaded in Kriya and the authors send a striking image through? Even if it's just 'leave a note on the email'?