Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2021-05-13T10:59:22Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/334[eLife] Adding Author response to the submissions form2021-05-13T10:59:22ZEugeniu Stribitchi[eLife] Adding Author response to the submissions formAs Kotahi User I would like to register Author response in the submission/evaluation form, so that it could be published
**Acceptance criteria:**
- [ ] Author response should be added to submission and evaluation view
- [ ] Field shou...As Kotahi User I would like to register Author response in the submission/evaluation form, so that it could be published
**Acceptance criteria:**
- [ ] Author response should be added to submission and evaluation view
- [ ] Field should be type of abstract
- [ ] Field shouldn't b requiredeLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/420[eLife] Download Crossref DOI on production server2021-06-09T13:40:34ZEugeniu Stribitchi[eLife] Download Crossref DOI on production servereLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/433[eLife] Split S3 bucket name2021-06-15T09:56:24ZRyan Dix-Peek[eLife] Split S3 bucket name**Description;** Currently, the bucket name is included as part of the S3_ENDPOINT URL for S3 only. Minio doesn't support including the bucket name in the endpoint, so this is an inconsistency. One way to resolve this is to split the buc...**Description;** Currently, the bucket name is included as part of the S3_ENDPOINT URL for S3 only. Minio doesn't support including the bucket name in the endpoint, so this is an inconsistency. One way to resolve this is to split the bucket name out of S3_ENDPOINT and have it in a separate S3_BUCKET variable. This would then work consistently for both S3 and Minio.
**Acceptance criteria;**
?eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/426[eLife] Backport content from Hypothesis2021-07-19T05:25:21ZRyan Dix-Peek[eLife] Backport content from Hypothesis**Description;** pull eLife annotations data from Hypothesis API and populate eLife-Kotahi database with all published eLife evaluations. Only update database, no need for previous post to be captured on the Manuscripts page.**Description;** pull eLife annotations data from Hypothesis API and populate eLife-Kotahi database with all published eLife evaluations. Only update database, no need for previous post to be captured on the Manuscripts page.eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/427[eLife] Register DOIs with Crossref for all backported content2021-07-19T05:25:38ZRyan Dix-Peek[eLife] Register DOIs with Crossref for all backported content**Description;** register DOIs with Crossref for all backported content. Potential implementation options; are to register via Kotahi submission form or use script to run all migrated evaluations through Crossref.**Description;** register DOIs with Crossref for all backported content. Potential implementation options; are to register via Kotahi submission form or use script to run all migrated evaluations through Crossref.eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/600[eLife] updated form structure to added to config file2021-08-10T00:56:17ZRyan Dix-Peek[eLife] updated form structure to added to config file**Description;** update latest version of the form in the configuration file; https://gitlab.coko.foundation/kotahi/kotahi/-/blob/main/app/storage/forms/submit.json
**Acceptance criteria;**
- Latest version of the form will be used in t...**Description;** update latest version of the form in the configuration file; https://gitlab.coko.foundation/kotahi/kotahi/-/blob/main/app/storage/forms/submit.json
**Acceptance criteria;**
- Latest version of the form will be used in the event the database is formatted/dropped.eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/580[eLife] Enable publishing DOIs to Crossref2021-09-09T12:04:32ZRyan Dix-Peek[eLife] Enable publishing DOIs to Crossref**Issue description;** evaluations are currently published to Crossref Sandbox. The purpose of this task is to enable the publishing of evaluation DOIs with Crossref.
Reference; https://www.crossref.org/documentation/member-setup/direct...**Issue description;** evaluations are currently published to Crossref Sandbox. The purpose of this task is to enable the publishing of evaluation DOIs with Crossref.
Reference; https://www.crossref.org/documentation/member-setup/direct-deposit-xml/testing-your-xml/
**Acceptance criteria;**
- [ ] TBCeLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/861[eLife] Import preprints2022-04-05T13:29:41ZRyan Dix-Peek[eLife] Import preprints**Description;** the eLife editorial team would like to triage and select preprints for review using Kotahi. They would like to use the 'NCRC' model, where preprints using a manual Refresh action. They would like to create their own keyw...**Description;** the eLife editorial team would like to triage and select preprints for review using Kotahi. They would like to use the 'NCRC' model, where preprints using a manual Refresh action. They would like to create their own keyword search query and ensure a category tag is assigned to each imported preprint (see list of 18 subject matter categories listed on the [elifesciences homepage](https://elifesciences.org/). These categories can potentially be exposed via bioRxiv or eLife APIs.
A further recommendations query should also run using a new [Semantic Scholar API](https://www.semanticscholar.org/product/api). Results that appeared in both bioRxiv and Semantic Scholar calls should be identified as 'priority preprints' to be considered.eLife v1https://gitlab.coko.foundation/kotahi/kotahi/-/issues/975[eLife] Add 'Upload image' plugin to AbstractEditor2022-08-03T05:27:06ZRyan Dix-Peek[eLife] Add 'Upload image' plugin to AbstractEditorAs an admin, I would like to embed images when reviewing content, and publish to Hypothe.is.
**Acceptance criteria;**
- [ ] `upload-file` feature is accessible in the Basic Wax editor when editing content in an `AbstractEditor`.
- [ ]...As an admin, I would like to embed images when reviewing content, and publish to Hypothe.is.
**Acceptance criteria;**
- [ ] `upload-file` feature is accessible in the Basic Wax editor when editing content in an `AbstractEditor`.
- [ ] An editor is able to use the Asset Manager to source & manage images.
- [ ] An Author is able to use a file picker to locate and add image files.eLife v1https://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/269Language localisation implementation2023-01-18T12:33:14ZRyan Dix-PeekLanguage localisation implementation**User story;** as a system administrator I would like to translate text on pages, menus, states and/or actions in order to customise the experience and improve usability for all users.
**Description;** the solution should allow system...**User story;** as a system administrator I would like to translate text on pages, menus, states and/or actions in order to customise the experience and improve usability for all users.
**Description;** the solution should allow system administrators to translate or include their own desired nomenclature across all language strings. The solution should be lightweight, and not attempt any automatic translations but rather perform simple string replacements as specified.
**Acceptance criteria;**
- Solution utilises an existing open-source application; [i18next](https://www.i18next.com/), ~~[Polyglot](https://airbnb.io/polyglot.js/)~~
- Contain embedded strings that supports the use of locales.
- Pages targeted for language changes;
| Page | Component |
| --- | --- |
| Menu | Manuscripts item |
| Dashboard | Section titles |
| Manuscripts | Action titles |
| Manuscripts | Column title e.g role & manuscript title |
| Decision page | Workflow > Decision > Recommendations/Reviews titles |
| Decision page | Workflow > Assign roles titles per dropdown |
| Decision page | Role title |
| New submission | Upload manuscript titles |
| Buttons | Notify, Submit, Publish/Re-publish |eLife v1