micropublication issueshttps://gitlab.coko.foundation/micropublication/micropublication/-/issues2021-08-24T08:48:31Zhttps://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/273Respond to reviewer invitation from within email2020-04-01T18:02:43ZYannis BarlasRespond to reviewer invitation from within emailhttps://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/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/249Use token for external reviewer invitations2021-05-05T20:46:37ZYannis BarlasUse token for external reviewer invitationsRight now, they simply need to sign up with the same email, but this seems insufficient.Right now, they simply need to sign up with the same email, but this seems insufficient.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/247Chat live updates2021-05-05T20:46:51ZYannis BarlasChat live updatesSo that users can see new messages arriving without needing to reload.
This requires graphql subscriptions to be set up server-side.So that users can see new messages arriving without needing to reload.
This requires graphql subscriptions to be set up server-side.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/246Show unread messages in chat2021-05-05T20:46:42ZYannis BarlasShow unread messages in chatWe should visually indicate that:
* there are unread messages in a chat (eg. on the "chat with author" button)
* which messages are now within the chat itselfWe should visually indicate that:
* there are unread messages in a chat (eg. on the "chat with author" button)
* which messages are now within the chat itselfhttps://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/192Allow additional uploads2021-05-05T20:43:03ZYannis BarlasAllow additional uploadsWe need the ability to upload file attachments beyond the main image.
To be decided:
* How many files can a user upload
* What type of files are allowed
* File size limits, if anyWe need the ability to upload file attachments beyond the main image.
To be decided:
* How many files can a user upload
* What type of files are allowed
* File size limits, if anyhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/191Modify Credit values2021-05-05T20:42:56ZYannis BarlasModify Credit valuesThis requires the micropublication team to work with the 'credit' organisation, in order to create values that are more appropriate to our use cases.
The only development task would be to update the options, once the above has been agre...This requires the micropublication team to work with the 'credit' organisation, in order to create values that are more appropriate to our use cases.
The only development task would be to update the options, once the above has been agreed upon.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/183Add author suggested reviewer to science officer section2021-05-05T20:41:53ZYannis BarlasAdd author suggested reviewer to science officer sectionAdd the reviewers suggested by the author in the science officer section of the
editor panel. (the science officer can currently only view the reviewers suggested by the
editors)Add the reviewers suggested by the author in the science officer section of the
editor panel. (the science officer can currently only view the reviewers suggested by the
editors)https://gitlab.coko.foundation/micropublication/micropublication/-/issues/182Multi-tenancy2021-05-05T20:41:58ZYannis BarlasMulti-tenancyWe discussed what “multi-tenancy” support would look like. In other words, how manuscript
submissions beyond WormBase (like FlyBase, XenBase etc.), as well as manuscripts outside of
biology (eg. geology) would be possible within the appl...We discussed what “multi-tenancy” support would look like. In other words, how manuscript
submissions beyond WormBase (like FlyBase, XenBase etc.), as well as manuscripts outside of
biology (eg. geology) would be possible within the application in the future.
The general idea is that everything would be hosted under the same application. The
manuscript submissions would be separated under categories within the same database. It
would be on the author to choose a category on initial submission.
The microPublication editors would need an administration interface where they can add new
categories, as well as manage who the editors and science officers for that category are. They
would also need to manage which forms are available for each category.
Editors and science officers assigned to these categories would only have permissions on the
categories they’ve been assigned to. These permissions would look similar to the editor and
science officer permissions for WormBase submissions in the current application. They wouldn’t
however, have the permission to manage team members of other categories.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/181Bioentity linking2020-06-04T20:36:23ZYannis BarlasBioentity linking“Linking” refers to highlighting genes or similar entities in the main description and methods text.
The goal is to have a navigable list of entities on the final article. Linking will be achieved by
communicating with an external API (w...“Linking” refers to highlighting genes or similar entities in the main description and methods text.
The goal is to have a navigable list of entities on the final article. Linking will be achieved by
communicating with an external API (which will be handled by Nicholas Stiffler). The Coko
application will send over the text and the API will respond with the links it found in the text.
Linking should be done early on by the submitting author (before the initial submission), quite
possibly with a “link” button next to the text. After the API response is received, the author will
be presented with a table of the links found and will be able to correct mistakes in the text and
running the linking function again.
The editors should also have access to the linking feature, so that they can check the
manuscript links and communicate to the author changes that they deem necessary.nickstifflernickstiffler