Skip to content

Commit

Permalink
Merge pull request #1118 from librariam/patch-62
Browse files Browse the repository at this point in the history
Updated what's new in 3.4
  • Loading branch information
emmauhl authored Aug 1, 2023
2 parents 1753881 + 9d0f3bc commit f6e9ee4
Show file tree
Hide file tree
Showing 5 changed files with 51 additions and 12 deletions.
51 changes: 42 additions & 9 deletions learning-ojs/en/about-ojs.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,18 +44,46 @@ OJS is easy to install and configure. However, running a web service requires a

### Workflow

OJS 3.4 introduces several workflow changes, including a new submission wizard and an improved process for recording editorial decisions.
OJS 3.4 introduces several workflow changes, including:

![New submission wizard](./assets/learning-ojs3.4-submission-wizard.png)
**A new and improved submission wizard**

Among other improvements, it is now possible to save/autosave a submission in progress, change a submission language, and make a submission file (component) required.

See the [Making a Submission](./authoring#making-a-submission) section and [Component](./settings-workflow#components) settings for more details.

![OJS 3.4 new submission wizard](./assets/learning-ojs3.4-submission-wizard.png)

**An improved process for recording editorial decisions**

As part of recording an editorial decision, it’s possible to add any email in CC/BCC fields of the author notification, as well as insert other content. A copy of the notification can be sent to reviewers in a separate screen that uses a reviewer-specific email template, maintaining anonymity from authors.

See the [Making the Decision](./editorial-workflow#making-the-decision) section for more details.

![Editorial decision workflow and new email composition tools](./assets/learning-ojs3.4-editorial-decision.png)

OJS 3.4 introduces new tools for email composition, including the ability to write and select between multiple templates. The editorial decision toolset leverages these new tools, and they will be rolled out to other areas of the system in future releases.
**An option to cancel a stage or a review round**

For more information on the new editorial decisions workflow, see [slide deck](https://docs.google.com/presentation/d/e/2PACX-1vTpSVv_zY4RShrh3EfBZjHcRSYKVqDkzejDnESh6Bkg7uMgM8zFYZz-ha7j3iz_csTKump2_rI3YNWS/pub#slide=id.g16f0bb3e17f_0_26) and [video recording](https://youtu.be/JEJJ1FVpao0?t=1798).
It is now possible to cancel an accidentally started review round, unless a reviewer has completed a review. It is also possible to cancel a stage and move the submission to a previous stage, e.g. from Copyediting to Review, with an option to notify the author about this change.

See the [Additional Round of Review](./editorial-workflow#additional-round-of-review) section for more details.

![Review stage with decision options including cancelling a review round.](./assets/learning-ojs3.4-cancel-review-round.png)

**Enhanced email template tools**

OJS 3.4 introduces new tools for email composition, including the ability to write and select between multiple templates. Each email comes with a glossary of available variables that can be inserted using the ‘Insert Content’ button. The values of variables, such as the author's name, can be previewed before the email is sent.

The default set of email templates that is included with OJS has been rewritten to be more inclusive and friendly.

See the [Email Setup](./settings-workflow#email-setup) section for more details.

![OJS 3.4 emails templates.](./assets/learning-ojs3.4-jm-settings-workflow-single-email-templates.png)

The editorial decision toolset leverages these new tools, and they will be rolled out to other areas of the system in future releases.

For more information on the new editorial decisions workflow, see [slide deck](https://docs.google.com/presentation/d/e/2PACX-1vTpSVv_zY4RShrh3EfBZjHcRSYKVqDkzejDnESh6Bkg7uMgM8zFYZz-ha7j3iz_csTKump2_rI3YNWS/pub#slide=id.g16f0bb3e17f_0_26) and [video recording](https://youtu.be/JEJJ1FVpao0?t=1798).

### Statistics

COUNTER support has been updated to [COUNTER Release 5](https://www.projectcounter.org/counter-release-5/), including tools to report on readership on based on region and institutional access. This has also introduced basic [ROR (Research Object Registry)](https://ror.org/) support for institutional subscriptions.
Expand All @@ -64,20 +92,25 @@ COUNTER support has been updated to [COUNTER Release 5](https://www.projectcount

### Persistent Identifiers

DOI and CrossRef support has been comphrehensively rewritten in consultation with CrossRef and to address common sources of confusion with the previous implementation.
DOI and CrossRef support has been comprehensively rewritten in consultation with CrossRef and to address common sources of confusion with the previous implementation.

(See [slide deck](https://docs.google.com/presentation/d/e/2PACX-1vTpSVv_zY4RShrh3EfBZjHcRSYKVqDkzejDnESh6Bkg7uMgM8zFYZz-ha7j3iz_csTKump2_rI3YNWS/pub#slide=id.g16f0bb3e17f_0_14) and [video recording](https://youtu.be/JEJJ1FVpao0?t=501).)

### Multi-Journal Installations

Site Administrators now have the same managerial access as Journal Managers regardless of whether they also have that role. This is intended to distinguish more clearly between Site Administrators (who are often system administrators or technical support, but are not active in journal workflow) from Journal Managers (who participate in workflow); in previous releases it was often necessary for administrators to have both roles assigned to be effective. (#7392)[https://github.com/pkp/pkp-lib/issues/7392]
Site Administrators now have the same managerial access as Journal Managers regardless of whether they also have that role. This is intended to distinguish more clearly between Site Administrators (who are often system administrators or technical support, but are not active in journal workflow) from Journal Managers (who participate in workflow); in previous releases it was often necessary for administrators to have both roles assigned to be effective. [Github issue #7392](https://github.com/pkp/pkp-lib/issues/7392)

Starting with OJS 3.4.0, Journal Managers now have the ability to control user enrolment in their journal regardless of whether the user is active in other journals. In previous releases, it was often necessary to escalate enrolment issues to Site Administrators when a user was active in multiple journals. [Github issue #7391](https://github.com/pkp/pkp-lib/issues/7391)

### Submission title formatting

Starting with OJS 3.4.0, Journal Managers now have the ability to control user enrolment in their journal regardless of whether the user is active in other journals. In previous releases, it was often necessary to escalate enrolment issues to Site Administrators when a user was active in multiple journals. (#7391)[https://github.com/pkp/pkp-lib/issues/7391]
Submission titles can now contain limited formatting, including bold, italic, underline, superscript and subscript. This is particularly important for articles referencing taxonomical names (which are typically formatted in italics) and for review articles (which may reference the reviewed resource by underlined title). [Github issue #2564]([https://github.com/pkp/pkp-lib/issues/2564](https://github.com/pkp/pkp-lib/issues/2564))

### Other Notable Changes

- Submission titles can now contain limited formatting. This is particuarly important for articles referencing taxonomical names (which are typically formatted in italics) and for review articles (which may reference the reviewed resource by underlined title). (#2564)[https://github.com/pkp/pkp-lib/issues/2564]
- The submission full-text index is no longer updated at the moment the user performs a new upload. In previous releases this was a frequent source of frustration and the update process could be time-consuming.=
* The submission full-text index is no longer updated at the moment the user performs a new upload. In previous releases this was a frequent source of frustration and the update process could be time-consuming.
* Data availability statement can now be enabled as one of the metadata fields.
* A direct “Unsubscribe” link is now added to system notification emails that support unsubscribing, such as new issue, announcement, discussion notifications, etc.

### More Information

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 5 additions & 1 deletion learning-ojs/en/editorial-workflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -611,7 +611,7 @@ It is best to start a new round of review **after** an author uploads revised fi

A new round should **not** be started if you are experiencing any issues with the current round (i.e., unable to record decision, re-invite a declined or removed reviewer).

To start an additional round of review after revised files have been received, click the **New Review Round** tab in the review tab of the manuscript. As of OJS 3.4 you can cancel an additional review round.
To start an additional round of review after revised files have been received, click the **New Review Round** tab in the review tab of the manuscript.

![The New Review Round button in the Review panel](./assets/learning-ojs-3-new-round-1.png)

Expand Down Expand Up @@ -639,6 +639,10 @@ Reviewers from previous rounds will not have access to comments they've made the

These steps can be repeated until a final decision to accept or decline the manuscript has been reached.

In OJS 3.4 **it is possible to cancel a review round** that has been started, unless a reviewer has completed a review. If a reviewer has declined the review, you must cancel the reviewer before you can cancel the review round. You cannot cancel a review round if a review has been submitted.

![Review stage in 3.4 with decision options including cancelling a review round.](./assets/learning-ojs3.4-cancel-review-round.png)

### Moving to Copyediting

The submission is now ready to be moved to copyediting. To do so, use the blue **Send to Copyediting** button.
Expand Down
6 changes: 4 additions & 2 deletions learning-ojs/en/settings-workflow.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,13 +48,15 @@ Using the links provided, you can change the **Order** of the components \(how t

You can also edit each component by selecting the blue arrow to the left of the component name. This will reveal an Edit link and a Delete link.

![OJS 3.3 component editing menu.](./assets/learning-ojs3.3-jm-settings-workflow-comp-edit.png)
![OJS 3.4 component editing menu.](./assets/learning-ojs3.4-submissions-component.png)

- **Name**: This is the name of the component, as presented to the author.

- **File Type**: Choose how the files associated with this component will be treated and displayed. Anything that is marked as a Dependent file will not be published.
- **File Type**: Choose how the files associated with this component will be treated and displayed. Anything that is marked as a Dependent file will not be published. Anything marked as a Supplementary file will be displayed visually differently than the main article galley(s), will not be shown in the issue's Table of Contents, and will not be counted among article galley downloads.

- **File Metadata**: Select the type of metadata that these files may receive. Document should be selected for the main publication files, such as the downloadable PDF, so that these files inherit their metadata from the publication. Otherwise, choose Supplementary Content for most file types. Artwork is appropriate for files which require distinct credit, caption and licensing metadata.

- **Require with Submission**: Starting in OJS 3.4 it is possible to make a component mandatory for submission. A submitting author will not be able to proceed without uploading at least one file of this type.

- **Key**: Optional short symbol for the component.

Expand Down

0 comments on commit f6e9ee4

Please sign in to comment.