micropublication issueshttps://gitlab.coko.foundation/groups/micropublication/-/issues2020-02-20T16:32:59Zhttps://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/254External storage provider2020-02-20T21:06:09ZYannis BarlasExternal storage provider@nickstiffler is there any plans for using an external storage provider (eg. S3)?
This would probably make file handling a more sustainable solution in the long term than simply keeping an upload folder on the filesystem.@nickstiffler is there any plans for using an external storage provider (eg. S3)?
This would probably make file handling a more sustainable solution in the long term than simply keeping an upload folder on the filesystem.nickstifflernickstifflerhttps://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/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/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/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/184"Accept" wording needs to be better2021-05-05T20:41:49ZYannis Barlas"Accept" wording needs to be betterWe need to differentiate the wording between “accept an invitation” and “accepting a
manuscript”.We need to differentiate the wording between “accept an invitation” and “accepting a
manuscript”.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.