From 00c2ef36167ed29448eb5883b6bc7dca0bcae7b0 Mon Sep 17 00:00:00 2001 From: Michael Shirts Date: Tue, 6 Aug 2019 23:00:14 -0600 Subject: [PATCH 1/2] instructions to post PDF articles --- _editorial_policies/02_editor_instructions.md | 27 ++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/_editorial_policies/02_editor_instructions.md b/_editorial_policies/02_editor_instructions.md index 6b95aec..e649b22 100644 --- a/_editorial_policies/02_editor_instructions.md +++ b/_editorial_policies/02_editor_instructions.md @@ -66,7 +66,7 @@ Following acceptance, the editor's responsibiltiies are: > - Author 2: Jane W. Public, ORCID 0000-0002-4339-2187 > - Online Publication Date: 2018 - In the above email: - - The article URL is generated by saving the publication, and looking at the URL generated by selecting the green "Preview" on the right menu. This URL will be of the form https://livecoms.scholasticahq.com/draft/article/XXXX-the-title, where `XXXX` is the article ID, and `the-title` is the title. The final future published URL can be obtained by replacing https://livecoms.scholasticahq.com/draft/article with https://www.livecomsjournal.org/article (see example above) + - The article URL is generated by first creating looking at the URL generated when creating a new article (see [creating a new article](#creating-a-new-article) for instructions. This URL will be of the form https://livecoms.scholasticahq.com/draft/article/XXXX-the-title, where `XXXX` is the article ID, and `the-title` is the title. The final future published URL can be obtained by replacing https://livecoms.scholasticahq.com/draft/article with https://www.livecomsjournal.org/article (see example above) - The proposed DOI is of the form `10.33011/livecoms.(volume #).(issue #).(article ID #)`, where the article ID is generated by importing the article into a new publication, and saving, and looking at the preview, as described above; it's the `XXXX` right after https://livecoms.scholasticahq.com/draft/article. - List all authors (not just the first two). - The initial date can just be the year (that field is required for initial request), as it will be updated to be the final date when the issue is published. @@ -77,4 +77,29 @@ Following acceptance, the editor's responsibiltiies are: - The managing editor posts the PDF as an ASAP article. - The managing editors will notify the authors articles that are posted as ASAP articles several weeks before the release of the next issue, to identify if there are any typo fixes, errors, added ciations the authors would like to make, and to notify the editor of their articles of changes. The authors will make these updates as pull requests through the website (no need to resubmit it through Scholastica at this point) no later than one week before the notified issue publication date, and put the new version pdf in the release folder as described in the authors instructions. If acceptable, the editor will notify the managing editors of the updated version. If not acceptable, the editor will work with the authors to address the issues. When ready, the managing editors will post it to the LiveCoMS site. - At the publication of the issue, the managing editors send the publication date to cuscholaradmin@colorado.edu with the DOI and the updated date. + +## Creating a new article + +These instructions are for managing ediitors to post new papers + +- Go to the 'Publishing' tab on the main journal site. Select the blue 'New' pull-down button on the upper right, and select 'PDF Article'. +- At the top of the form with publication information, choose the option to "Import it here', and select the proper accepted article. It will auto-import the metadata. +- If there is missing metadata, find and insert it (the editor in charge of the paper should already have made sure it is entered, but one should check. +- Insert the lede provided by the author, as well as the article image. Verify that the article image is sufficiently high resolution. +- Press the green 'Preview' button to get the webpage. Follow the instructions above to get the DOI from CU. +- Journal issues need to be created beforer articles can be placed in an issue. + + + + + + + + + + + + + + From 8bc8296d54fa182377ea5ffbc6f4367905507135 Mon Sep 17 00:00:00 2001 From: Michael Shirts Date: Wed, 7 Aug 2019 10:11:20 -0600 Subject: [PATCH 2/2] remove extra lines. --- _editorial_policies/02_editor_instructions.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/_editorial_policies/02_editor_instructions.md b/_editorial_policies/02_editor_instructions.md index e649b22..c7810ac 100644 --- a/_editorial_policies/02_editor_instructions.md +++ b/_editorial_policies/02_editor_instructions.md @@ -88,18 +88,3 @@ These instructions are for managing ediitors to post new papers - Insert the lede provided by the author, as well as the article image. Verify that the article image is sufficiently high resolution. - Press the green 'Preview' button to get the webpage. Follow the instructions above to get the DOI from CU. - Journal issues need to be created beforer articles can be placed in an issue. - - - - - - - - - - - - - - -