Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2024-03-20T13:14:58Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1525[BPSC] Update import query2024-03-20T13:14:58ZRyan Dix-Peek[BPSC] Update import queryUpdate the search query on targeting the BPSC group only, on the NCRC instance; https://app.ncrc.kotahi.cloud/bpsc/
Updated query; [JHU_Bat_Spillover_Search_Query_v3_020924.docx](/uploads/56912d1c1212a8eb55425836830bbc7c/JHU_Bat_Spillov...Update the search query on targeting the BPSC group only, on the NCRC instance; https://app.ncrc.kotahi.cloud/bpsc/
Updated query; [JHU_Bat_Spillover_Search_Query_v3_020924.docx](/uploads/56912d1c1212a8eb55425836830bbc7c/JHU_Bat_Spillover_Search_Query_v3_020924.docx)
Request from the client; to ensure that updating the query has no impact on the existing data, manuscript selection or archived manuscripts.BPSC Collaborative form field typePankaj KandpalPankaj Kandpalhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1523Unknown default Flax logo is displaying2024-02-13T12:22:04ZRyan Dix-PeekUnknown default Flax logo is displayingDefault source logo; https://kotahidev.cloud68.co/kotahi/assets/images/logo.png seems to be set, and overrides the logo set in CMS>Layout>Brand logo. Adding a new 'Brand logo' is not saved after 'publishing data' or leaving the page.
- ...Default source logo; https://kotahidev.cloud68.co/kotahi/assets/images/logo.png seems to be set, and overrides the logo set in CMS>Layout>Brand logo. Adding a new 'Brand logo' is not saved after 'publishing data' or leaving the page.
- An image file should be saved (attached) to the 'Brand logo' field after successful upload.
- No logo should be displayed if there is no file attached to the 'Brand logo' field.
- If an image file has been uploaded successfully this image should be displayed as the 'Brand logo' in Flax header.
![Screenshot_2024-02-09_at_13.56.58](/uploads/a1f731b555eede0a5bd0c82abc99a25e/Screenshot_2024-02-09_at_13.56.58.png)
![Screenshot_2024-02-09_at_13.56.32](/uploads/466543647d4097a60def37e11c5ecb06/Screenshot_2024-02-09_at_13.56.32.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1515[eLife] Slow queries and users intermittently being logged out2024-02-15T03:51:11ZBen Whitmore[eLife] Slow queries and users intermittently being logged outWe have reports from eLife that their instance is sluggish and users are every now and then being redirected to the login page and forced to log in again (earlier than 24 hours after their previous login!).
Examining the logs, there are...We have reports from eLife that their instance is sluggish and users are every now and then being redirected to the login page and forced to log in again (earlier than 24 hours after their previous login!).
Examining the logs, there are a lot of Knex connection timeout errors, indicating possible heavy loads on the database. Knex timeout errors could conceivably cause users to be logged out if Kotahi is unable to obtain session information from the database.Ben WhitmoreBen Whitmorehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1513Unable to download PDFs2024-02-28T11:49:34ZCloud68 Support teamUnable to download PDFs<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
When clicking the Download button and then selecting PDF, the used should be redirected to a PDF file.
<!-- Required. Tell us what should...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
When clicking the Download button and then selecting PDF, the used should be redirected to a PDF file.
<!-- Required. Tell us what should happen -->
## Current behaviour
A pop up saying "something went wrong"
<!-- Required. Tell us what happens instead of the expected behaviour -->
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. Create a manuscript
2. Complete the needed fields
3. Do not add an publish date.
4. Submit the manuscript
5. Click production
6. Try to download a PDF
7. it will fail
## Environment
<!-- Required. Provide relevant information such as browser name and version, PC or Mac use, internet speed, etc.]-->
## Possible solution
From the container logs it looks like the datePublish is needed in order to generate the PDF.
```
Error: Unable to call `article["submission"]["datePublished"]["split"]`, which is undefined or falsey name=Template render error
info: ::ffff:172.18.0.1 - - [26/Jan/2024:08:52:38 +0000] "POST /graphql HTTP/1.1" 200 134 "https://kotahi.url/kotahi/versions/manuscript/production" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0"
```
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1510malformed date can crash PDF generation2024-01-25T03:45:14ZDan Viselmalformed date can crash PDF generation`server/pdfexport/pdfTemplates/article.njk` contains this code:
```
<span class="citation">{{ article.submission.datePublished.split(".")[2] }}<span></span></span>
```
If `datePublished` is not coming in as a string with two "."s in it, ...`server/pdfexport/pdfTemplates/article.njk` contains this code:
```
<span class="citation">{{ article.submission.datePublished.split(".")[2] }}<span></span></span>
```
If `datePublished` is not coming in as a string with two "."s in it, this will fail; PDF generation fails with an error. There should be a fallback here.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1508Save and display each author feedback element2024-03-11T07:04:27ZRyan Dix-PeekSave and display each author feedback elementEach round of author proofing (author feedback form) should be saved against the version. Each feedback component should be saved, and displayed in the Production editor (read-only).Each round of author proofing (author feedback form) should be saved against the version. Each feedback component should be saved, and displayed in the Production editor (read-only).v3.1.0Vignesh DevendranVignesh Devendranhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1507The submit button will not "submit" the new manuscript2024-01-29T10:57:42ZCloud68 Support teamThe submit button will not "submit" the new manuscript<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
there should be an indicator that the manuscript has been submited or failed.
<!-- Required. Tell us what should happen -->
## Current b...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
there should be an indicator that the manuscript has been submited or failed.
<!-- Required. Tell us what should happen -->
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behaviour -->
After creating a new manuscript and uploading a pdf the submit button on the pop-up will not perform any action.
The following error is shown on the console logs:
```
Uncaught (in promise) Error: Something went wrong! Please contact your administrator
t app.9c27b569.js:68312
next app.9c27b569.js:221915
v app.9c27b569.js:251336
b app.9c27b569.js:251336
value app.9c27b569.js:251336
$/< app.9c27b569.js:4191
$ app.9c27b569.js:4191
next app.9c27b569.js:4191
v app.9c27b569.js:251336
b app.9c27b569.js:251336
value app.9c27b569.js:251336
v app.9c27b569.js:251336
b app.9c27b569.js:251336
value app.9c27b569.js:251336
v app.9c27b569.js:251336
b app.9c27b569.js:251336
value app.9c27b569.js:251336
exports app.9c27b569.js:377358
app.9c27b569.js:68312
```
The following error is shown on the console logs:
```
error: update "manuscripts" set "type" = $1, "id" = $2, "created" = $3, "updated" = $4, "parent_id" = $5, "submitter_id" = $6, "status" = $7, "decision" = $8, "authors" = $9, "meta" = $10, "submission" = $11, "published" = $12, "evaluations_hypothesis_map" = $13, "is_imported" = $14, "import_source" = $15, "import_source_server" = $16, "short_id" = $17, "submitted_date" = $18, "is_hidden" = $19, "form_fields_to_publish" = $20, "searchable_text" = $21, "doi" = $22, "group_id" = $23 where "manuscripts"."id" = $24 - invalid input syntax for type json name=DataError, length=230, name=error, severity=ERROR, code=22P02, detail=Token "test" is invalid., hint=undefined, position=undefined, internalPosition=undefined, internalQuery=undefined, where=JSON data, line 1: test...
PL/pgSQL function manuscripts_searchable_text_trigger() line 15 at assignment, schema=undefined, table=undefined, column=undefined, dataType=undefined, constraint=undefined, file=json.c, line=1269, routine=report_invalid_token, originalStack=error: update "manuscripts" set "type" = $1, "id" = $2, "created" = $3, "updated" = $4, "parent_id" = $5, "submitter_id" = $6, "status" = $7, "decision" = $8, "authors" = $9, "meta" = $10, "submission" = $11, "published" = $12, "evaluations_hypothesis_map" = $13, "is_imported" = $14, "import_source" = $15, "import_source_server" = $16, "short_id" = $17, "submitted_date" = $18, "is_hidden" = $19, "form_fields_to_publish" = $20, "searchable_text" = $21, "doi" = $22, "group_id" = $23 where "manuscripts"."id" = $24 - invalid input syntax for type json
at Parser.parseErrorMessage (/home/node/app/node_modules/pg-protocol/dist/parser.js:287:98)
at Parser.handlePacket (/home/node/app/node_modules/pg-protocol/dist/parser.js:126:29)
at Parser.parse (/home/node/app/node_modules/pg-protocol/dist/parser.js:39:38)
at Socket.<anonymous> (/home/node/app/node_modules/pg-protocol/dist/index.js:11:42)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23), client=postgres
info: ::ffff:172.18.0.1 - - [18/Jan/2024:13:28:59 +0000] "POST /graphql HTTP/1.1" 200 117 "https://url/group/versions/2c330264-0cf5-4ebe-8a78-e9be52a70cb8/submit" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0"
error: update "manuscripts" set "type" = $1, "id" = $2, "created" = $3, "updated" = $4, "parent_id" = $5, "submitter_id" = $6, "status" = $7, "decision" = $8, "authors" = $9, "meta" = $10, "submission" = $11, "published" = $12, "evaluations_hypothesis_map" = $13, "is_imported" = $14, "import_source" = $15, "import_source_server" = $16, "short_id" = $17, "submitted_date" = $18, "is_hidden" = $19, "form_fields_to_publish" = $20, "searchable_text" = $21, "doi" = $22, "group_id" = $23 where "manuscripts"."id" = $24 - invalid input syntax for type json name=DataError, length=230, name=error, severity=ERROR, code=22P02, detail=Token "test" is invalid., hint=undefined, position=undefined, internalPosition=undefined, internalQuery=undefined, where=JSON data, line 1: test...
PL/pgSQL function manuscripts_searchable_text_trigger() line 15 at assignment, schema=undefined, table=undefined, column=undefined, dataType=undefined, constraint=undefined, file=json.c, line=1269, routine=report_invalid_token, originalStack=error: update "manuscripts" set "type" = $1, "id" = $2, "created" = $3, "updated" = $4, "parent_id" = $5, "submitter_id" = $6, "status" = $7, "decision" = $8, "authors" = $9, "meta" = $10, "submission" = $11, "published" = $12, "evaluations_hypothesis_map" = $13, "is_imported" = $14, "import_source" = $15, "import_source_server" = $16, "short_id" = $17, "submitted_date" = $18, "is_hidden" = $19, "form_fields_to_publish" = $20, "searchable_text" = $21, "doi" = $22, "group_id" = $23 where "manuscripts"."id" = $24 - invalid input syntax for type json
at Parser.parseErrorMessage (/home/node/app/node_modules/pg-protocol/dist/parser.js:287:98)
at Parser.handlePacket (/home/node/app/node_modules/pg-protocol/dist/parser.js:126:29)
at Parser.parse (/home/node/app/node_modules/pg-protocol/dist/parser.js:39:38)
at Socket.<anonymous> (/home/node/app/node_modules/pg-protocol/dist/index.js:11:42)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23), client=postgres
info: ::ffff:172.18.0.1 - - [18/Jan/2024:13:28:59 +0000] "POST /graphql HTTP/1.1" 200 117 "https://url/group/versions/2c330264-0cf5-4ebe-8a78-e9be52a70cb8/submit" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0"
```
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. create a manuscript
2. upload a pdf
3. add the needed info on the fields
4. Click submit
## Environment
<!-- Required. Provide relevant information such as browser name and version, PC or Mac use, internet speed, etc.]-->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Dan ViselDan Viselhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1501Users can access pages of a manuscript, without being assigned a role2024-02-13T11:47:31ZSidorela UkuUsers can access pages of a manuscript, without being assigned a role<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
A user (not admin/group manager role) should only be able to see manuscripts they are authors, reviewers or editors of. The manuscripts ...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
A user (not admin/group manager role) should only be able to see manuscripts they are authors, reviewers or editors of. The manuscripts a user should be able to access should also be listed in the main dashboard of their submissions/to review/editor of.
## Current behaviour
A user can access any manuscript page, if given a url for it, without any role assigned.
## Steps to reproduce
1. Login as an admin (any other user could be valid for the test case)
2. Create a new manuscript
3. The new url of the manuscript will be similar to this: (https://nbdt.cloud68.co/kotahi/versions/05634472-c8c9-45a9-b201-d5a8ce4b8a5b/submit). Copy that.
4. On a new browser login as a normal user.
5. Paste on the browser the url from point 3.
6. You are able to access the submission page, also by changing the last part /submit to /decision and /review, you can access the other pages.
This was tested on nbdt test site and also in aperture test site. The only difference in case of aperture the /decision page can't be accessed.
## Environment
Firefox and Brave browsers.
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
<!-- After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Ben WhitmoreBen Whitmorehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1499[BPSC] Repeat imports issue2024-02-21T10:19:59ZRyan Dix-Peek[BPSC] Repeat imports issueThe following preprints are being imported daily. The manuscripts are repeat imports, and have already been triaged - these manuscripts should not be imported daily.
**List of repeated preprints imported daily;**
1. Exploring Spatial-T...The following preprints are being imported daily. The manuscripts are repeat imports, and have already been triaged - these manuscripts should not be imported daily.
**List of repeated preprints imported daily;**
1. Exploring Spatial-Temporal Variations of Public Discourse on Social Media: A Case Study on the First Wave of the Coronavirus Pandemic in Italy
2. Detecting Changes in the Transmission Rate of a Stochastic Epidemic Model
3. Weekly sequential Bayesian updating improves prediction of deaths at an early epidemic stage
4. An open debate on SARS-CoV-2's proximal origin is long overdue
5. In silico comparison of spike protein-ACE2 binding affinities across species; significance for the possible origin of the SARS-CoV-2 virus
6. A Time Delay Dynamic System with External Source for the Local Outbreak of 2019-nCoV
7. A Robust Stochastic Method of Estimating the Transmission Potential of 2019-nCoV
8. Structural modeling of 2019-novel coronavirus (nCoV) spike protein reveals a proteolytically-sensitive activation loop as a distinguishing feature compared to SARS-CoV and related SARS-like coronaviruses
What I noticed;
- None of the preprints above have DOIs. But if you look at an example e.g. '[Weekly sequential Bayesian updating improves prediction of deaths at an early epidemic stage](https://arxiv.org/abs/2104.01133)' - there is a DOI; doi.org/10.48550/arXiv.2104.01133. We should be populating `submisson.doi` with this DOI.
- My understanding is that we use the data in `submission.doi` filed to validate if a manuscript has previously been imported, so without this data, we'll get repeated imports of the same manuscripts. Is this correct?
- None of the `submission.link` fields are populated.
- These manuscripts are all from the arXiv server, so perhaps this is an issue with how we pull data from their API.
![Screenshot_2024-01-05_at_3.50.53_PM](/uploads/7c41f1e87404df5bd95f6491cd8cd3ef/Screenshot_2024-01-05_at_3.50.53_PM.png)BPSC Collaborative form field typePankaj KandpalPankaj Kandpalhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1498Minimise sidebar2024-03-27T10:01:40ZAdam Hydeadam@coko.foundationMinimise sidebarThe left sidebar occupies alot of room. We could maximise space by adding a 'minimise funciton'. THe functionality in gitlab itself looks good to me and we should emulate this. Click on the icon that looks like this:
![Screenshot from 2...The left sidebar occupies alot of room. We could maximise space by adding a 'minimise funciton'. THe functionality in gitlab itself looks good to me and we should emulate this. Click on the icon that looks like this:
![Screenshot from 2024-01-09 23-31-26.png](/uploads/ae7086c7b65b8035f7fc10250acfbba7/Screenshot_from_2024-01-09_23-31-26.png)
the behaviour is in 3 parts:
1. clicking makes the sidebar dissapeear
2. hover to the left brings the sidebar back so you can choose a sidebar menu item, then mousing out it re-minimisies
3. clicking on the same icon after doing (2) and it sets the sidebar back to always visiblev3.1.0MRdevTaggMRdevTagghttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1492Add config setting to enable/disable author-proofing workflow2024-03-11T07:25:10ZRyan Dix-PeekAdd config setting to enable/disable author-proofing workflowThe purpose of this task is to add a configuration setting to enable the Author proofing workflow control from appearing on the Dashboard>My submission page, Control>Team and in the Production editor.
**Acceptance criteria;**
- [ ] Add ...The purpose of this task is to add a configuration setting to enable the Author proofing workflow control from appearing on the Dashboard>My submission page, Control>Team and in the Production editor.
**Acceptance criteria;**
- [ ] Add the checkbox setting to the Configuration>Workflow>Control>'Allow authors to participate in proofreading rounds'.
- [ ] The configuration setting should be enabled as a default for the `journal` archetype only.
![Screenshot_2024-01-25_at_07.51.49](/uploads/8792f02536c900c38d6875c9ecb82357/Screenshot_2024-01-25_at_07.51.49.png)Amnet Author proofing workflowVignesh DevendranVignesh Devendranhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1489[BPSC] Export manuscript data2024-02-13T11:43:54ZRyan Dix-Peek[BPSC] Export manuscript data1. Configuration option to download Submission, Review and Decision data as CSV or JSON file.
1. A UI control accessible by editors and group managers: either another export option added to the production page export button, or an action...1. Configuration option to download Submission, Review and Decision data as CSV or JSON file.
1. A UI control accessible by editors and group managers: either another export option added to the production page export button, or an action added to the manuscripts table. The downloaded JSON would not be redacted (would contain confidential fields, reviewer names, etc)
JSON is best suited, as CSV isn’t good at representing nested data (such as author data) or variable-length data (such as variable number of reviews, variable number of authors etc.)BPSC Collaborative form field typePankaj KandpalPankaj Kandpalhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1487[BPSC] Import suggested manuscripts using Semantic Scholar2024-03-12T08:35:22ZRyan Dix-Peek[BPSC] Import suggested manuscripts using Semantic Scholar1. The solution should only be implemented on the `prc` archetype.
2. Move the enable/disable Semantic Scholar .env variable into the config manager. This should be a checkbox setting; Conguration>Workflow>Semantic Scholar>Import preprin...1. The solution should only be implemented on the `prc` archetype.
2. Move the enable/disable Semantic Scholar .env variable into the config manager. This should be a checkbox setting; Conguration>Workflow>Semantic Scholar>Import preprints using Semantic Scholar. Also move, 'Import manuscripts from Sematic Scholar no older than ‘x’ number of days' field to display if Semantic Scholar is enabled.
1. Add config field allowing Group Managers to (multi) select servers from a list; https://www.semanticscholar.org/about/publishersBPSC Collaborative form field typePankaj KandpalPankaj Kandpalhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1485[CMS] Article editor2024-03-07T05:55:10ZRyan Dix-Peek[CMS] Article editor1. Add Article Template under CmsPage Menu
1. Add css and article to layout Query for Flax to get the content of the Template
1. Improve Upload Manager with Tags and fileType. In order for this to work and build the cms Article based on ...1. Add Article Template under CmsPage Menu
1. Add css and article to layout Query for Flax to get the content of the Template
1. Improve Upload Manager with Tags and fileType. In order for this to work and build the cms Article based on the Template we need to update the version of the flax on Docker compose . But we havent publish the new version yet.v3.1.0Giannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1482[CMS] Unable to add insert images into new Pages2024-02-13T12:23:27ZRyan Dix-Peek[CMS] Unable to add insert images into new PagesAs a Group Manager, I am unable to insert a new image into a Page using the Asset Manager. I'm unable to access, select and/or upload new image files. I can insert images into existing Pages.
>This behaviour is happening only if you ha...As a Group Manager, I am unable to insert a new image into a Page using the Asset Manager. I'm unable to access, select and/or upload new image files. I can insert images into existing Pages.
>This behaviour is happening only if you have not saved CMS page form, as the asset manager requires an `ID` for the image and record to be linked.
![Screenshot_2023-12-20_at_10.25.43](/uploads/7bbc648c80fef42ba6b7fb26d4f9fd18/Screenshot_2023-12-20_at_10.25.43.png)Vignesh DevendranDan ViselVignesh Devendranhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1481[ejpimport] Create link from DOI2024-03-20T08:32:53ZRyan Dix-Peek[ejpimport] Create link from DOICurrently, we import the DOI only; 10.1101/2023.08.28.555217
A link needs to be structured from this data captured in the `submission.doi` field e.g. https://doi.org/10.1101/2023.08.28.555217 needs to be created from the DOI (10.1101/20...Currently, we import the DOI only; 10.1101/2023.08.28.555217
A link needs to be structured from this data captured in the `submission.doi` field e.g. https://doi.org/10.1101/2023.08.28.555217 needs to be created from the DOI (10.1101/2023.04.17.537164).DocMaps pluginAlexandros GeorgantasAlexandros Georgantashttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1478[ejpimport] Order on publishing to retained on publish action2024-03-20T08:32:57ZRyan Dix-Peek[ejpimport] Order on publishing to retained on publish actionThe order of review, assessment and author response data is important to the elife editorial team. This data is published via Hypothesis, which reorders the data for display in bioRxiv>TRip. Only if field; Include when sharing or publish...The order of review, assessment and author response data is important to the elife editorial team. This data is published via Hypothesis, which reorders the data for display in bioRxiv>TRip. Only if field; Include when sharing or publishing? = 'Always' or 'Ad hoc' the following order be adhered to;
1. Assessment (Decision form field)
1. Review 1 (Review form field)
1. Review 2 (Review form field)
1. Review 3 (Review form field)
1. Author response (Submission form field)
When publishing;
- The order of fields within the `Decision` or `Submission` forms should be retained where there are multiple fields set to be published.
- Order reviews based on the `Review` title e.g. 'Review 1' appears at the top, in descending order.
The order is reversed when data is displayed as an annotation in Hypothesis. Configuration>Publushin>Hypotheis>'Reverse the order of Submission/Decision form fields published to Hypothesis' setting controls the reverse ordering.DocMaps pluginPankaj KandpalPankaj Kandpalhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1473Refactor access to author-proofing feedback2024-03-11T11:28:13ZRyan Dix-PeekRefactor access to author-proofing feedbackCurrently, the author-proofing workflow allows authors to capture feedback in the Production editor and view the submitted feedback (read-only) from the Feedback tab on the `/submit` page. The editor can access this feedback from the Fee...Currently, the author-proofing workflow allows authors to capture feedback in the Production editor and view the submitted feedback (read-only) from the Feedback tab on the `/submit` page. The editor can access this feedback from the Feedback tab on the `/decision` page.
The purpose of this task is to;
1. Deprecate the use of the 'Feedback' tab on the `/submit` and `/decision` pages.
1. To create new action links for the author and editor to access the author-proofing feedback from the Production editor.
2. Replace link icon with text on the `/dashboard/submissions` page. And add a text link on the `dashboard/edits` page.
3. Add the version to the submitted state recorded in the Production Editor>Feedback tab.
4. If multiple rounds of author proofing have been completed, author feedback should be ordered from most recent at the top to oldest at the bottom.
**Acceptance criteria;**
- [ ] Author should be able to access the Production editor using the text link; 'Provide production feedback' when in an 'author proofing assigned'/'author proofing in progress' state. An author should be able to access the Production editor using the text link; 'View production feedback' when in an 'author proofing in completed' state.
- [ ] Authors are able to click on the edit icon link from the `/dashboard/submissions` page to access the author-proofing form in an edit/read-only) state. The link text should be displayed when the initial round of review is instigated, and persist thereafter.
- [ ] Editors are able to click on the 'Production' link from the `dashboard/edits` page to access the author-proofing form in a read-only state.
- [ ] Author/editor should see the following record on the Production editor>Feedback tab; Last edited e.g. 'Edited '[insert `meta.title`]' version [insert version number] on 2023-09-25 15:11' and submitted e.g. 'Ryan Dix submitted feedback for '[insert `meta.title`]' version [insert version number] on 2023-09-25 15:11'.
- [ ] Editors can only ever access the Production editor>Editor or Production editor>Feedback in a read-only state.v3.1.0Vignesh DevendranVignesh Devendranhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1472Journal archetype event triggers are not working2024-02-15T07:53:27ZRyan Dix-PeekJournal archetype event triggers are not workingThe 'journal` uses the following notification triggers. All of which when actioned are not sending an email notification;
1. Reviewer rejects an invitation to review
1. Submitted review
1. Submitted manuscript
Email notifications should...The 'journal` uses the following notification triggers. All of which when actioned are not sending an email notification;
1. Reviewer rejects an invitation to review
1. Submitted review
1. Submitted manuscript
Email notifications should be sent on the above events when a template is selected from the Configuration>Emails page. The triggers when actioned should send an email notification on the `aperture` archetype only. These events have not been developed to display on the `prc` archetype - perhaps this should be handled as part of this fix as well.
![Screenshot_2023-12-06_at_13.33.26](/uploads/7658460e091c8da250020e3fd9d18f66/Screenshot_2023-12-06_at_13.33.26.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1471[CoLab] Update editor role names2024-02-19T10:43:42ZRyan Dix-Peek[CoLab] Update editor role names| Current name | Function | New name |
| ------ | ------ | ------ |
| Senior editor | Requires access to submission in order to provide advice | **Advisory curator** |
| Handling editor | Requires access to submission in order to provi...| Current name | Function | New name |
| ------ | ------ | ------ |
| Senior editor | Requires access to submission in order to provide advice | **Advisory curator** |
| Handling editor | Requires access to submission in order to provide advice | **Advisory curator** |
| Editor | Is {{Sender}} | **Handling curator** |
These changes should be implemented on Control panel;
![Screenshot_2023-12-06_at_12.36.25](/uploads/aa30780671ed1e7a18a1f79cdbd483ea/Screenshot_2023-12-06_at_12.36.25.png)
This should only be implemented on https://nbdt.cloud68.co/ and https://biophysics-sciencecolab.kotahi.cloud/CoLab Biophysics v6Pankaj Agrawalpankaj@coloredcow.comPankaj Agrawalpankaj@coloredcow.com