This page documents the details of the metadata emails that journals send to Dryad, notifying Dryad of a new manuscript, or a change in status for a previously reported manuscript. These notices allow Dryad to create and prepopulate a record for the data, greatly facilitating the author's process of data deposit.
Below is the complete template for all notification emails sent by journals to Dryad. Since these notices are processed automatically, following these format requirements is critical.
- Notices to the Dryad system can be generated as separate items from a manuscript submission system, or alternatively Dryad can be copied on existing notices to authors, as long as the content needed by the Dryad system is the last part of the email. Some journals use their standard emails to authors, prefacing the Dryad content with a statement like: "Below is the information about your manuscript that we are relaying to the Dryad repository to facilitate your data archiving."
- For journals that use Manuscript Central/Scholar One, the general format and content of the email is specified in the Manuscript Central template for Dryad created by Tim Vines.
From: XXX To: firstname.lastname@example.org Subject: Prepopulation data email
Journal Name: ##JOURNAL_NAME## Journal Code: XXXX Print ISSN: XXX Online ISSN: XXX Journal Admin Email: ##EMAIL_CONTACT_ADMIN_CENTER_EMAIL## Journal Editor: ##PROLE_MANAGING_EDITOR_FIRSTNAME## ##PROLE_MANAGING_EDITOR_LASTNAME## Journal Editor Email: ##PROLE_MANAGING_EDITOR_EMAIL## MS Reference Number: ##DOCUMENT_ID## Article Status: accepted MS Title: ##DOCUMENT_TITLE## MS Authors: ##DOCUMENT_AUTHORS## Contact Author: ##PROLE_AUTHOR_FIRSTNAME## ##PROLE_AUTHOR_LASTNAME## Contact Author Email: ##PROLE_AUTHOR_EMAIL## Contact Author Address 1: ##PROLE_AUTHOR_ADDRESS1## Contact Author Address 2: ##PROLE_AUTHOR_ADDRESS2## Contact Author Address 3: ##PROLE_AUTHOR_ADDRESS3## Contact Author City: ##PROLE_AUTHOR_CITY## Contact Author State: ##PROLE_AUTHOR_STATE## Contact Author Country: ##PROLE_AUTHOR_COUNTRY## Contact Author ZIP/Postal Code: ##PROLE_AUTHOR_POSTALCODE## Keywords: ##ATTR_KEYWORDS## Abstract: ##DOCUMENT_ABSTRACT## EndDryadContent
Note that the Abstract should always be the last item in the email, with no text following it. If this is not possible (e.g., if the journal email system automatically adds a footer), the message should be terminated with the tag EndDryadContent.
The following fields must be present, or the email will not be processed:
- Journal Code - This field is the preferred way to determine where the message goes within Dryad, and what version of the processing system is used. If the Journal Code is not present, the Journal Name will be used. Without a journal code or properly formatted journal name, the messages cannot be processed.
- Journal Name - If the Journal Code is not present, this field is used to determine where the message goes within Dryad, and what version of the processing system is used. Since Journal Names may change, it is preferred to use the Journal Code.
- MS Reference Number - The manuscript number that will be used to identify an article within Dryad during the submission process. This typically corresponds to the journal's internal manuscript number.
- MS Title - The manuscript's title. This will be displayed to the author during the submission process, allowing the author to verify that the correct article has been selected. The title of the Dryad data package will be identical to this title, with the words "Data From:" prepended.
- MS Authors - A list of authors, separated by semicolons. Each author name is in the format "Last, First" (without quotes). Note that this is the default format produced by ScholarOne. Dryad can accommodate a different format, as long as there is a clear way to discriminate between names.
- Article Status - Specifies how Dryad will handle data submitted in relation to the article. See values below.
All other fields are optional. Any field that is blank should not be included in the email.
The Article Status field is mandatory. It specifies how Dryad will handle data submitted in relation to the article. Acceptable values and their meanings:
- submitted - The manuscript has been submitted by an author, and is being processed/reviewed by the journal. Data submitted to Dryad will only be available to users who have the "reviewer PIN". A provisional DOI will be assigned, but the DOI is not registered, and will not resolve.
- accepted - The article has been accepted for publication. Data submitted to Dryad will be made available subject to the embargo status chosen by the author. If data had been submitted while the article was under review, this data will now become publicly available (again, subject to the author's embargo selection). A DOI will be assigned, and will resolve.
- rejected - The article has been rejected by the target journal. If data had been submitted while the article was under review, the data package will be moved into the user's workspace, and remain available for future submissions.
- needs revision - Reviewers have requested that more experiments be performed, or more data be supplied. If data had been submitted while the article was under review, the data package will be moved into the user's workspace, and remain available for future submissions.
- published - This article has appeared in print. Data that had been in "blackout" status will be visible (subject to embargo restrictions). If the data is under an embargo for 1 year or a custom length, the end date for the embargo will be set.
- rejected and referred to X - The article has been rejected by the target journal, but the author has been directed to resubmit the article to journal X. The value of X should be the Dryad abbreviation for a journal. Currently, Dryad will treat this status as equivalent to the rejected status.
If the journal wishes to seek author consent before sending manuscript details to Dryad, they may use this template which adds a checkbox to the initial manuscript submission phase, asking if the author would like deposit data in Dryad. This Scholar One template was created by Tim Vines for use with Molecular Ecology.