Kotahi issueshttps://gitlab.coko.foundation/kotahi/kotahi/-/issues2024-01-23T15:10:24Zhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1509Unable to view Manuscripts2024-01-23T15:10:24ZCloud68 Support teamUnable to view Manuscripts<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
<!-- Required. Tell us what should happen -->
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behavio...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
<!-- Required. Tell us what should happen -->
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behaviour -->
When clicking view on a manuscript a white screen will be shown
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. Create a new manuscript
2. Upload a pdf
3. Enter text on the required fields
4. Submit the manuscript
5. Click the View button
The following error is shown on the console logs:
```
TypeError: c is undefined
yI app.48846056.js:377358
Go app.48846056.js:251028
gs app.48846056.js:251028
cl app.48846056.js:251028
sl app.48846056.js:251028
$s app.48846056.js:251028
Wi app.48846056.js:251028
unstable_runWithPriority app.48846056.js:251336
Fi app.48846056.js:251028
Wi app.48846056.js:251028
Ui app.48846056.js:251028
N app.48846056.js:251028
Xt app.48846056.js:251028
app.48846056.js:251028
es app.48846056.js:251028
callback app.48846056.js:251028
fo app.48846056.js:251028
os app.48846056.js:251028
pl app.48846056.js:251028
unstable_runWithPriority app.48846056.js:251336
Fi app.48846056.js:251028
fl app.48846056.js:251028
$s app.48846056.js:251028
Wi app.48846056.js:251028
unstable_runWithPriority app.48846056.js:251336
Fi app.48846056.js:251028
Wi app.48846056.js:251028
Ui app.48846056.js:251028
N app.48846056.js:251028
Xt app.48846056.js:251028
```
## Environment
<!-- Required. Provide relevant information such as browser name and version, PC or Mac use, internet speed, etc.]-->
Browser: Firefox
OS: Ubunutu
## 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. -->https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1506White screen when draging form filds out of the table2024-01-22T09:56:37ZCloud68 Support teamWhite screen when draging form filds out of the table<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
the grabbed field should return to the place is was grabbed
<!-- Required. Tell us what should happen -->
## Current behaviour
the scree...<!-- Required. Provide a general summary of the issue in the title above -->
## Expected behaviour
the grabbed field should return to the place is was grabbed
<!-- Required. Tell us what should happen -->
## Current behaviour
the screen will go white and you need to refresh in order to see the form again
also this is the error from the console:
```
TypeError: n.find(...) is undefined
value app.9c27b569.js:253555
Ia app.9c27b569.js:251028
ja app.9c27b569.js:251028
gs app.9c27b569.js:251028
cl app.9c27b569.js:251028
sl app.9c27b569.js:251028
$s app.9c27b569.js:251028
Wi app.9c27b569.js:251028
unstable_runWithPriority app.9c27b569.js:251336
Fi app.9c27b569.js:251028
Wi app.9c27b569.js:251028
Ui app.9c27b569.js:251028
j app.9c27b569.js:251028
z app.9c27b569.js:251028
Jt app.9c27b569.js:251028
Kt app.9c27b569.js:251028
Gt app.9c27b569.js:251028
qt app.9c27b569.js:251028
ht app.9c27b569.js:251028
ln app.9c27b569.js:251028
Za app.9c27b569.js:251028
ul app.9c27b569.js:251028
cl app.9c27b569.js:251028
sl app.9c27b569.js:251028
$s app.9c27b569.js:251028
Wi app.9c27b569.js:251028
unstable_runWithPriority app.9c27b569.js:251336
Fi app.9c27b569.js:251028
Wi app.9c27b569.js:251028
Ui app.9c27b569.js:251028
el app.9c27b569.js:251028
notify app.9c27b569.js:377358
notifyNestedSubs app.9c27b569.js:377358
i app.9c27b569.js:377358
f app.9c27b569.js:377358
Vv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Iv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Wv app.9c27b569.js:377358
Uv app.9c27b569.js:377358
Bv app.9c27b569.js:377358
Nv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
dispatch app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
Gv app.9c27b569.js:377358
m app.9c27b569.js:377358
fluidLift app.9c27b569.js:377358
fn app.9c27b569.js:377358
r app.9c27b569.js:377358
_y app.9c27b569.js:377358
l app.9c27b569.js:377358
c app.9c27b569.js:377358
fn app.9c27b569.js:377358
r app.9c27b569.js:377358
_y app.9c27b569.js:377358
o app.9c27b569.js:377358
T_ app.9c27b569.js:377358
is app.9c27b569.js:251028
os app.9c27b569.js:251028
pl app.9c27b569.js:251028
unstable_runWithPriority app.9c27b569.js:251336
Fi app.9c27b569.js:251028
fl app.9c27b569.js:251028
$s app.9c27b569.js:251028
Wi app.9c27b569.js:251028
unstable_runWithPriority app.9c27b569.js:251336
Fi app.9c27b569.js:251028
Wi app.9c27b569.js:251028
Ui app.9c27b569.js:251028
gl app.9c27b569.js:251028
unstable_runWithPriority app.9c27b569.js:251336
Fi app.9c27b569.js:251028
ml app.9c27b569.js:251028
hl app.9c27b569.js:251028
H app.9c27b569.js:251336
onmessage app.9c27b569.js:251336
EventHandlerNonNull* app.9c27b569.js:251336
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:251028
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:251028
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:68312
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:377358
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:221915
n app.9c27b569.js:1
<anonymous> app.9c27b569.js:1
<anonymous> app.9c27b569.js:1
app.9c27b569.js:251028
```
<!-- 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 new form on the form builder
2. add new fields
3. drag one filed out of the "table"
4. white screen
## 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. -->https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1505Malformed title when viewing a completed review2024-01-26T03:59:09ZBen WhitmoreMalformed title when viewing a completed reviewIn the decision page / decision tab, clicking on "Show" for a completed review, I saw this:
![image](/uploads/7641aee9b3b9d3e328ab14fa39fb5d6c/image.png)
The heading should be "Ben Whitmore’s Review Report", not "Ben Whitmore&#39;s Revi...In the decision page / decision tab, clicking on "Show" for a completed review, I saw this:
![image](/uploads/7641aee9b3b9d3e328ab14fa39fb5d6c/image.png)
The heading should be "Ben Whitmore’s Review Report", not "Ben Whitmore's Review Report’s Review Report".
Actually, it would be better style to have it in sentence case, not Title Case. Thus it should ideally read "Ben Whitmore’s review report".https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1500Create notification tests2024-02-05T14:36:44ZRyan Dix-PeekCreate notification testsThe purpose of the task is to create Cypress tests to ensure email notifications are sent within the context of the following components;
1. Control panel>Tasks & Notifications page (Task Manager)
1. Discussions (Chat)
**Task Manager*...The purpose of the task is to create Cypress tests to ensure email notifications are sent within the context of the following components;
1. Control panel>Tasks & Notifications page (Task Manager)
1. Discussions (Chat)
**Task Manager**
1. Email notification sent manually from Control panel>Notifications
1. Email notification sent manually from Control panel>Task>recipient>User roles>Registered user
1. Email notification sent manually from Control panel>Task>recipient>User roles>Unregistered user
2. Email notification sent manually from Control panel>Task>recipient>User roles>Author
3. Email notification sent manually from Control panel>Task>recipient>User roles>Reviewer
4. Email notification sent manually from Control panel>Task>recipient>User roles>Editor
6. Scheduled emails sent from Control panel>Task>recipient>User roles>Registered user
2. Scheduled emails sent from Control panel>Task>recipient>User roles>Author
3. Scheduled emails sent from Control panel>Task>recipient>User roles>Reviewer
4. Scheduled emails sent from Control panel>Task>recipient>User roles>Editor
**Discussions**
Scheduled notifications, 1st notification sent after 30mins of inactivity and subsequent notifications next day (UTC);
1. Scheduled email notifications sent to an automatically subscribed user; editor
1. Scheduled email notifications sent to an automatically subscribed user; reviewer
1. Scheduled email notifications sent to a manually subscribed user; group manager
1. Mute channel suppresses email notifications being sent to subscribed users
Instant notifications, sent when @mention a user in the discussion channel;
2. Email notifications sent to an automatically subscribed user; editor
1. Email notifications sent to an automatically subscribed user; reviewer
1. Email notifications sent to a manually subscribed user; group manager
1. Mute channel suppresses email notifications being sent to subscribed users
**User profile**; mute notifications, when selected should prevent all scheduled/instant notifications from being sent to an end user.Sidorela UkuSidorela Ukuhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1497Update Node version 18-202024-01-23T04:15:42ZRyan Dix-PeekUpdate Node version 18-20https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1491Image, figures, and tables in Wax2023-12-22T07:09:39Zjulientaqjulien@coko.foundationImage, figures, and tables in WaxLooking at Pooyan and elife articles, the captions for tables and images we have right now in Kotahi don’t offer enough options, and they have a different behaviors.
We need to make it easier for the user to manage the captions for tabl...Looking at Pooyan and elife articles, the captions for tables and images we have right now in Kotahi don’t offer enough options, and they have a different behaviors.
We need to make it easier for the user to manage the captions for tables and images.
1. The UI to add title and caption for table is quite different from the images, but both forbid any complex caption.
This is how a figure caption looks like in Kotahi.
![Screenshot_2023-12-21_at_12.06.47](/uploads/2e5afd4806ab14a5532456bbfae02b26/Screenshot_2023-12-21_at_12.06.47.jpg)
And this is how a text caption exists:
![Screenshot_2023-12-21_at_12.09.55](/uploads/430bb51c3bf8530dbd895c90ce8b8f4e/Screenshot_2023-12-21_at_12.09.55.jpg)
They need to be the same, as the type of metadata they need is quite close.
2. We need to be able to add title, list, paragraphs, or any other block level type of content in the caption. Right now, we can only have simple text.
Adding a table should work as adding a image and it should offer the option to add custom label, title, long caption and alt text (for images).
Both can be put inside a `figure` element.
---
Last thing, sometimes, the images and the tables are not figure but part of the flow (it happens sometimes in elife’s epp manuscript).
In that case, we should be able to define that in wax.
Attaching a couple of pdf/images to show some examples:
![Screenshot_2023-12-21_at_12.36.43](/uploads/b5f5b36533b0b1d6bff9e921b19f906a/Screenshot_2023-12-21_at_12.36.43.jpg)
![Screenshot_2023-12-21_at_12.37.26](/uploads/42f34596e624490bddc6b08e33bf7e1a/Screenshot_2023-12-21_at_12.37.26.jpg)
![Screenshot_2023-12-21_at_12.38.04](/uploads/714638bd6283d6203e82015a4cfb4f5b/Screenshot_2023-12-21_at_12.38.04.jpg)
[elife examples are coming from Bioarxiv so their tables are actually images, but the problem would be the same with real `table` elements.]https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1490XSweet: New Approach2024-01-29T11:55:10ZMurali KasiramanXSweet: New ApproachXSweet does both normalization as well as font based style identification. We need to separate both these services as independent services.
1. Normalization (Clean-up, font normalization, junk characters, etc.)
2. Style identification
B...XSweet does both normalization as well as font based style identification. We need to separate both these services as independent services.
1. Normalization (Clean-up, font normalization, junk characters, etc.)
2. Style identification
Because of this synchronized activity, we are getting issues like block inside block, and other issues that are unnoticed as of now:
Example:-
<h4><math-display class=”math-node”>....</math-display>{{some content}}</h4>
This results in non-rendering of math tags in the editor due to block scoped schema.
We also find the following issues in Xsweet in terms of LaTex:
1. math-display comes inside table cell
example :- <td><p class=”paragraph”><math-display class=”math-node”> \\mu</math-display></p><td>
2. Missing closing tags for \left:-
Xsweet latex:
\left(7\right)p\left(1\right)=\theta _{y}\varphi \left(\frac{1-\mu }{\mu }
Corrected latex: -
\left(7\right)p\left(1\right) = \theta_{y} \varphi\left(\frac{1-\mu}{\mu}\right)
3. Unwanted closing tags:-
Xsweet latex:-
\dot {\iota }=\beta _{\iota }\cdot (\iota ^{T}-\iota \right)
Corrected latex:-
\dot {\iota }=\beta _{\iota }\cdot (\iota ^{T}-\iota)
4. Fraction correction:-
Xsweet latex:-
\sfrac{1}{2}https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1488[BPSC] Display journal name for all imported preprints2023-12-20T11:04:01ZRyan Dix-Peek[BPSC] Display journal name for all imported preprintsCurrent state; we are pulling the data from APIs. In this case; PubMed, Scopus and EuropePMC. We also have a fallback in place, where if the API does not provide a journal name we fetch this data from Crossref. If Crossref returns no dat...Current state; we are pulling the data from APIs. In this case; PubMed, Scopus and EuropePMC. We also have a fallback in place, where if the API does not provide a journal name we fetch this data from Crossref. If Crossref returns no data then we display the server name (e.g. Scopus).
Enhancement is to improve the quality of this data by first pulling the journal data from Crossref API in all cases.BPSC Collaborative form field typehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1486[BPSC] Search results should use metadata keywords2024-03-27T10:05:10ZRyan Dix-Peek[BPSC] Search results should use metadata keywordsThe purpose of this task is to allow Group Managers to see a list of journal results using a keyword search on the Manuscripts page. Currently, searching metadata keywords does not yield any relevant results.The purpose of this task is to allow Group Managers to see a list of journal results using a keyword search on the Manuscripts page. Currently, searching metadata keywords does not yield any relevant results.BPSC Collaborative form field typeBen WhitmoreBen Whitmorehttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1484[BPSC] Allow multiple users can access a collaborative form field2024-03-25T08:08:14ZRyan Dix-Peek[BPSC] Allow multiple users can access a collaborative form field'Document' form field type can be added to the review form. Initially, only reviewers, editors/Group Managers have permission to collaborate. Reviewers will collaborate on the `/review` page and editors/Group Managers will access the col...'Document' form field type can be added to the review form. Initially, only reviewers, editors/Group Managers have permission to collaborate. Reviewers will collaborate on the `/review` page and editors/Group Managers will access the collaborative form field from the `/decision` page.BPSC Collaborative form field typeGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1483[BPSC] Create full wax editor form field type2024-02-29T10:52:54ZRyan Dix-Peek[BPSC] Create full wax editor form field typeThe purpose of the collaborative editor is to support multiple users accessing and editing the same review content. For the MVP, only reviewers assigned to a review will be able to access this collaborative form field form the Review pag...The purpose of the collaborative editor is to support multiple users accessing and editing the same review content. For the MVP, only reviewers assigned to a review will be able to access this collaborative form field form the Review page, and editors assigned to a manuscript will be able to access the field from the control panel.
**Acceptance criteria;**
- [ ] This task aims to create a new form field type; Collaborative editor. A Group Manager should be able to select and add this field to a Review form.
- [ ] The collaborative editor will use a full wax editor. Production tools; Download, Annotations and Parsers should not be displayed.BPSC Collaborative form field typeGiannis Kopanasjkopanas@gmail.comGiannis Kopanasjkopanas@gmail.comhttps://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/1476pdf export2023-12-10T22:40:07Zjulientaqjulien@coko.foundationpdf exportIf you use a javascript file with two `.` in the name, the rendering gets broken.
```
qrcode.min.js
```
needs to be renamed
```
qrcode.js
```
so the export can run.
We should use the extension name of any file we uploadIf you use a javascript file with two `.` in the name, the rendering gets broken.
```
qrcode.min.js
```
needs to be renamed
```
qrcode.js
```
so the export can run.
We should use the extension name of any file we uploadhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1475Error when accessing 'view' from manuscripts page as admin2023-12-08T04:34:14ZAdam Hydeadam@coko.foundationError when accessing 'view' from manuscripts page as adminTypeError: Cannot read properties of undefined (reading 'updateChannelViewed') at yI (app.c5a8145d.js:377358:1) at Go (app.c5a8145d.js:251028:1) at gs (app.c5a8145d.js:251028:1) at cl (app.c5a8145d.js:251028:1) at sl (app.c5a8145d.js:251...TypeError: Cannot read properties of undefined (reading 'updateChannelViewed') at yI (app.c5a8145d.js:377358:1) at Go (app.c5a8145d.js:251028:1) at gs (app.c5a8145d.js:251028:1) at cl (app.c5a8145d.js:251028:1) at sl (app.c5a8145d.js:251028:1) at $s (app.c5a8145d.js:251028:1) at app.c5a8145d.js:251028:1 at t.unstable_runWithPriority (app.c5a8145d.js:251336:1) at Fi (app.c5a8145d.js:251028:1) at Wi (app.c5a8145d.js:251028:1)
when trying to access view from the manuscripts page for article 29990 on kotahidev @ryandixpeekhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1474PDF template: show classes and ID used in the article2023-12-07T04:42:44Zjulientaqjulien@coko.foundationPDF template: show classes and ID used in the articleWhen making a template in Kotahi, there is no way to know the different `class` and `id` used in the content of the article.
For example. the abstract is exported as `abstractSection`. If you don’t have that information you can’t make a...When making a template in Kotahi, there is no way to know the different `class` and `id` used in the content of the article.
For example. the abstract is exported as `abstractSection`. If you don’t have that information you can’t make a template.
We need table showing all the semantics available in the editor and their corresponding output to be able to style them correctly.https://gitlab.coko.foundation/kotahi/kotahi/-/issues/1469Capture a history of manuscripts edits2024-03-27T08:25:45ZRyan Dix-PeekCapture a history of manuscripts editsUseful links;
- Consider implementation of YJS; https://docs.yjs.dev/
- Demo of versioning in a basic prosemirror editor; https://demos.yjs.dev/prosemirror-versions/prosemirror-versions.html
High-level requirements to date;
1. Timestam...Useful links;
- Consider implementation of YJS; https://docs.yjs.dev/
- Demo of versioning in a basic prosemirror editor; https://demos.yjs.dev/prosemirror-versions/prosemirror-versions.html
High-level requirements to date;
1. Timestamp record log (Username, date and time e.g. Entry name | Ryan Dix | 12/112023 | 23:45)
1. Accept/reject changes are also recorded (Username, date and time e.g. Accepted | Ryan Dix | 12/112023 | 23:45)
1. Comments added/replied to (Username, date and time e.g. Comment | Ryan Dix | 12/112023 | 23:45)
1. Recorded as a session (each session is a version) of edits made to content, and include an idle time (time tbc)
![Screenshot_2023-11-29_at_12.19.16](/uploads/8726b4fe383214b4cec099d7a223c6a6/Screenshot_2023-11-29_at_12.19.16.png)Production editor version historyDan ViselDan Viselhttps://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/1465[Notify] Published object link returned to Kotahi2023-11-21T11:29:06ZRyan Dix-Peek[Notify] Published object link returned to KotahiOn publish action, a record is sent to Hypothe.is. Furthermore, Sciety should return a message (and email to author?) that the review is published on Sciety with a link to the object (this can also be saved as metadata).On publish action, a record is sent to Hypothe.is. Furthermore, Sciety should return a message (and email to author?) that the review is published on Sciety with a link to the object (this can also be saved as metadata).COAR Notify integrationhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1462Dev Notes2023-11-20T03:51:20ZAdam Hydeadam@coko.foundationDev NotesMaking these dev notes for potential discussion:
1. CMS
1. edit article template
2. multiple article templates depennding on article type
3. unpublish article
4. SEO
5. link to PDF & JATS
6. nested menu
...Making these dev notes for potential discussion:
1. CMS
1. edit article template
2. multiple article templates depennding on article type
3. unpublish article
4. SEO
5. link to PDF & JATS
6. nested menu
7. improve Pagedjs production UI
8. render preview
9. version templates/CSS
10. expose tree
2. Production tasks
3. Task inter-dependencies
4. Add editors to new submissions determined by article type
5. CRediT Taxonomy
6. ROR Taxonomy
7. MECA export
8. Submission form keywords taxonomy
9. Adding suggested reviewers by author to review process
10. Adding automated suggested reviewers
11. Personalising emails
12. Multiple revision email templates
13. Support file attachments to outgoing emails
14. Email author-\> editorial staff for help
15. Different reviewer forms depending on article type
16. Assigning reviewers to a group of submissions
17. Declining reviewers can suggest another reviewer
18. Author and staff availability cal
19. Export events to CSVhttps://gitlab.coko.foundation/kotahi/kotahi/-/issues/1461Releases Announcement and General Maintenance etc Announcement banner2024-01-10T08:16:26ZAdam Hydeadam@coko.foundationReleases Announcement and General Maintenance etc Announcement bannerWe need to work out how to
1. announce to kotahi admins that there is a new version of Kotahi released and what the new features are
2. maintenance forward-announcements to all users
3. general announcements to all users
First we start...We need to work out how to
1. announce to kotahi admins that there is a new version of Kotahi released and what the new features are
2. maintenance forward-announcements to all users
3. general announcements to all users
First we start with something very basic.
The ability to make announcements should be a new item in the left pane under Emails and labeled 'announce'. On that (new) page we see:
1. a basic textfield (we could use wax but probably the easiest is if we use plain text announcements for now)
2. an 'announce now!' button
3. a 'don't display any announcements' checkbox
Announcements get displayed on the user dashboard as an overlay that can be clicked away. Once a specific announcement is clicked away it does not appear again for the user. The dashboard item on the left of the nav menu should display a indicator to suggest there is an announcement to be read on the dashboard.
There is just one kind of announcement, later we will add:
* wax editor
* rich text display of announcements
* color selector for the background of an announcement to reflect the announcement type (eg warning, general announcement etc)
* setting color and some defaults for different types of announcement templates
Announcements (for now) are displayed in plain text against a white background (bordered)Ryan Dix-PeekRyan Dix-Peek