-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
instructions to post PDF articles #193
Open
mrshirts
wants to merge
2
commits into
master
Choose a base branch
from
new-articles
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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,14 @@ 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 [email protected] 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. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Add instructions for page number and publication date. |
||
- 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. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remind that version number is needed in title