micropublication issueshttps://gitlab.coko.foundation/micropublication/micropublication/-/issues2021-08-24T08:48:20Zhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/306Finish client-side refactor2021-08-24T08:48:20ZYannis BarlasFinish client-side refactor* [ ] all pages should use apollo hooks
* [ ] all ui components should move to storybook
* [ ] remove react-adopt
* [ ] remove react-powerplug* [ ] all pages should use apollo hooks
* [ ] all ui components should move to storybook
* [ ] remove react-adopt
* [ ] remove react-powerplugWrap uphttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/305Add graphql shield for server-side authorization2021-08-24T08:48:26ZYannis BarlasAdd graphql shield for server-side authorizationWrap uphttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/304Reviewer redesign feedback2021-08-24T08:48:31ZYannis BarlasReviewer redesign feedbackPasting @draciti's feedback here:
For section ‘Invite a reviewer that is not a user yet’
* I insert the reviewer info but I would like to add to the list, not send an invitation right away. The button below says send invitation. Would b...Pasting @draciti's feedback here:
For section ‘Invite a reviewer that is not a user yet’
* I insert the reviewer info but I would like to add to the list, not send an invitation right away. The button below says send invitation. Would be better that the button said “add to list”. Once that reviewer is in the list, the editor can rearrange reviewers and then start the automation. (need @karenyook’s feedback when she will be back from vacation)
* When I entered a reviewer there (‘Invite a reviewer that is not a user yet’) I did not receive an invitation but I did receive a notification when the invitation was revoked.
* Once I start the automation I cannot add reviewers in the ‘Invite a reviewer that is not a user yet’. We should allow that as we might receive additional names while the system is running. Possible to allow it?
* the cron seems not to be working. When I start the automation I do not receive reminder emails, waited 12 min now.Wrap uphttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/303Replace xpub edit with wax-prosemirror2021-08-24T08:48:42ZYannis BarlasReplace xpub edit with wax-prosemirrorWe'll also need a "special characters" plugin for the editor if it doesn't exist already.We'll also need a "special characters" plugin for the editor if it doesn't exist already.Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/302Reimplement statuses2021-05-05T20:31:49ZYannis BarlasReimplement statusesThere's two aspects to this:
One is that status creation should be constructed or derived server-side
The other is that we need a rethink of what statuses we're using.
@nickstiffler @draciti @karenyook feel free to brainstorm in the ...There's two aspects to this:
One is that status creation should be constructed or derived server-side
The other is that we need a rethink of what statuses we're using.
@nickstiffler @draciti @karenyook feel free to brainstorm in the comments what changes you'd like to see in the statuses.Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/301Make assign reviewers accessible after publish2021-08-24T08:48:38ZYannis BarlasMake assign reviewers accessible after publishAfter a manuscript is published, the assign reviewers page should be accessible, but read-only.After a manuscript is published, the assign reviewers page should be accessible, but read-only.Wrap uphttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/300Invite reviewer text2021-05-05T20:32:08ZYannis BarlasInvite reviewer textWhen invite is clicked:
* Open a modal
* Modal should have a text area where editors can compose their message
* Text that was composed becomes the email that is sent outWhen invite is clicked:
* Open a modal
* Modal should have a text area where editors can compose their message
* Text that was composed becomes the email that is sent outNexthttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/299Handle invitations after publish2021-08-24T08:48:35ZYannis BarlasHandle invitations after publishThere's states like publish, or when a manuscript is rejected, where the reviewer shouldn't be able to accept an invitation any more.
We should
* automatically uninvite reviewers when manuscripts get to these states
* check for these ...There's states like publish, or when a manuscript is rejected, where the reviewer shouldn't be able to accept an invitation any more.
We should
* automatically uninvite reviewers when manuscripts get to these states
* check for these states anyway when the reviewer responds to an invitationWrap uphttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/296Update team membership error2021-05-05T20:45:28ZnickstifflerUpdate team membership error@draciti and @karenyook experience an issue I have been unable to replicate. When they use the team manager to set the editors, SO and curator for an article, the server doesn't return and the modal doesn't close. The error on the server...@draciti and @karenyook experience an issue I have been unable to replicate. When they use the team manager to set the editors, SO and curator for an article, the server doesn't return and the modal doesn't close. The error on the server is:
`{"error":{"message":"Cannot read property 'title' of undefined","locations":[{"line":2,"column":3}],"path":["updateManuscriptTeamMembership"],"extensions":{"code":"INTERNAL_SERVER_ERROR"}},"level":"error","message":"Cannot read property 'title' of undefined","timestamp":"2020-10-31T23:24:41.678Z"}`
The error happens here:
https://gitlab.coko.foundation/micropublication/micropublication/blob/master/server/services/notify/emailMiddleware.js#L137
Can you think of a reason the version would be undefined?Nexthttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/268Add email field to user profile2021-05-05T20:46:31ZnickstifflerAdd email field to user profileUsers need to be able to update their contact email. The will require email confirmation. Depends on #258Users need to be able to update their contact email. The will require email confirmation. Depends on #258Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/250Add warning text about invitation emails in signup page2021-05-05T20:45:40ZYannis BarlasAdd warning text about invitation emails in signup pageeg. "Make sure you use the same email as ..."eg. "Make sure you use the same email as ..."Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/244Confirmation popups2021-05-05T20:46:20ZYannis BarlasConfirmation popupsUsers should get a confirmation dialog when they try to:
* Delete an article (dashboard)
* Retract an article (dashboard)
* Submit a review (reviewer panel)
* Submit a decision (editor panel)
* Invite / reinvite reviewer (assign reviewer...Users should get a confirmation dialog when they try to:
* Delete an article (dashboard)
* Retract an article (dashboard)
* Submit a review (reviewer panel)
* Submit a decision (editor panel)
* Invite / reinvite reviewer (assign reviewers page)
* Reinvite reviewer (editor panel)Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/243Retract article2021-05-05T20:43:32ZYannis BarlasRetract articleAfter initial submission (including when an article is under revision), the author should not be able to delete the article.
They should, however, be able to "retract" the article.
This will not make it go away from the dashboard, bu...After initial submission (including when an article is under revision), the author should not be able to delete the article.
They should, however, be able to "retract" the article.
This will not make it go away from the dashboard, but it would freeze it and label it as "retracted".Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/232Signup password confirmation2021-05-05T20:43:24ZYannis BarlasSignup password confirmationIt's a too easy right now to enter the wrong password.
We need an extra field that requires you to repeat your password.It's a too easy right now to enter the wrong password.
We need an extra field that requires you to repeat your password.Upcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/231Replace all current user Consumers with useContext hook2021-05-05T20:43:29ZYannis BarlasReplace all current user Consumers with useContext hookUpcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/217Implement Modal Provider2021-05-05T20:43:20ZYannis BarlasImplement Modal ProviderUpcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/215Dockerize production environment2021-08-24T08:49:08ZYannis BarlasDockerize production environmentEnd goal should be to deliver a built container for deployment.
Pending #214 and #22.End goal should be to deliver a built container for deployment.
Pending #214 and #22.Nexthttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/212Make setup and seed scripts not hang for 1 second2021-05-05T20:43:16ZYannis BarlasMake setup and seed scripts not hang for 1 secondUpcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/208Gray out suggested reviewer and disclaimer after initial submission2021-05-05T20:43:12ZYannis BarlasGray out suggested reviewer and disclaimer after initial submissionUpcominghttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/180Dashboard filtering2020-09-26T00:59:54ZYannis BarlasDashboard filteringWe discussed a filtering feature for the dashboard, where the editors could select a status from
the dropdown menu, thereby filtering the manuscripts to only those that are in the selected
status.
Articles that are “done” (published, re...We discussed a filtering feature for the dashboard, where the editors could select a status from
the dropdown menu, thereby filtering the manuscripts to only those that are in the selected
status.
Articles that are “done” (published, rejected etc) will be automatically archived (but not deleted),
so that they are by default not in the dashboard view.
The proposed states were as follows (wording subject to change):
* Needs datatype/curator QC - done ->initial submission ready
* Needs SO approval
* Needs reviewer invites
* Reviewer has been invited - done
* Needs reviewer chasing (needs a date step)
* Reviewer reviewing - done -> pending
* Author needs to revise
* Reviewers want to see revision
* Editor needs to make decision
* Needs to be publishedUpcomingnickstifflernickstiffler