micropublication issueshttps://gitlab.coko.foundation/micropublication/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/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/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/282Add twiiter to notifications2020-05-21T19:42:03ZnickstifflerAdd twiiter to notificationshttps://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/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/273Respond to reviewer invitation from within email2020-04-01T18:02:43ZYannis BarlasRespond to reviewer invitation from within emailhttps://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/269Mint DOI from app2020-11-05T15:09:04ZnickstifflerMint DOI from appThe DOI gets registered through datacite. They have a graphql api (https://api.datacite.org/graphql).The DOI gets registered through datacite. They have a graphql api (https://api.datacite.org/graphql).https://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/264Automated reviewer reminder2021-04-13T07:43:25ZYannis BarlasAutomated reviewer reminderAutomate #263 when #261 is implemented.Automate #263 when #261 is implemented.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/263Send reviewer reminder2021-04-15T17:42:57ZYannis BarlasSend reviewer reminderOnce a reviewer has accepted an invitation, the editors should be able to manually trigger a reminder email if they haven't submitted their review.Once a reviewer has accepted an invitation, the editors should be able to manually trigger a reminder email if they haven't submitted their review.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/262Author proofing step2021-04-15T17:42:59ZYannis BarlasAuthor proofing stepOnce a manuscript has been accepted, the author needs to proof it.
The manuscript will need to be editable by the author again at that stage.Once a manuscript has been accepted, the author needs to proof it.
The manuscript will need to be editable by the author again at that stage.nickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/261Automated task service2020-03-29T20:47:20ZYannis BarlasAutomated task serviceWe need a service layer that will run periodically on its own and perform automated tasks.
eg. Marking a manuscript as stalled when nothing has happened on it for x days.We need a service layer that will run periodically on its own and perform automated tasks.
eg. Marking a manuscript as stalled when nothing has happened on it for x days.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/256Reorder authors in submission form2020-02-20T16:32:59ZYannis BarlasReorder authors in submission formUsers should be able to drag and drop authors after input.Users should be able to drag and drop authors after input.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/255Affiliation normalization2020-02-20T16:33:36ZYannis BarlasAffiliation normalizationThrough Ringold or a similar service.Through Ringold or a similar service.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/253PDF export2021-04-15T17:48:59ZYannis BarlasPDF exportCopy-pasting @nickstiffler's description from !181 here.
> @yannis We couldn't wait on this any longer as we receive frequent requests for the PDF view. Let me know if you have any suggestions on how this should be implemented or if thi...Copy-pasting @nickstiffler's description from !181 here.
> @yannis We couldn't wait on this any longer as we receive frequent requests for the PDF view. Let me know if you have any suggestions on how this should be implemented or if this is ok for now. My plan it to export to PDF directly from the app using Puppeteer https://developers.google.com/web/tools/puppeteer, so this will be temporary.Upcomingnickstifflernickstiffler