moodLearning Wiki

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

publishone [2020/05/16 00:23]
serbizadmin 		publishone [2020/06/13 15:10]
Line 1: Line 1:
-====== PublishOne ====== 
  
-**PublishOne** is a service to customize your journal publication platform based on open source codes. [[https://www.moodlearring.com | moodLearning]] supports its development and customization for academic institutions. 
-\\ 
-\\ 
-{{ ::publishone_cover_1.png?650 |}} 
-\\ 
-\\ 
-**PublishOne** is an online submission and evaluation system for authors, reviewers, editors, and publishers. Its publication is reader-centric, allowing a high-level of discoverability and indexability for scaled readership.  
-\\ 
-\\ 
-===== Editorial Workflow===== 
-  * flexible, configurable editorial workflow 
-  * dedicated content management 
-  * the editorial workflow has four (4) stages: submission, review, copyediting, and production. 
-[{{ ::editorial-workflow-diagram.jpg?600 |The **Editorial Workflow** moves from an author's manuscript Submission to the journal's Review, Copyediting, and Production of the work.}}] 
-\\ 
-==== 1. submission==== 
-{{:submission.png?150 |}} 
- 
-  * at this stage of the editorial workflow, an author submits an article 
-  * submissions get assigned to **section editors** who'll consider moving the materials to the next stage (Review) 
-  * at this stage, the journal may consider the //bona fides// of authors, ensure the completeness and veracity of submitted materials 
-  * discussions can already be initiated at this stage to clarify matters such as editorial policies, guidelines, review process, authorship, copyright, and the like. 
-\\ 
- 
-[{{ ::submission_stage.png?600 |**Submission Stage** on the screen of Author. Screenshot is that of an actual paper submission in one prestigious medical journal.}}] 
-\\ 
-Depending on your Role, an editorial stage would appear differently, with options appropriate to your functions. Here's the view of Submission stage from the standpoint of Administrator. 
-\\ 
-  
-[{{ ::submission_stage_-_admin_window.png?nolink&600 |**Submission Stage** on the screen of Administrator}}] 
-\\ 
-To allow for safe and efficient administration and vetting of of submissions, right from the start, uploads are classified by components in the manuscript.  
-\\ 
-{{ ::file_upload_options.png?nolink&300 |}} 
-\\ 
-Article text, research instrument, research materials, results, transcripts, data analysis, data set, source texts--having these components enables not only focused review of the paper but also modular attention to the work. 
-\\  
-==== 2. review==== 
-{{:review.png?150 |}} 
- 
-  * peer review is done at this stage 
-  * revisions may be required from the author during the review process 
-  * accepted revisions may move to the next stage (copyediting) 
-\\ 
-\\ 
-\\ 
-\\ 
-==== 3. copyediting==== 
-{{:copyediting.png?150 |}} 
- 
-  * accepted articles could be improved by copyeditors in this stage 
-  * authors are given the opportunity to review the copyedits  
- 
-[{{ ::copyediting_stage.png?600 |**Copyediting Stage** on the screen of Author. Screenshot is that of an actual paper submission.}}] 
-\\ 
-==== 4. production==== 
-{{:production.png?140 |}} 
- 
-  * completed, reviewed approved copyedits move to the production stage 
-  * copies on this stage are converted to galleys, providing a range of  reader "consumption" options: HTML, XML, PDF, etc.  
-  * even in this stage, authors still have the opportunity to proofread the galleys up for publication in a future issue of the journal 
-\\ 
-\\ 
-=====Publishing===== 
-  * reader-centric front-end 
-  * customizable themes and designs 
-  * subscription module for readers, with delayed open access options 
-  * integrated with scholarly publishing services like Crossref, ORCiD, and DOAJ 
-  * highly discoverable and indexable by search engines and scholarly databases like Google Scholar 
- 
----- 
-[{{ ::workflow_settings.png?500 |**Workflow Settings** on Administrator's screen.}}] 
- 
----- 
- 
-=====User Roles===== 
- 
-{{ ::author.png?150|}} 
-==== author==== 
-  * an author self-registers and makes submissions 
-  * an author is expected to follow the journal's guidelines on manuscript submission 
-  * if multiple authors are involved, a //corresponding author// can be designated by the authors to coordinate with the journal editors 
- 
-{{ ::reviewer.png?150|} 
-}==== reviewer==== 
-  * a reviewer self-registers and reviews the manuscripts 
- 
-{{ ::editor.png?150|}} 
-==== editor==== 
-  * an editor manages submissions and assigns tasks to others 
-  * an editor may also perform the following duties:  
-<code> 
-- read content and correct for errors in spelling,  
-  punctuation, and grammar 
-- evaluate submissions from authors to decide  
-  what to publish 
-- rewrite copy to make it easier for readers to  
-  understand the article 
-- verify facts using standard reference sources 
-- work with authors to help their articles succeed 
-- plan the themes or foci for future publications 
-- enforce the publication’s style and editorial policy 
-- approve final versions of submissions 
-</code> 
- 
-{{ ::section_editor.png?150|} 
-}==== section editor==== 
-  * aka guest editor, a section editor gets special assignment from the editor 
- 
-{{ ::copy_editor.png?150|} 
-}==== copyeditor====  
- 
-  * a copyeditor revise written material to improve readability and fitness for its purpose 
-  * a copyeditor ensures the material is free of grammatical and factual errors 
-  * a copyeditor can only access the copyediting stage and cannot jump to the Review stage to see what happened during the peer review process. 
- 
-{{ ::layout_editor.png?150|} 
-}====layout editor==== 
-  * a layout editor transforms the copyedited versions of the submission into galleys in HTML, PDF, XML, etc. — files which the journal has elected to use for online publication 
-  * a layout editor can also serve as the editor or section editor in some cases 
- 
-{{ ::proof_reader.png?150|}} 
-====proof reader==== 
-  * a proofreader carefully goes over the galleys in the various formats in which the journal publishes (as does the author or the editor) 
-  * a proofreader (and the Author) record any typographic and formatting errors for the Layout Editor to fix 
-  * in some journals, a proofreader can also serve as the editor or section editor 
- 
-{{ ::reader.png?150|}} 
-====reader==== 
-  * a reader is the simplest role and has the fewest capabilities 
-  * a reader receives notification email with the publication of each issue, including the Table of Contents for that particular issue 
-\\ 
- 
-===== Development and Customization=====  
- 
-UI landing page customization:  
-  * changeable color scheme 
-  * more graphical interface 
- 
- 
-User roles: 
-  * add custom user roles to cater specific functions 
Last modified: 2020/06/13 15:10