Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2023-01-13T08:41:33Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1118[Form builder] Update button should resemble 'action button'2023-01-13T08:41:33ZRyan Dix-Peek[Form builder] Update button should resemble 'action button'As an admin, after editing a form field and clicking on the 'update' button, it's not obvious that my edits have been saved.
The purpose of this task is to update the current update button to resemble the styling of the 'action button'...As an admin, after editing a form field and clicking on the 'update' button, it's not obvious that my edits have been saved.
The purpose of this task is to update the current update button to resemble the styling of the 'action button' applied to the 'Notify' and form submission buttons.
Current state;
![Screenshot_2022-11-08_at_09.45.44](/uploads/dca99fe4e724fc1f5141f0653669a3e7/Screenshot_2022-11-08_at_09.45.44.png)
Notify action;
![Screenshot_2022-11-08_at_09.46.35](/uploads/69770cdbabea58d12345d9ce65607828/Screenshot_2022-11-08_at_09.46.35.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1115Original manuscript populating the resubmitted manuscript box2022-11-04T14:24:55ZBeau HaugenOriginal manuscript populating the resubmitted manuscript boxHello Kotahi,
Evan Beal, the author of manuscript #54 in Aperture Neuro, attempted to resubmit the second version of their manuscript. However, the manuscript text was automatically populated with their original manuscript, instead of a...Hello Kotahi,
Evan Beal, the author of manuscript #54 in Aperture Neuro, attempted to resubmit the second version of their manuscript. However, the manuscript text was automatically populated with their original manuscript, instead of allowing them to submit with their revised manuscript. Not sure what is to be done with this.
Thanks!
Beau.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1114Peer-Review Invitation still sending out Survey Monkey2022-11-07T05:48:14ZBeau HaugenPeer-Review Invitation still sending out Survey MonkeyHello Kotahi,
When a Handling Editor uses their notification template for Aperture Neuro to send out a peer review invitation (for example: Catie Chang Peer-Review Invitation Assignment) it still has the old message with the Survey Monk...Hello Kotahi,
When a Handling Editor uses their notification template for Aperture Neuro to send out a peer review invitation (for example: Catie Chang Peer-Review Invitation Assignment) it still has the old message with the Survey Monkey link.
The Reviewer Invitation Template works just fine.
Thanks!
Beau.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1113[CoLab] Add ability for editor to rescind reviewer invitation2023-12-06T10:45:12ZRyan Dix-Peek[CoLab] Add ability for editor to rescind reviewer invitationCurrently, a reviewer's access to a review page can be revoked by deleting the reviewer from the Control panel>Manage reviewers page. It is not currently possible to revoke a 'reviewer invitation' email notification.
Solution; a 'delet...Currently, a reviewer's access to a review page can be revoked by deleting the reviewer from the Control panel>Manage reviewers page. It is not currently possible to revoke a 'reviewer invitation' email notification.
Solution; a 'delete' action should also be available in the Control panel once the email notification is sent. This feature can be used by the editor to rescind the invitation.
The email notification may have still been sent, but clicking on the accept/decline should not display a notification that access to the review has been revoked.
Current state, control panel does not include a 'delete' (rescind) action;
![Screenshot_2023-01-16_at_12.50.36](/uploads/79004397df4a78f51424222c7cf70bbc/Screenshot_2023-01-16_at_12.50.36.png)
Current state, 'access revoked' error handling display;
![Screenshot_2023-01-16_at_12.53.24](/uploads/a132085f3368918de2b437daa6dac7b6/Screenshot_2023-01-16_at_12.53.24.png)CoLab Biophysics v7https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1109Unused dependencies2022-10-29T22:13:14ZPete StengerUnused dependenciesThe `package.json` contains a lot of packages, and I was curious if all of them were needed. I ran `npx depcheck` which shows that a large number of dependencies are unused by the project.
```
npx: installed 128 in 9.093s
Unused depende...The `package.json` contains a lot of packages, and I was curious if all of them were needed. I ran `npx depcheck` which shows that a large number of dependencies are unused by the project.
```
npx: installed 128 in 9.093s
Unused dependencies
* @babel/helper-define-map
* @pubsweet/job-xsweet --used
* @pubsweet/model-user --used
* apollo-link-context
* apollo-link-schema
* apollo-server-express
* aws-sdk
* babel-runtime
* client-zip
* compression
* cookie-parser
* font-awesome
* got
* graphql-middleware
* graphql-tools
* helmet
* http-status-codes
* inversify-inject-decorators
* jimp
* loadable-components
* memory-cache
* morgan
* net
* node-schedule
* react-dropdown
* react-html-parser
* react-js-pagination
* react-markdown
* waait
* wax-prosemirror-plugins
* wax-prosemirror-schema
* ws
* xpub-with-context
Unused devDependencies
* @babel/plugin-proposal-export-namespace-from
* @babel/plugin-proposal-function-sent
* @babel/plugin-proposal-json-strings
* @babel/plugin-proposal-numeric-separator
* @babel/plugin-proposal-throw-expressions
* @babel/plugin-syntax-dynamic-import
* @babel/plugin-syntax-import-meta
* babel-core
* babel-jest
* babel-preset-minify
* clean-webpack-plugin
* jest
* joi-browser
* node-wait-for-it
* nodemon
* react-router-redux
* sass-loader
* speed-measure-webpack-plugin
* string-replace-loader
* uglifyjs-webpack-plugin
* webpack-bundle-analyzer
* webpack-cli
* webpack-dev-middleware
* webpack-dev-server
* webpack-hot-middleware
Missing dependencies
* babel-eslint: ./.eslintrc.js
* eslint-plugin-jest: ./.eslintrc.js
* eslint-plugin-prettier: ./.eslintrc.js
* eslint-config-airbnb: ./.eslintrc.js
* eslint-config-standard: ./.eslintrc.js
* eslint-config-standard-react: ./.eslintrc.js
* eslint-plugin-cypress: ./.eslintrc.js
* eslint-config-prettier: ./.eslintrc.js
* eslint-plugin-import: ./.eslintrc.js
* eslint-plugin-react: ./.eslintrc.js
* eslint-plugin-jsx-a11y: ./.eslintrc.js
* eslint-plugin-node: ./.eslintrc.js
* eslint-plugin-promise: ./.eslintrc.js
* eslint-plugin-standard: ./.eslintrc.js
* cz-customizable: ./package.json
* husky: ./package.json
```https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1107Invite Reviewer Modal2022-12-04T19:41:47ZZora ZhangInvite Reviewer Modal## Description
In the "Team" tab, a modal popup should appear when an editor clicks on "Invite Reviewer" to invite a user to review a certain manuscript. The modal will display detailed user information, it will also allow user to toggle...## Description
In the "Team" tab, a modal popup should appear when an editor clicks on "Invite Reviewer" to invite a user to review a certain manuscript. The modal will display detailed user information, it will also allow user to toggle:
- Whether or not to share the review content with author (aka the "shared" toggle)
- Whether or not to send an email notification to the invited user (aka the "send email notification" toggle)
<img src="/uploads/2198ccca224fec693261f9115f59eab0/image.png" alt="drawing" width="300"/>
## Notes
- For email notification, there are multiple templates in the codebase, but we are only concerned about `Reviewer invitation` template. See issue #1007 as well.
- Refer to the general modal component (see #1108).
- Checkbox Defaults:
- "Shared" should be unchecked
- "Send Email Notification" should be checked
## Learning objectives
- React
- React Modal
- Email Notification
## Useful links
- Designs: https://www.figma.com/file/oS6QzvBfDvlqMRQ6aaRRjf/Kotahi-Draft?node-id=621%3A3550
<!--
Template sourced from https://github.com/hack4impact-uiuc/falling-fruit
Shoutout to the wonderful FF team!
-->Aaron AlexanderAaron Alexanderhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1103[eLife] Use a configuration setting to inlcude/remove pages form the control ...2022-10-27T12:45:01ZRyan Dix-Peek[eLife] Use a configuration setting to inlcude/remove pages form the control panel**Description;** instances using the `elife` archetype make use of the Evaluation page to capture and publish reviews. The control panel pages; workflow, manuscript text and metadata are not visible to the end user. The purpose of this t...**Description;** instances using the `elife` archetype make use of the Evaluation page to capture and publish reviews. The control panel pages; workflow, manuscript text and metadata are not visible to the end user. The purpose of this task would be to allow an instance to allow pages to be visible as required using a configuration variable in the .env file.
For example; the elife team could benefit from features such as assigning a reviewer or using creating a task list. Currently, these features are inaccessible because the control panel is hidden in elife archetype.eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1097Retain sorting when accessing the Control panel from Manuscripts page2023-03-23T23:54:12ZRyan Dix-PeekRetain sorting when accessing the Control panel from Manuscripts page**Issue description;** currently, from the Manuscripts page as admin can sort a column, however, if the user accesses a manuscript (Manuscripts page>Control panel) and navigates back using their browser 'click to go back' action - the so...**Issue description;** currently, from the Manuscripts page as admin can sort a column, however, if the user accesses a manuscript (Manuscripts page>Control panel) and navigates back using their browser 'click to go back' action - the sorting is no longer applied. Sorting should be applied as per the user action or until the page is refreshed.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1095[CoLab] Submitting a new version should prevent automated import of the same ...2023-12-06T10:45:19ZRyan Dix-Peek[CoLab] Submitting a new version should prevent automated import of the same preprint from bioRxiv**Description;** currently, we prevent the importing of duplicates from bioRxiv based on the `submission.link` and from Semantic Scholar based on `submission.doi`.
A key outcome of the Colab peer review cycle is to ensure an author sub...**Description;** currently, we prevent the importing of duplicates from bioRxiv based on the `submission.link` and from Semantic Scholar based on `submission.doi`.
A key outcome of the Colab peer review cycle is to ensure an author submits an updated version of their manuscripts to a preprint server. The purpose of this task is to ensure that we do not automatically import the updated version of the preprint (e.g. https://www.biorxiv.org/content/10.1101/2021.01.10.426076v2) into Kotahi if the preprint has been submitted as part of the initial version/1st review cycle.
Suggested solution; preprionts imported automatically are validated against against `submission.link` field captured in the database. A validation error should display for all `submission.url` fields where a duplication is present in the system - this will allow an Editor to manually varify and archive the duplicate.CoLab Biophysics v7https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1092Show "success" message on form field save2022-11-01T21:47:07ZAndrew LesterShow "success" message on form field saveCurrently, saving a form field with the "Update form" button doesn't let the user know the save was successful. We want to use a similar button to the submit button on the Control Panel page .
![image](/uploads/72cf4e29bf8d244265d9e8c62...Currently, saving a form field with the "Update form" button doesn't let the user know the save was successful. We want to use a similar button to the submit button on the Control Panel page .
![image](/uploads/72cf4e29bf8d244265d9e8c622bdf6ce/image.png)Hack4Impact | MiscAnthony Cruz MacedoAnthony Cruz Macedohttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1085Ensure anonymous reviewer ids are hidden when 'hide reviewer' name' setting i...2022-10-17T08:30:39ZRyan Dix-PeekEnsure anonymous reviewer ids are hidden when 'hide reviewer' name' setting is appliedhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1084Edit Date field uneditable2022-10-19T12:48:14ZBen WhitmoreEdit Date field uneditableUsing aperture workflow, I tried to create a new manuscript (submit URL rather than upload manuscript). All fields in the submission form were editable except "Edit Date". When I clicked on the field its border was highlighted to show fo...Using aperture workflow, I tried to create a new manuscript (submit URL rather than upload manuscript). All fields in the submission form were editable except "Edit Date". When I clicked on the field its border was highlighted to show focus, but no cursor appeared for text entry, and typing did nothing.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1070[Production editor] Add the ability to apply inline callouts in a random order2022-10-11T12:29:15ZRyan Dix-Peek[Production editor] Add the ability to apply inline callouts in a random orderTo be specced -
Uses would like to apply footnote references inline in random order. Wax footnote callout logic only supports chronological ordering at this stage. This needs to be discussed as to how best to do this.To be specced -
Uses would like to apply footnote references inline in random order. Wax footnote callout logic only supports chronological ordering at this stage. This needs to be discussed as to how best to do this.Amnet Production Editor v2https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1067[CoLab] Validate DOIs submitted manually2023-12-06T10:45:26ZRyan Dix-Peek[CoLab] Validate DOIs submitted manually**Description;** For the `colab` archetype configuration; Manuscripts can be imported automatically or submitted manually. We have a use case where authors, editors and or curators may submit a manuscript manually for review. This submis...**Description;** For the `colab` archetype configuration; Manuscripts can be imported automatically or submitted manually. We have a use case where authors, editors and or curators may submit a manuscript manually for review. This submission may already have been imported automatically into kotahi - we need to account for this duplicate in the system, as the manuscript may have already been considered for review, reviewed and/or rejected.
The most common identifier is the DOI. A suggestion is to validate the DOI captured against DOIs currently in the Manuscripts page or archived in the database.
We could display an alert at the form field level; 'Duplicate of manuscript number 1015' or 'Duplicate of manuscript number 1015 (ARCHIVED)'
![Screenshot_2022-10-10_at_14.32.08](/uploads/bfa23908dd1372784d64acecdf5e391b/Screenshot_2022-10-10_at_14.32.08.png)CoLab Biophysics v7https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1066[CoLab] 'Select all' applied to all objects on the Manuscripts2022-10-10T09:21:19ZRyan Dix-Peek[CoLab] 'Select all' applied to all objects on the Manuscripts**Description;** the purpose of this task is to improve the usability of the bulk select action for Curators on the Manuscripts page, and to be more efficient with the use of page real estate in consideration of additional features (acti...**Description;** the purpose of this task is to improve the usability of the bulk select action for Curators on the Manuscripts page, and to be more efficient with the use of page real estate in consideration of additional features (actions) that may be applied in the near future ( for example; a 'move' action to move manuscripts between groups in a multi-tenant instance).
Currently, there are two ways to archive a manuscript 1) select all and Archive (top of page) and 2) manually archive (action per object in the manuscripts table). The purpose of this task is to simply the action to select and delete an object from the manuscripts table.
**Acceptance criteria;**
- [ ] Remove the 'Archive' action at the object level from the controls in the manuscripts table.
- [ ] Allow all objects in the manuscripts table to be selected/deselected individually or bulk selected and archived.
- [ ] Manuscripts with the 'Select' label applied can also be selected individually, or bulk selected and archived.
![Screenshot_2022-10-10_at_09.50.17](/uploads/9dacdcf5ff4b0016250aaed4d50ef59f/Screenshot_2022-10-10_at_09.50.17.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1056Register reviews for manuscripts in Crossref in article publishing configuration2022-11-01T21:34:52ZAndrew LesterRegister reviews for manuscripts in Crossref in article publishing configuration_This issue has been edited since Thursday's dev night_
We need to register *all* reviews for manuscripts in Crossref when Kotahi is in the "reviews" publishing configuration. *All* reviews means both reviews specified in the submission..._This issue has been edited since Thursday's dev night_
We need to register *all* reviews for manuscripts in Crossref when Kotahi is in the "reviews" publishing configuration. *All* reviews means both reviews specified in the submission form (review1, review2, etc.) AND reviews attached to the manuscript but submitted through the review form. The latter type of review is accessible in a manuscript object's `reviews` property.
You will need to edit the `publishReviewsToCrossref` function to include the review-form submitted reviews in the larger JSON object that represents all peer-reviews being registered. The DOI suffix for these reviews is complicated. Here's an idea:
The suffix for the reviews established using submission properties (review1, review2, etc.) is {manuscript.id}/{reviewNumber}. Please change this to be {decisionFormDOISuffix}/{reviewNumber}
The suffix for reviews established using the review form (not yet implemented) should be {decisionFormDOISuffix}/{reviewIndexInReviewsList + 4}. This way, these reviews start after the ones from the submission form.Hack4Impact | MiscAaron AlexanderPete StengerAaron Alexanderhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1053[CoLab] Refresh and Import actions should be combined and configurable2022-12-14T08:18:49ZRyan Dix-Peek[CoLab] Refresh and Import actions should be combined and configurablehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1046Link tool is not easily accessible within the form field viewport2022-10-10T07:57:59ZRyan Dix-PeekLink tool is not easily accessible within the form field viewportAdd a link using the Wax link tool in an `AbstractEditor` the modal to enter link text is difficult to use. The link pop-up should overlap the viewport and not the other way around.
![Screenshot_2022-09-27_at_10.52.23](/uploads/a717f7c...Add a link using the Wax link tool in an `AbstractEditor` the modal to enter link text is difficult to use. The link pop-up should overlap the viewport and not the other way around.
![Screenshot_2022-09-27_at_10.52.23](/uploads/a717f7c3d2f77557efefd197b6272e4b/Screenshot_2022-09-27_at_10.52.23.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1038[CoLab] Apply a label to manual submissions2022-10-04T05:16:55ZRyan Dix-Peek[CoLab] Apply a label to manual submissions**Description;** the purpose of this to avoid a situation where a manual (new) submission is mistakingly deleted (archived) on a bulk delete action.
**Acceptance criteria;**
- [ ] When a manuscripts is 'Selected' in the Manuscripts ta...**Description;** the purpose of this to avoid a situation where a manual (new) submission is mistakingly deleted (archived) on a bulk delete action.
**Acceptance criteria;**
- [ ] When a manuscripts is 'Selected' in the Manuscripts table the `selectedforConsideration` label should be applied and not the `readyToEvaluate` as per current state.
- [ ] Upon creation of a +new submission the `selectedforConsideration` label should be applied i.e. the manuscript is automatically 'Selected'.
- [ ] This should be applied to all preprint workflows utilising the 'refresh' or 'automated' import functionality; `colab`.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1033(Manuscript search) Rank all submission form field data2022-09-20T11:57:24ZRyan Dix-Peek(Manuscript search) Rank all submission form field data**Description;** the purpose of this task is to ensure that submission form data is ranked when using keyword search.**Description;** the purpose of this task is to ensure that submission form data is ranked when using keyword search.