Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2022-03-15T15:04:07Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/822[CoLab] add Select form field to add annotation tags in Hypothes.is2022-03-15T15:04:07ZRyan Dix-Peek[CoLab] add Select form field to add annotation tags in Hypothes.is**Description;** we have the option to customise annotation tags in Hypothes.is. We need to agree on the correct naming convention.
**Current state;**
HYPOTHESIS_PUBLISH_FIELDS="decision:evaluationSummary, reviews:evaluation, submission...**Description;** we have the option to customise annotation tags in Hypothes.is. We need to agree on the correct naming convention.
**Current state;**
HYPOTHESIS_PUBLISH_FIELDS="decision:evaluationSummary, reviews:evaluation, submission.strengths:strengths"
- Publishing `decision` applies the tag "evaluationSummary"
- `reviews`, each with the tag "evaluation" and
- the submission.strengths field with the tag "strengths".
![Screenshot_2022-03-02_at_12.35.44](/uploads/5f9c7651800118614de54efc9ac85ff1/Screenshot_2022-03-02_at_12.35.44.png)CoLab Biophysics v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/594[CoLab] configure manuscripts view2022-06-14T10:29:07ZRyan Dix-Peek[CoLab] configure manuscripts view**Description;** configure manuscripts view as outlined in the acceptance criteria.
Note that `MANUSCRIPTS_TABLE_FIRST_COLUMN_WIDTH` is now unused by the code. It used to be ignored for all `INSTANCE_NAME`s other than `ncrc`, but during...**Description;** configure manuscripts view as outlined in the acceptance criteria.
Note that `MANUSCRIPTS_TABLE_FIRST_COLUMN_WIDTH` is now unused by the code. It used to be ignored for all `INSTANCE_NAME`s other than `ncrc`, but during the work for #582 it appears I stopped using it entirely (I only just realised this!). So we need to just ensure that the columns look alright.
**Acceptance criteria;**
- [ ] Filter labels TBC
- [ ] Roles (Editor, Author and/or Reviewer)
- [ ] First column width (25%) TBC
- [ ] Order of form fields; TBCCoLab Biophysics v1https://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/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/1426Editing citations in the full wax editor2023-09-25T07:49:53ZRyan Dix-PeekEditing citations in the full wax editorThis task impacts the author proofing workflow and is only applicable after the release of the Citation Manager. We assume production workflow will result in parsed citations being displayed in the full wax editor accessed by authors fr...This task impacts the author proofing workflow and is only applicable after the release of the Citation Manager. We assume production workflow will result in parsed citations being displayed in the full wax editor accessed by authors from the `/submission` page.
When accessing the editor, authors should be able to;
- Read parsed citations
- Add a new citation within a paragraph
- Add new citations to a reference list
- Edit existing citations (using the Citation Manager edit modal)
- Delete a citation
For the author-proofing workflow, these changes should be displayed as 'suggested changes' in Wax.Amnet Wax citation packageshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1389[BPSC] Setup publishing to Hypothe.is2023-08-21T09:27:17ZRyan Dix-Peek[BPSC] Setup publishing to Hypothe.is1. Create a new Hypothe.is group
2. input credentials in Configuration>Hypothe.is1. Create a new Hypothe.is group
2. input credentials in Configuration>Hypothe.isSetup Bat Pathogen Spillover Compendium instancehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1480[CoLab] Support for multiple editors to be assigned to a manuscript2024-01-26T11:20:24ZRyan Dix-Peek[CoLab] Support for multiple editors to be assigned to a manuscriptThe purpose of this task is to support a use case, where a Group Manager/Editor wishes to assign more than 3 editors to a manuscript. For a PRC workflow; the Group Manager may wish to assign 5 or more users as editors - these users will ...The purpose of this task is to support a use case, where a Group Manager/Editor wishes to assign more than 3 editors to a manuscript. For a PRC workflow; the Group Manager may wish to assign 5 or more users as editors - these users will discuss who is best suited to act as the handling editor based on domain knowledge and/or other contributing factors. The number of editors may vary.
The brief is to create UI features that support;
1. Assigning multiple editors (think between 5-10 users, but the solution should in theory support an infinite amount).
2. The editors should be assigned from the Control panel>Team page.
3. Editors who are registered listed should be searchable and selected from a list.
4. Editors can removed as required by a Group Manager/Editor (as per current state).
![Screenshot_2023-12-13_at_14.28.07](/uploads/bc614a43b98f7e1ed957bd94b0aa7b09/Screenshot_2023-12-13_at_14.28.07.png)CoLab Biophysics v6https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1479[CoLab] Display form field share settings on submit2023-12-13T08:02:02ZRyan Dix-Peek[CoLab] Display form field share settings on submitThis task allows the editor to see and confirm what data will be shared with the author and/or reviewers when submitting a Decision form.
Solution;
- When clicking on the Decision>Decision>Submit button, editors will be presented with...This task allows the editor to see and confirm what data will be shared with the author and/or reviewers when submitting a Decision form.
Solution;
- When clicking on the Decision>Decision>Submit button, editors will be presented with a modal providing a summary of each form field that will be shared with the author and/or reviewers.
- The editor will have the option to alter the settings from this modal.
- The editor will be able to submit and share data with the respective role recipients when clicking on the submit action displayed in the modal.
UI; [Figma board](https://www.figma.com/file/8XdAAiZTvjXCOC6ZYJ66yt/Kotahi?type=design&node-id=3254%3A8&mode=design&t=7nCnvmn4JRYpqaVU-1)
**Acceptance criteria;**
- [ ] Editors and Group Managers can enable/disable sharing Submission, Review and/or Decision form field data with an author and/or reviewers from the Control panel>Deicsion>Decision>Submit>Submit modal.CoLab Biophysics v6https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1470Add config setting to hide discussion channels2023-12-05T10:53:21ZRyan Dix-PeekAdd config setting to hide discussion channelsThis task aims to support workflows where communication between either 1) authors and the editorial team 2) reviewers and the editorial team and/or 3) the editorial team is not required.
The suggested solution is to use a checkbox conf...This task aims to support workflows where communication between either 1) authors and the editorial team 2) reviewers and the editorial team and/or 3) the editorial team is not required.
The suggested solution is to use a checkbox configuration setting to show/hide;
- Author discussion on the `/submit` and `/decision` pages
- Review discussion on the `/review` page
- Editorial discussion on the `/decision` page
**Acceptance criteria;**
- [ ] Group Manager can select Configuration>Discussion>Discussions accessible to>Authors to display the discussion on the /submit page and `/decision` pages.
- [ ] Group Manager can select Configuration>Discussion>Discussions accessible to>Reviewers to display the discussion on the `/review` page and `/decision` pages. If unchecked, the Editorial discussion still remains visible and accessible to editors on the `/decision` page.
- [ ] Group Manager can select Configuration>Discussion>Discussions accessible to>Editors to display the discussion on the `/decision` page only.CoLab Biophysics v6https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1453Preview email notification templates2024-02-06T07:51:02ZRyan Dix-PeekPreview email notification templatesUsers wish to see the emails they have created before they send/assign to an event/task; 1) to evaluate the layout and 2) to confirm hyperlinks and Handlebar variables and display as intended. An option in the basic wax editor toolbar to...Users wish to see the emails they have created before they send/assign to an event/task; 1) to evaluate the layout and 2) to confirm hyperlinks and Handlebar variables and display as intended. An option in the basic wax editor toolbar to toggle to a 'preview' view.
UI; [[Figma board](https://www.figma.com/file/8XdAAiZTvjXCOC6ZYJ66yt/Kotahi?type=design&node-id=3416-18&mode=design&t=xlnlt8kVeHeYGqm2-0#683625995)]
Suggested solution;
- Toggle action to run preview mode on/off
- In preview mode, all Handlebar variables should display dummy content; TBC
- Incorrect Handlbar syntax should be displayed in red; TBC
![Screenshot_2023-10-26_at_14.55.02](/uploads/611302c0ef1bbc2e175c42f0ee860559/Screenshot_2023-10-26_at_14.55.02.png)Event notificationshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1407[CoLab] Display form field publishing settings & endpoints on Publish action2024-02-21T06:00:29ZRyan Dix-Peek[CoLab] Display form field publishing settings & endpoints on Publish actionThis task allows the editor to see and confirm what data will be shared publicly when publishing from the Control panel>Decision page.
Solution;
- When clicking on the Decision>Decision>Publish button, editors will be presented with a...This task allows the editor to see and confirm what data will be shared publicly when publishing from the Control panel>Decision page.
Solution;
- When clicking on the Decision>Decision>Publish button, editors will be presented with a modal providing a summary of each form field that will be published, and to which endpoint; Webhook, Hypothesis, Flax and/or Crossref.
- The editor will have the option to alter the settings from this modal.
- The editor will be able to publish metadata, manuscripts, reviews and/or decision data when clicking on the submit action displayed in the modal.
UI; TBC
**Acceptance criteria;**
- [ ] Editors and Group Managers can enable/disable publishing Manuscripts, Submission, Review and/or Decision form field data to Flax, Hypothesis, Webhook, Crossref and/or other endpoints from the Control panel>Deicsion>Decision>Submit>Submit modal.
![Screenshot_2023-12-13_at_14.15.31](/uploads/43bdad5cf69a10bda9c3dd43e6c17c4d/Screenshot_2023-12-13_at_14.15.31.png)CoLab Biophysics v6https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1283[CoLab] Events configuration2023-06-29T06:55:28ZRyan Dix-Peek[CoLab] Events configurationAdmins should be able to;
- Add/modify events-related email notification template from Settings>Email
- See a list of triggered event notifications; Configuration>Notifications>Events>_'Event X'_. Each event should have a dropdown menu o...Admins should be able to;
- Add/modify events-related email notification template from Settings>Email
- See a list of triggered event notifications; Configuration>Notifications>Events>_'Event X'_. Each event should have a dropdown menu of all email templates, admin should be able to select a template.
- Admin should be able to select a checkbox to enable/suppress each event notification from; Configuration>Notifications>Events>_'Event X'_.Event notificationshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1191[CoLab] Event notifications2023-10-12T07:30:47ZRyan Dix-Peek[CoLab] Event notifications**Description;** the purpose of this task is to set up generic email notifications that can be configured to send on user actions common to most journal/prc workflows. The events should be available in all instances where a Gmail account...**Description;** the purpose of this task is to set up generic email notifications that can be configured to send on user actions common to most journal/prc workflows. The events should be available in all instances where a Gmail account is set up.
References;
- [Brief](https://docs.google.com/document/d/1yaPcwg-HezL4VoQoN0Tp3zvwTYKNlFDJLGw4R_XB4mk/edit?usp=sharing)
- Generic email templates (TBC)
**Acceptance criteria;**
- [ ] Create and link generic email notification templates to events.
- [ ] Users should be able to 'opt-out' of email communication from their User profile.
- [ ] Add the ability to enable/suppress 'Event Notification' events from the Configuration Manager.
- [ ] Add the ability to assign an email notification template to an event in the Configuration Manager.
- [ ] 'Group manager' role should have access to a record of event notifications sent from Kotahi.Event notificationshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1502Sticky chat2024-03-27T10:15:26ZAdam Hydeadam@coko.foundationSticky chatCurrently we can open and collapse any of the chats in kotahi. However the state is not remembered between sessions or clicking between different pages. We need to preserve the state of the chat so that if a user opens or collapses a cha...Currently we can open and collapse any of the chats in kotahi. However the state is not remembered between sessions or clicking between different pages. We need to preserve the state of the chat so that if a user opens or collapses a chat window that state is preserved if they navigate away and come back to the page. (This should also be the same for the collapsible sidebar)Kotahi Live Contrib to 3.0MRdevTaggMRdevTagghttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1496Crossref plagarism detection (Similarity Check)2023-12-25T01:16:36ZAdam Hydeadam@coko.foundationCrossref plagarism detection (Similarity Check)Kotahi Live Contrib to 3.0https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1494Add beta tags to MVP functions in deployed features2024-02-12T09:53:19ZAdam Hydeadam@coko.foundationAdd beta tags to MVP functions in deployed featuresWe need to have a config 'display beta functionality'. We can then mark some functions/features as beta and when this item is checked in the config, then the features are displayed. I would like to do this with article editing and one mi...We need to have a config 'display beta functionality'. We can then mark some functions/features as beta and when this item is checked in the config, then the features are displayed. I would like to do this with article editing and one minute migrationsKotahi Live Contrib to 3.0Ryan Dix-PeekVukile LangaGiannis Kopanasjkopanas@gmail.comRyan Dix-Peekhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1512Add suggested change styling for tables & images2024-01-25T06:14:08ZRyan Dix-PeekAdd suggested change styling for tables & imagesAmnet Author proofing workflowhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1514MetaData Manager2024-03-27T10:02:33ZAdam Hydeadam@coko.foundationMetaData ManagerWe need Publication MetaData page in the CMS. This should be a new page nested in the CMS tree. In the top part of the page we want 'publication metadata' and list (pulling equivalent metadata from the settings if the items exist eg jou...We need Publication MetaData page in the CMS. This should be a new page nested in the CMS tree. In the top part of the page we want 'publication metadata' and list (pulling equivalent metadata from the settings if the items exist eg journal name):
* title
* description
* ISSN
* logo
* contact
Below this we want a collections manager. In this we would like:
* a button to 'add new collection'
* A button to delete a collection
* with each collection we want the following metadata:
* title
* date of publication
* description
* image
* issue number
each metadata item must be referencable so we can reuse in the CMSv3.1.0Giannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1504Add review invitation to dashboard.2024-03-27T12:01:40ZAdam Hydeadam@coko.foundationAdd review invitation to dashboard.When someone is invited to review the invitation appears only in email. It should also _always_ appear in the reviewer section of the dashboard.
From there the user should be able to click 'accept'When someone is invited to review the invitation appears only in email. It should also _always_ appear in the reviewer section of the dashboard.
From there the user should be able to click 'accept'v3.1.0MRdevTaggMRdevTagghttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1503Dashboard refinements (change names of tabs)2024-03-27T12:15:55ZAdam Hydeadam@coko.foundationDashboard refinements (change names of tabs)* "My Submissions" (keep)
* "To Review" -\> "Review Assignments.
* "Manuscripts I'm Editor of" -\> "Editing Queue"* "My Submissions" (keep)
* "To Review" -\> "Review Assignments.
* "Manuscripts I'm Editor of" -\> "Editing Queue"v3.1.0MRdevTaggMRdevTagg