micropublication issueshttps://gitlab.coko.foundation/groups/micropublication/-/issues2018-10-11T15:40:24Zhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/69Display 'Disclaimer' text2018-10-11T15:40:24ZDaniela RacitiDisplay 'Disclaimer' textDisplay this text next to the disclaimer: ‘By submitting your article to microPublication Biology, you and any co-authors agree to the following: I/we declare to the best of my/our knowledge that each reported experiment is reproducible;...Display this text next to the disclaimer: ‘By submitting your article to microPublication Biology, you and any co-authors agree to the following: I/we declare to the best of my/our knowledge that each reported experiment is reproducible; that the submission has been approved by all authors; that the submission has been approved by the laboratory's Principal Investigator, and that the results have not been published elsewhere by us. As the author(s) I/we declare no conflict of interest.’MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/68Add 'References' box2018-10-11T15:39:21ZDaniela RacitiAdd 'References' boxbelow 'Reagents'. Free textbelow 'Reagents'. Free textMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/67Add 'Reagents' box2018-10-11T15:39:25ZDaniela RacitiAdd 'Reagents' boxBelow MethodsBelow MethodsMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/66Add Methods box2018-10-11T15:39:28ZDaniela RacitiAdd Methods boxbelow 'Main article text'below 'Main article text'MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/65Rename ”Pattern Description” box2018-10-11T15:40:27ZDaniela RacitiRename ”Pattern Description” boxRename 'Pattern Description' box to ‘Main article text'Rename 'Pattern Description' box to ‘Main article text'MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/63Move 'Title' box after funding2018-10-11T15:40:31ZDaniela RacitiMove 'Title' box after fundingMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/60Credit taxonomy link2018-10-11T15:40:36ZDaniela RacitiCredit taxonomy linkAdd link to Credit taxonomy to allow authors to see what it is about- https://casrai.org/credit/Add link to Credit taxonomy to allow authors to see what it is about- https://casrai.org/credit/MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/59Credit taxonomy label2018-10-11T15:40:39ZDaniela RacitiCredit taxonomy labelChange the label of Credit taxonomy from ‘Select’ to ‘Author contributionChange the label of Credit taxonomy from ‘Select’ to ‘Author contributionMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/52List reviewer suggestions on Editor Panel page2018-12-10T19:05:17ZAlex ThegList reviewer suggestions on Editor Panel pageThe Editor Panel's general info line should list all reviewers suggested by the author and the editor, so the SO can see them without moving to the Reviewer Control Panel.
This way, the Science Officer doesn't need access to the Reviewe...The Editor Panel's general info line should list all reviewers suggested by the author and the editor, so the SO can see them without moving to the Reviewer Control Panel.
This way, the Science Officer doesn't need access to the Reviewer Control Panel, and can review the suggested reviewers from the Editor Panel.
* Each reviewer should have their origin listed next to their name:
* "Author suggestion"
* or "Editor suggestion"
@adam @yannis we'd discussed these labels changing to "Invited" once reviewer invitations were sent, but it would probably make more sense for these labels in the general info line not to change, and reviewer status information to appear below, in the reviewer status summary. That would allow the most complete picture at-a-glance.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/51Move Editor Panel decision area above discussion thread2018-09-19T17:01:09ZAlex ThegMove Editor Panel decision area above discussion threadThe section of the Editor Panel that the editor uses to render a decision should go above the chat. This is to avoid having to scroll through long chat threads when trying to render a decision.The section of the Editor Panel that the editor uses to render a decision should go above the chat. This is to avoid having to scroll through long chat threads when trying to render a decision.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/50Reviewer control panel specs2018-12-10T19:01:03ZAlex ThegReviewer control panel specsThis ticket articulates the reviewer control panel MVP functionality.
* The author's reviewer suggestions should appear in 2 places:
* In an always-visible, static display
* Teed up in the interface the editor would use to add their...This ticket articulates the reviewer control panel MVP functionality.
* The author's reviewer suggestions should appear in 2 places:
* In an always-visible, static display
* Teed up in the interface the editor would use to add their own reviewers to a queue before sending reviewer invites, so they can be added at the click of a button
* Editors should be able to assemble a queue of potential reviewers, made up of author and their own reviewer suggestions, without actually inviting them. That way, the science officer can review the reviewers before any are invited.
* To begin, editors will need to select reviewers that have an account in the system (the micropublications system, not just a WB Person ID).
* Reviewers in the queue should be labeled as "Author suggestion" and "Editor suggestion" until they are invited, then "Invited," and subsequently "Agreed", "Declined", or "Complete".
* Editor should always be allowed to change the reviewer list, even after the SO has approved itMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/49Add "Send to Science Officer" button to Editor Panel2018-12-10T19:06:57ZAlex ThegAdd "Send to Science Officer" button to Editor PanelAn editor should be able to send a submission to the science officer at any point in the article's lifecycle.
Every article needs to go to the science officer initially, for signoff on the article and proposed reviewers. The first time,...An editor should be able to send a submission to the science officer at any point in the article's lifecycle.
Every article needs to go to the science officer initially, for signoff on the article and proposed reviewers. The first time, the science officer must either approve or not approve the submission to proceed, leaving any notes in the general discussion thread. After this, the editor should still have access to the send to science officer button, but when the science officer is ready to return the submission to the editor, he or she should simply leave a comment in the general discussion thread and hit a similar button to "return to Editor" without rendering any approve/do not approve decision again.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/48Dashboard permissions2018-09-19T16:49:58ZYannis BarlasDashboard permissionsThere are three sections in the dashboard:
* The author section, where the articles you submitted appear.
* The reviewer section, where the articles you have been invited to review appear.
* The editor section, where all submitted articl...There are three sections in the dashboard:
* The author section, where the articles you submitted appear.
* The reviewer section, where the articles you have been invited to review appear.
* The editor section, where all submitted articles appear for the editors to handle.
Permissions:
* Editor section is hidden to anyone **not** belonging to the Editor and Science Officer global teams.
* Authors can only see the articles that they have initiated.
* Reviewers can only see the articles that they have been invited to.
* Editors cannot see the articles that are not past their initial submission stage.MVPJureJurehttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/45Statuses in an article's lifecycle2018-12-10T19:10:00ZYannis BarlasStatuses in an article's lifecycleWe will have some simple statuses for starters (eg. "Not Submitted", "Under Revision" etc.).
We should come up with more refined statuses down the line.
So the to-do here for now is:
* [ ] Define what the different stages in the lifecyc...We will have some simple statuses for starters (eg. "Not Submitted", "Under Revision" etc.).
We should come up with more refined statuses down the line.
So the to-do here for now is:
* [ ] Define what the different stages in the lifecycle are
When that is done, we can see if all of them should be reflected in statuses or not.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/44Credit form field2018-09-19T17:02:47ZYannis BarlasCredit form fieldThis is part of #17, but it is unclear what the element should look like.
@atheg can you provide some insight on this?This is part of #17, but it is unclear what the element should look like.
@atheg can you provide some insight on this?MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/41Editors should assign articles in the dashboard2018-08-27T12:52:27ZYannis BarlasEditors should assign articles in the dashboardThey should assign themselves or someone else to articles right from the dashboard.
This will be done with a dropdown, as the number of editors for the time being is very small.They should assign themselves or someone else to articles right from the dashboard.
This will be done with a dropdown, as the number of editors for the time being is very small.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/35Article submission roles and permissions2018-12-10T19:11:10ZYannis BarlasArticle submission roles and permissionsTo do
* [x] Define teams (Authors, Reviewers, Editors, Science Officers) -- The first two are per article, the last two are both per article and global
* [x] When an article is not submitted, it is only visible by the author.
* [x] When ...To do
* [x] Define teams (Authors, Reviewers, Editors, Science Officers) -- The first two are per article, the last two are both per article and global
* [x] When an article is not submitted, it is only visible by the author.
* [x] When an article is not submitted or if the editors haven't assigned a datatype, the author can only see the initial part of the submission form
* [x] When an article's initial submission is through, the editors can see the article in the dashboard
* [x] When an article's initial submission is through, the editors can assign a datatype in the form
* [x] When a datatype has been assigned, the author can see (but not change) the datatype in the submission form, as well as the second part of the submission form.
* [x] Editors cannot change any values in the submission form apart from the datatypeMVPhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/34Connect data to app database2018-08-19T09:46:23ZYannis BarlasConnect data to app databaseThe important part here would be to come up with a schema for the data.The important part here would be to come up with a schema for the data.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/33Validations on form fields2018-08-27T12:43:37ZYannis BarlasValidations on form fieldsUse `yup` or `joi` to reduce boilerplate code.Use `yup` or `joi` to reduce boilerplate code.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/25Define teams2018-09-19T16:51:08ZYannis BarlasDefine teamsTeams are as follows:
* __Authors__ _(on an article)_
* __Reviewers__ _(on an article)_
* __Invited Reviewers__ _(on an article)_
* __Accepted Reviewers__ _(on an article)_
* __Rejected Reviewers__ _(on an article)_
* __Editors__ _(on an...Teams are as follows:
* __Authors__ _(on an article)_
* __Reviewers__ _(on an article)_
* __Invited Reviewers__ _(on an article)_
* __Accepted Reviewers__ _(on an article)_
* __Rejected Reviewers__ _(on an article)_
* __Editors__ _(on an article)_
* __Science Officers__ _(on an article)_
* __Editors__ _(global)_
* __Science Officers__ _(global)_
Authors and Reviewers can only have their role _on a specific article_.
Editors and Science Officer could have their role on a specific article, but they should also belong to a global team. MVPJureJure