Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2024-03-27T08:26:17Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1571Editing actions on images are retained across versions2024-03-27T08:26:17ZRyan Dix-PeekEditing actions on images are retained across versionsProduction editor version historyhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1558Some pages do not have language localisation2024-03-14T05:11:40Zudhaya kumarSome pages do not have language localisationSome pages are not translated
1. **Title heading is not changed in all the table**
![image](/uploads/e6dbeb30cbfa72d5340b4742e4027bff/image.png)
2. **Control > Decision** (page—paragraph ,decision page, accept ,reject, revise)
![ima...Some pages are not translated
1. **Title heading is not changed in all the table**
![image](/uploads/e6dbeb30cbfa72d5340b4742e4027bff/image.png)
2. **Control > Decision** (page—paragraph ,decision page, accept ,reject, revise)
![image](/uploads/66010fb9b50d5c28d26446b73dfc6d6e/image.png)
3. **Setting -> Forms -> Submission**
![image](/uploads/a0db52658dfb99fbaf949585976424e9/image.png)
4. **Setting -> Forms -> Decision**
![image](/uploads/62f39e71fd515c9cddf27f13c2f4f0e5/image.png)
5. **Setting -> Forms -> Review**
![image](/uploads/c03d7bcbb1633546612409d7943c361b/image.png)
6. **Setting ->Emails**
![image](/uploads/677f6e775b7b5e9f00e2d98dd8d6de59/image.png)
7. **Wax Editor test are not translated**
![image](/uploads/5549303f4d42381f8fdd8b99c8711cfb/image.png)
.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1518Equations in image format2024-02-05T08:52:26Zmadhan mEquations in image formatThe common issue across all files is that the equations are in Image format. so that xsweet doesn't recognise them as equations instead recognises them as images.
Currently xsweet converts equations only if the following format is in th...The common issue across all files is that the equations are in Image format. so that xsweet doesn't recognise them as equations instead recognises them as images.
Currently xsweet converts equations only if the following format is in the document.
But in the case of the sample files xsweet is unable to recognise the equations if it is in image format as in the below attached image.
Please find the attached manuscript for the same as well[27353-Manuscript-196158-1-2-20221026.docx](/uploads/7ea656694942ced6e9232ace1c1cd8ec/27353-Manuscript-196158-1-2-20221026.docx)https://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/1477Load testing2024-02-15T06:33:52ZRyan Dix-PeekLoad testingThe Amnet team have requested an evaluation to determine system performance specifications; https://docs.google.com/document/d/1NPyo5mI7z4agXvxRO6DHwCR-8wygBMZgarpc4h1OFQ8/edit?usp=sharing
To evaluate performance specifications for Kota...The Amnet team have requested an evaluation to determine system performance specifications; https://docs.google.com/document/d/1NPyo5mI7z4agXvxRO6DHwCR-8wygBMZgarpc4h1OFQ8/edit?usp=sharing
To evaluate performance specifications for Kotahi we implement the following;
1. Turn database logging on and test queries to establish impact.
2. Create a Cypress test to run 'high load' queries simulating rapid interactions by multiple users.
3. Run an Amazon server using predefined standards to establish minimum memory requirements and other details.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1467Publisher[s] on single domain across journals2024-01-31T09:53:14ZsathishkumarbPublisher[s] on single domain across journals
# RFC: Feature proposal: Publisher[s] on single domain across journals
## Context
The purpose of this specification is to outline the requirements and behavior of the publisher login and redirect functionality on the Kotahi platform. ...
# RFC: Feature proposal: Publisher[s] on single domain across journals
## Context
The purpose of this specification is to outline the requirements and behavior of the publisher login and redirect functionality on the Kotahi platform. The primary aim is to empower a super admin to efficiently manage multiple journals through a unified URL. The proposed solution includes a comprehensive user interface for adding, editing, and managing publishers, all within a single URL. This enhancement will empower super admins to oversee journals comprehensively and provide publishers access to consolidated reports.
## Proposal
Objectives:
Unified Access:
Enable the super admin to access and manage all journals through a single domain URL.
Admin Interface Enhancement:
Develop a user-friendly super admin interface for seamless management of publishers.
Provide functionalities for adding, editing, and managing publishers within the same interface.
Streamlined Journal Administration:
Allow the super admin to perform actions such as adding, editing, and managing publishers in a unified environment.
Comprehensive Reporting:
Introduce a reporting feature within the super admin interface.
Allow publishers to access consolidated reports for all journals through their super admin login.
Scope:
Publisher[s] must be able to visit their journal[s] in the same domain URL. Admin interface must be provided to manage the publishers, and then they should be able to configure publishers to the journals and it follows many to many relationship model.
Ex:
Publisher A -> Journal
Publisher B -> Journal1
Publisher B -> Journal2
Publisher C -> Journal
User Interface:
The user interface of the publisher and configuring publishers to the journals are followed as below:
a. Add/Edit/Delete Publisher
delete won't be possible, if journals are mapped/configured to the publisher
b. Manage add/edit/remove journals(archetype) from the list to the publisher
Single URL Management:
Enable the super admin to perform all necessary actions related to publishers and journals within a single URL.
Publisher Management:
Provide options for adding, editing, and managing publishers efficiently.
Unified Control Panel:
Design a cohesive control panel allowing the super admin to oversee and control all aspects of multiple journals from a centralized location.
Reporting Section:
Implement a reporting section within the super admin interface for publishers to access consolidated reports across all journals.
## Design
[Include sketch or wireframes of the UI changes necessary for this feature]
## Implementation (if applicable)
[A description of the steps to implement the feature.]
## Alternative approaches (if applicable)
[Include any alternatives to meet this use case.]
## Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1437Math not rendered in chat2023-10-17T12:59:20ZAdam Hydeadam@coko.foundationMath not rendered in chatI am not seeing math render in the chat editor. See attached image
![Screenshot from 2023-10-14 23-57-45.png](/uploads/3c245e949841263f4d0767b8c5281e3f/Screenshot_from_2023-10-14_23-57-45.png)I am not seeing math render in the chat editor. See attached image
![Screenshot from 2023-10-14 23-57-45.png](/uploads/3c245e949841263f4d0767b8c5281e3f/Screenshot_from_2023-10-14_23-57-45.png)https://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/1364[Multitenancy] Add ability to move between groups2023-08-01T05:22:53ZRyan Dix-Peek[Multitenancy] Add ability to move between groupsAmnet multi-tenancy v2https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1348Ordering reference lists2023-09-26T06:18:01ZRyan Dix-PeekOrdering reference listsControls are needed to order references in a reference list. Use cases to be considered;
- Reference list in alphabetical order.
- Reference list adopts conventions as per citation format selection e.g. APA
- Reference list reflects the ...Controls are needed to order references in a reference list. Use cases to be considered;
- Reference list in alphabetical order.
- Reference list adopts conventions as per citation format selection e.g. APA
- Reference list reflects the order of citations.
Are these controls placed int he Wax editor or in the Citation modal?https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1339[Multi-tenancy] Allow groups to publish on separate domains/sub-domains2023-06-26T04:42:08ZRyan Dix-Peek[Multi-tenancy] Allow groups to publish on separate domains/sub-domainsOffering a solution, perhaps server management software, that allows users to set up a unique domain/sub-domain per group. Set up reverse proxy mapping per group so that we can map groups to different domains/sub-domains.Offering a solution, perhaps server management software, that allows users to set up a unique domain/sub-domain per group. Set up reverse proxy mapping per group so that we can map groups to different domains/sub-domains.Amnet multi-tenancy v2https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1226[Production editor] Add feature to remove annotations2023-03-07T19:41:06ZRyan Dix-Peek[Production editor] Add feature to remove annotationsCurrently, in a new session when accessing the Production editor; users are unable to remove annotations applied to paragraph text. Only annotations applied in the same session can be removed using the 'undo' action. This is problematic ...Currently, in a new session when accessing the Production editor; users are unable to remove annotations applied to paragraph text. Only annotations applied in the same session can be removed using the 'undo' action. This is problematic as an incorrectly applied annotation cannot be removed.
**Suggested solution;** clicking on the annotated area displays a cancel action on the top-right, clicking on cancel would remove the annotation.Amnet Production Editor v2https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1225PDF export html validation2023-04-19T06:37:04Zjulientaqjulien@coko.foundationPDF export html validationI run the html to generate the PDF on the html validator, and i found a couple of issues.
Most of them are ok, but with paged.js i think we should be only taking valid html to make sure a bug is not coming from there.
- Thee `section....I run the html to generate the PDF on the html validator, and i found a couple of issues.
Most of them are ok, but with paged.js i think we should be only taking valid html to make sure a bug is not coming from there.
- Thee `section.content` includes a full html page with `html`, `head` and `body` element. It should only include the content. On export, we should only keep the innerHTML of the body element and throw the rest away
- ```author-list ul``` inside an ```authors``` paragraph is prohibited.
- element `footnote` not allowed as a child of p (and pretty sure not allowed at all). footnote should be replaced by a span with a footnote class. (should be done in wax imho)
- multiple mathjax with the same ID, or nested svg with the same ID. I guess that’s because each math is done before pagedjs actually runs: I think we definitely want to use some kind of pagedjs plugin to render the math instead of making before end, but there may be good reasons for not doing that.
- Warning: Text run is not in Unicode Normalization Form C. it’s a warning but im curious how this can break the pdf rendering ```Ω(<em>x))``` : Ω(<em>x</em>)
- link can’t have empty target or empty rel
- img doesnt need a `/` to be a self closing element in the html world (but it needs in xml right?)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1222JATS validation error 'tr' missing child elements2023-03-02T07:19:46ZBen WhitmoreJATS validation error 'tr' missing child elementsI noticed the following in the kotahidev logs:
```
server_1 | info: ::ffff:172.18.0.1 - - [27/Feb/2023:09:26:47 +0000] "POST /graphql HTTP/1.1" 200 1182604 "https://kotahidev.cloud68.co/kotahi/versions/f77bf83d-d8d9-43b1-b28b-b2ff...I noticed the following in the kotahidev logs:
```
server_1 | info: ::ffff:172.18.0.1 - - [27/Feb/2023:09:26:47 +0000] "POST /graphql HTTP/1.1" 200 1182604 "https://kotahidev.cloud68.co/kotahi/versions/f77bf83d-d8d9-43b1-b28b-b2fff6099027/decision" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"
server_1 |
server_1 | 1 JATS validation error:
server_1 | [
server_1 | Error: Element 'tr': Missing child element(s). Expected is one of ( th, td ).
server_1 |
server_1 | at Schema.validate (/home/node/app/node_modules/libxmljs2-xsd/index.js:70:33)
server_1 | at validateJats (/home/node/app/server/jatsexport/validation.js:17:35)
server_1 | at jatsHandler (/home/node/app/server/jatsexport/graphql.js:57:24)
server_1 | at runMicrotasks (<anonymous>)
server_1 | at processTicksAndRejections (internal/process/task_queues.js:97:5)
server_1 | at async convertToJats (/home/node/app/server/jatsexport/graphql.js:70:31)
server_1 | at async middleware (/home/node/app/node_modules/graphql-shield/dist/generator.js:30:24) {
server_1 | domain: 17,
server_1 | code: 1871,
server_1 | level: 2,
server_1 | column: 0,
server_1 | line: 229
server_1 | }
server_1 | ]
server_1 | Converting inline-formula: \overline{C~}_{e}^{n}
server_1 | Attached formual inlineformula_0.svg
server_1 | info: [FILE CONTROLLER] - createFile: creating a new file representation
```
I'm not certain this relates to manuscript f77bf83d-d8d9-43b1-b28b-b2fff6099027.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1182Update pagedjs2023-01-17T12:28:20ZRyan Dix-PeekUpdate pagedjshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1176[Object store] Updates and config changes required to support ingestion and c...2023-01-09T12:29:11ZRyan Dix-Peek[Object store] Updates and config changes required to support ingestion and conversion of EPS filesUpdate coko server and config changes required to support ingestion and conversion of EPS files. Dependency to implement https://gitlab.coko.foundation/cokoapps/server/-/issues/16Update coko server and config changes required to support ingestion and conversion of EPS files. Dependency to implement https://gitlab.coko.foundation/cokoapps/server/-/issues/16https://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/1032Allow Reviewers to add comments in wax2022-09-19T15:24:02ZRyan Dix-PeekAllow Reviewers to add comments in waxhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/982Clicking on a callout should snap to footnote2022-07-26T23:34:03ZRyan Dix-PeekClicking on a callout should snap to footnote**Description;** when editing content in the Wax editor, clicking on a callout should snap to the respective footnote. This would be useful when editor content in Wax and also on export e.g. HTML/Flax.
Currently, clicking on callout cre...**Description;** when editing content in the Wax editor, clicking on a callout should snap to the respective footnote. This would be useful when editor content in Wax and also on export e.g. HTML/Flax.
Currently, clicking on callout created using a `note` has no interactive result. Clicking on callouts for importing Docx manuscripts that contain footnotes results in an error;
![Screenshot_2022-07-26_at_11.04.53](/uploads/85f163c6e461c171cc4d584aa15bad6a/Screenshot_2022-07-26_at_11.04.53.png)https://gitlab.coko.foundation/kotahi/kotahi/-/issues/788Improve Author name metadata tagging2022-10-14T11:01:55ZRyan Dix-PeekImprove Author name metadata tagging**Description;** in order to better organise metadata for output (XML, CSS etc), author `contrib` element and `corresp` attributes should be captured/integrated with the `AuthorInput` field. Currently, we capture this data in separate un...**Description;** in order to better organise metadata for output (XML, CSS etc), author `contrib` element and `corresp` attributes should be captured/integrated with the `AuthorInput` field. Currently, we capture this data in separate unrelated submissions form fields - the format of the data is not accessible/usable long term if we want to accurately markup author metadata for use in flax (CSS) or on export as valid JATS.Amnet Production Editor v2