micropublication issueshttps://gitlab.coko.foundation/groups/micropublication/-/issues2020-03-23T19:39:39Zhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/265Track emails2020-03-23T19:39:39ZnickstifflerTrack emailsWe need to add additional variables to the the email data (o:tracking or o:tracking-opens) to support tracking. They put a transparent png into the html portion to track opens).
https://documentation.mailgun.com/en/latest/user_manual.htm...We need to add additional variables to the the email data (o:tracking or o:tracking-opens) to support tracking. They put a transparent png into the html portion to track opens).
https://documentation.mailgun.com/en/latest/user_manual.html#tracking-opensnickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/167Link to article as opposed to generic dashboard2019-03-14T15:48:21ZDaniela RacitiLink to article as opposed to generic dashboardAs editor I requested revisions to the authors.
The author receives the message below but the link 'View it on the dashboard' points to the generic dashboard. Can it go to the Article?
'The editors have requested revisions for your art...As editor I requested revisions to the authors.
The author receives the message below but the link 'View it on the dashboard' points to the generic dashboard. Can it go to the Article?
'The editors have requested revisions for your article "Test 0.4.0. Italics working ok here? Is the lab field throwing errors?".
Decision letter:
Dear author please revise the article as suggested
View it on your dashboard'0.5.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/162Change the text of the popup upon first submission2019-03-04T21:21:09ZDaniela RacitiChange the text of the popup upon first submissionCould not find if there was a previous ticket.
this has to do with: **submission form:** show confirmation modal on initial submission
the current text should be changed into:
You are submitting your article to the editorial office. An...Could not find if there was a previous ticket.
this has to do with: **submission form:** show confirmation modal on initial submission
the current text should be changed into:
You are submitting your article to the editorial office. An editor will be in touch after the initial evaluation. Are you ready to submit?
Please note the text of the pop up should be changed only for the initial submission0.4.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/298Unable to `yarn server`2021-04-15T14:12:48ZnickstifflerUnable to `yarn server`I have tried a few configurations, and haven't been successful at running our dev server with the newest code release. When running `yarn server`, the browser resolves to `Cannot GET /`. This happens for both `NODE_ENV=development` and `...I have tried a few configurations, and haven't been successful at running our dev server with the newest code release. When running `yarn server`, the browser resolves to `Cannot GET /`. This happens for both `NODE_ENV=development` and `NODE_ENV=production`. This happens on our AWS instance (ubuntu) as well as my development laptop (arch).
Here is the output:
```
yarn run v1.17.3
$ pubsweet server
info: Starting PubSweet app
info: Checking if database tables exist.
info: Database tables exist.
info: App started.
info: The app will be kept running, even if errors occur, until you stop it.
info: To stop the app use ctrl-C
info: Registered component @pubsweet/model-team
info: Registered component @pubsweet/model-user
info: Registered component @pubsweet/component-send-email
info: Registered component ./server/api
info: Registered component ./server/models/chatMessage
info: Registered component ./server/models/chatThread
info: Registered component ./server/models/curatorReview
info: Registered component ./server/models/identity
info: Registered component ./server/models/manuscript
info: Registered component ./server/models/manuscriptVersion
info: Registered component ./server/models/review
info: Registered component ./server/models/teamMember
info: Registered component ./server/models/team
info: Registered component ./server/models/user
info: Registered component ./app/wbApi
info: Registered server component ./app/wbApi
info: Registered component ./server/export
info: Registered server component ./server/export
info: Registered component ./app/pubMedApi
info: Registered server component ./app/pubMedApi
info: Registered component ./app/dataCiteApi
info: Registered server component ./app/dataCiteApi
info: Coko server => Registering graphql middleware...
info: Coko server => Middleware: Registered email middleware
info: Starting HTTP server
info: App is listening on port 5000
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
webpack built app 56e4439525a099158dd7 in 20021ms
ℹ 「wdm」: Hash: 56e4439525a099158dd7
Version: webpack 4.42.1
Time: 20021ms
Built at: 04/13/2021 8:20:06 PM
Asset Size Chunks Chunk Names
app.js 9.36 MiB app [emitted] app
app.js.gz 2.31 MiB [emitted]
app.js.map 8.66 MiB app [emitted] [dev] app
favicon.ico 6.61 KiB [emitted]
index.html 244 bytes [emitted]
logo.png 28 KiB [emitted]
print.css 1.01 KiB [emitted]
Entrypoint app = app.js app.js.map
[0] multi react-hot-loader/patch ./app 40 bytes {app} [built]
[../node_modules/@babel/runtime/helpers/interopRequireDefault.js] 147 bytes {app} [built]
[../node_modules/@coko/client/src/index.js] 94 bytes {app} [built]
[../node_modules/pubsweet-client/dist/index.js] 2.22 KiB {app} [built]
[../node_modules/react-dom/index.js] 1.33 KiB {app} [built]
[../node_modules/react-hot-loader/dist/react-hot-loader.development.js] 95.3 KiB {app} [built]
[../node_modules/react-hot-loader/index.js] 1.24 KiB {app} [built]
[../node_modules/react-hot-loader/patch.js] 229 bytes {app} [built]
[../node_modules/react/index.js] 190 bytes {app} [built]
[../node_modules/regenerator-runtime/runtime.js] 23.6 KiB {app} [built]
[../node_modules/webpack/buildin/harmony-module.js] 573 bytes {app} [built]
[./app.js] 2.71 KiB {app} [built]
[./routes.js] 2.97 KiB {app} [built]
[./theme.js] 4.24 KiB {app} [built]
[./userContext.js] 2.22 KiB {app} [built]
+ 1231 hidden modules
Child html-webpack-plugin for "index.html":
Asset Size Chunks Chunk Names
index.html 534 KiB 0
Entrypoint undefined = index.html
[../node_modules/html-webpack-plugin/lib/loader.js!./index.ejs] 404 bytes {0} [built]
[../node_modules/lodash/lodash.js] 528 KiB {0} [built]
[../node_modules/webpack/buildin/global.js] 472 bytes {0} [built]
[../node_modules/webpack/buildin/module.js] 497 bytes {0} [built]
ℹ 「wdm」: Compiled successfully.
ℹ 「wdm」: Compiling...
webpack building...
webpack built app abd7f989b8deb7944284 in 2011ms
ℹ 「wdm」: Hash: abd7f989b8deb7944284
Version: webpack 4.42.1
Time: 2011ms
Built at: 04/13/2021 8:20:09 PM
Asset Size Chunks Chunk Names
56e4439525a099158dd7.hot-update.json 35 bytes [emitted] [immutable] [hmr]
app.js 9.36 MiB app [emitted] app
app.js.gz 2.31 MiB [emitted]
app.js.map 8.66 MiB app [emitted] [dev] app
favicon.ico 6.61 KiB [emitted]
index.html 244 bytes [emitted]
Entrypoint app = app.js app.js.map
[0] multi react-hot-loader/patch ./app 40 bytes {app}
[../node_modules/@babel/runtime/helpers/interopRequireDefault.js] 147 bytes {app}
[../node_modules/@coko/client/src/index.js] 94 bytes {app}
[../node_modules/pubsweet-client/dist/index.js] 2.22 KiB {app}
[../node_modules/react-dom/index.js] 1.33 KiB {app}
[../node_modules/react-hot-loader/dist/react-hot-loader.development.js] 95.3 KiB {app}
[../node_modules/react-hot-loader/index.js] 1.24 KiB {app}
[../node_modules/react-hot-loader/patch.js] 229 bytes {app}
[../node_modules/react/index.js] 190 bytes {app}
[../node_modules/regenerator-runtime/runtime.js] 23.6 KiB {app}
[../node_modules/webpack/buildin/harmony-module.js] 573 bytes {app}
[./app.js] 2.71 KiB {app}
[./routes.js] 2.97 KiB {app}
[./theme.js] 4.24 KiB {app}
[./userContext.js] 2.22 KiB {app}
+ 1231 hidden modules
Child html-webpack-plugin for "index.html":
Asset Size Chunks Chunk Names
index.html 534 KiB 1
Entrypoint undefined = index.html
[../node_modules/html-webpack-plugin/lib/loader.js!./index.ejs] 404 bytes {1}
[../node_modules/lodash/lodash.js] 528 KiB {1}
[../node_modules/webpack/buildin/global.js] 472 bytes {1}
[../node_modules/webpack/buildin/module.js] 497 bytes {1}
ℹ 「wdm」: Compiled successfully.
```Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/297Image path now includes server URL2021-01-26T18:13:38ZnickstifflerImage path now includes server URLIt looks like changes made in MR !300 is causing unexpected behavior. The full server URL is now stored in the database in addition to the image path. Example:
`{"url": "https://portal.micropublication.org/uploads/f82a5a73cb042583905a331...It looks like changes made in MR !300 is causing unexpected behavior. The full server URL is now stored in the database in addition to the image path. Example:
`{"url": "https://portal.micropublication.org/uploads/f82a5a73cb042583905a33185a122bf9.jpg", "name": "figure.jpg"}`
The figure does not render in the manuscript preview.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/295Null value in reference causes crash2020-09-27T19:07:26ZnickstifflerNull value in reference causes crashI am not sure how this happens, but on a couple of occasions authors have input references where the `pubmedId` is null. This causes the browser to crash when editing the references. I can edit the DB and replace the null with an empty s...I am not sure how this happens, but on a couple of occasions authors have input references where the `pubmedId` is null. This causes the browser to crash when editing the references. I can edit the DB and replace the null with an empty screen, but I am wondering how this might happen.
I am playing with adding a check to ensure objects do not contain null values here:
https://gitlab.coko.foundation/micropublication/micropublication/blob/master/app/components/SubmissionForm.js#L321Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/291Remove UI files that moved to storybook2020-08-21T19:29:36ZnickstifflerRemove UI files that moved to storybookThere are a few things that moved to `/ui/src` from /app/components/ui` but were never deleted. I sometimes edit the wrong file, but I am hesitant to delete anything.There are a few things that moved to `/ui/src` from /app/components/ui` but were never deleted. I sometimes edit the wrong file, but I am hesitant to delete anything.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/290Curator can submit to manuscript version under revision2021-02-02T23:57:28ZnickstifflerCurator can submit to manuscript version under revisionCurator submitted their assessment, but the editor couldn't see it because it went to a version that hadn't been submitted yet.Curator submitted their assessment, but the editor couldn't see it because it went to a version that hadn't been submitted yet.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/288Entering wrong username in password reset results in uninformative message2020-08-05T14:44:41ZnickstifflerEntering wrong username in password reset results in uninformative messageThe message is "There was an unexpected error" when it should be something like "Username not found". This is using a pubsweet component, so I am not sure the best way to handle it.The message is "There was an unexpected error" when it should be something like "Username not found". This is using a pubsweet component, so I am not sure the best way to handle it.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/285Replace pubsweet's base model with coko server's base model2020-05-28T19:24:44ZYannis BarlasReplace pubsweet's base model with coko server's base modelThis might need some checking, as the version coko server provides is different from the one we currently have as a dependency.This might need some checking, as the version coko server provides is different from the one we currently have as a dependency.JuanJuanhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/281show formatting during show changes between versions2020-08-11T00:41:42ZKaren Yookshow formatting during show changes between versionsI had a request from one of our SO's that while he is pleased with the show changes function, he would like to see paragraphs while looking at the changes between article versions. He looks at the revisions with unlocked tabs and goes ba...I had a request from one of our SO's that while he is pleased with the show changes function, he would like to see paragraphs while looking at the changes between article versions. He looks at the revisions with unlocked tabs and goes back and forth between versions, with show changes on.
I would like to add maintaining all formatting, e.g. italicization, as well.
How difficult would it be to add in maintaining formatting?https://gitlab.coko.foundation/micropublication/micropublication/-/issues/280Add our own base model2021-04-13T07:44:18ZYannis BarlasAdd our own base modelWe should add our own base model, that extends pubsweet's base model.
All our other models should extend our custom base.
Our own custom base would of course define all methods that we want all models to have.
For the time being, l...We should add our own base model, that extends pubsweet's base model.
All our other models should extend our custom base.
Our own custom base would of course define all methods that we want all models to have.
For the time being, let's just add a `findById` method that calls objection's `findById`, if only to have sth to test against.
Where this gets tricky is when one of our models extends one of pubsweet's other than base (eg. TeamMember extends pubsweet's TeamMember, not base).JuanJuanhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/279Need migration for section editor team on existing manuscripts2020-05-16T11:22:18ZnickstifflerNeed migration for section editor team on existing manuscriptsExisting manuscripts do not have a section editor team, so this breaks the dashboard.
https://gitlab.coko.foundation/micropublication/micropublication/blob/master/app/components/compose/Dashboard.js#L155
@yannis I can probably take care...Existing manuscripts do not have a section editor team, so this breaks the dashboard.
https://gitlab.coko.foundation/micropublication/micropublication/blob/master/app/components/compose/Dashboard.js#L155
@yannis I can probably take care of this, but I wanted to make an issue in case you were already working on it.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/278Section editor assignment notification2021-04-15T17:42:24ZYannis BarlasSection editor assignment notificationSection editor should receive email notification on assignment.Section editor should receive email notification on assignment.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/276Section editor testing2021-04-15T17:42:30ZDaniela RacitiSection editor testingRelated to #251
Hi Yannis, we tested the Section Editor role. Looks good!
A couple of things below:
- the section editor did not receive an e-mail notification when the article was assigned to her.
- It would be good to add in the Manage...Related to #251
Hi Yannis, we tested the Section Editor role. Looks good!
A couple of things below:
- the section editor did not receive an e-mail notification when the article was assigned to her.
- It would be good to add in the Manage team box both Editor and section editor roles - see screenshot 1
- We'd like to have the names of the section editor and Editor displayed in the dashboard - see screenshot 2
![Screen_Shot_1](/uploads/a80004a12f31716873d62e8c79c09218/Screen_Shot_1.png)![Screen_Shot_2](/uploads/96eca7447ae87f9afda2b8b2b2a21fbb/Screen_Shot_2.png)Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/275Canned messages for decision letters2020-12-22T21:48:46ZnickstifflerCanned messages for decision lettersWhen the editor makes a decision (accept, reject, revise), the letter field should automatically populate with a message that can be edited before sending.When the editor makes a decision (accept, reject, revise), the letter field should automatically populate with a message that can be edited before sending.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/274Reviewer management redesign2021-04-15T17:43:58ZYannis BarlasReviewer management redesignThe redesign revolves around having a list of reviewers ordered by preference, that once set up will automatically go through invitations.
More specifically, the editor:
* Goes to the page and creates a pool of possible reviewers.
* Dra...The redesign revolves around having a list of reviewers ordered by preference, that once set up will automatically go through invitations.
More specifically, the editor:
* Goes to the page and creates a pool of possible reviewers.
* Drags and drops people on the list to order them by preference.
* Sets how many reviewers should be invited at the same time, how many days the system should wait before a reminder and how many days to wait until the invitation is revoked. _(note: these could also be system-wide settings)_
* Clicks on a "run" button to start the invitation process.
If the reviewer declines, or the maximum waiting period passes, the system moves on to the next person on the list and repeats the process. The functionality should allow for manual overrides to cover edge cases (eg. a reviewer declines via email and not through the system)
__An example__:
Let's say the editor wants a single reviewer for this manuscript version, the waiting time for reminders is 2 days and the invitation expiration time is 6 days. The editor has chosen Reviewer A, Reviewer B and Reviewer C in that order.
On clicking "run" the system invites Reviewer A. They don't immediately respond, so a reminder email is sent to them after 2 days. They still don't respond, so after 6 days Reviewer A is uninvited.
Then it moves on to inviting Reviewer B, who immediately logs in and declines the invitation.
It finally moves to Reviewer C. They accept the invitation, so the invitation system "stops" for this version.
Under normal circumstances, the editor will not have needed to do anything beyond choosing the initial list of reviewers.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/272Revoke reviewer invitation2021-04-15T17:42:54ZYannis BarlasRevoke reviewer invitationSimilar to #263 and #264 in that it needs to happen both automatically and manually.
Revoking the invitation manually should be done in the reviewer management page.
Automatic revoking should be a cron job.
In combination with #264, i...Similar to #263 and #264 in that it needs to happen both automatically and manually.
Revoking the invitation manually should be done in the reviewer management page.
Automatic revoking should be a cron job.
In combination with #264, it would send a reminder after x days, and revoke after x + y days.
All pending invitations should be auto-revoked when a decision is made.
This should not delete the invitation, but keep the info (maybe with a status on the team member?)Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/271Spaces around author email2020-04-01T14:45:23ZnickstifflerSpaces around author emailA user couldn't submit their manuscript because email didn't pass validation. It turned out this was caused by a trailing space after the email.A user couldn't submit their manuscript because email didn't pass validation. It turned out this was caused by a trailing space after the email.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/270Middle initial text explanation2020-05-06T17:03:10ZDaniela RacitiMiddle initial text explanationChange the text on the top:
Enter author names in the order they will appear in the article. If you have a middle initial, enter it after your fist name.
In the Name box add:
First Name e.g. John WChange the text on the top:
Enter author names in the order they will appear in the article. If you have a middle initial, enter it after your fist name.
In the Name box add:
First Name e.g. John WYannis BarlasYannis Barlas