Add Reviewer Recommendation Manager plugin 1.0.3.0 for OJS 3.4/3.5#513
Open
edersotto wants to merge 1 commit into
Open
Add Reviewer Recommendation Manager plugin 1.0.3.0 for OJS 3.4/3.5#513edersotto wants to merge 1 commit into
edersotto wants to merge 1 commit into
Conversation
Lets a journal rename, reorder and disable the reviewer recommendations while preserving the review history.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new entry for the Reviewer Recommendation Manager plugin. On OJS 3.4/3.5 the six reviewer recommendations are hard-coded; this plugin lets a journal rename them per language, reorder them and disable the ones it does not use, without patching core.
~3.4.0.0and~3.5.0.0Scope, and its relationship with OJS 3.6
I am aware that customizable reviewer recommendations were implemented in core for OJS 3.6 (pkp/pkp-lib#1660). This entry is therefore scoped to 3.4 and 3.5 only, for journals that are still on those lines, and the limitation is stated explicitly in the plugin description and README so nobody installs it expecting it to be needed on 3.6. If you would rather not list a plugin that core supersedes in the next release, I completely understand - feel free to close this.
How it works
reviewerRecommendationOptionstemplate variable on the reviewer form (reviewer/review/step3.tpl) before it renders. The editor view is untouched, so recommendations recorded on past reviews are never hidden or rewritten.Notes
reviewerRecommendationManager/directory withLICENSEat its root; CI files are excluded via.gitattributesand there are no composer/npm dependencies.xmllint --schema ./plugins.xsd ./plugins.xml --noout; the package URL resolves and its MD5 matches.certificationelement included - that is for the maintainers to decide.Maintained by OJSBR (https://ojsbr.com).