micropublication issueshttps://gitlab.coko.foundation/micropublication/micropublication/-/issues2021-05-05T20:46:25Zhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/20Create extensions that connect to grantome API2021-05-05T20:46:25ZYannis BarlasCreate extensions that connect to grantome APIhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/112Verify email on signup2019-12-18T15:50:05ZYannis BarlasVerify email on signupThis is work that should arguably happen in pubsweet.
Will loop back here when there further info.This is work that should arguably happen in pubsweet.
Will loop back here when there further info.0.17.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/75Invite reviewers by email2019-01-29T16:46:52ZYannis BarlasInvite reviewers by emailWe need the ability to enter an email when choosing a reviewer, beyond choosing an existing user.
The system will need to send out an email with a link to the app, so that the reviewer can sign up.
We'll also need to figure out a wa...We need the ability to enter an email when choosing a reviewer, beyond choosing an existing user.
The system will need to send out an email with a link to the app, so that the reviewer can sign up.
We'll also need to figure out a way to store that this email has been associated with that particular article, so that when they do sign up, they're already invited to review.
This obviously dependent on #26, so that emails go out in the first place.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/64Add a "Figure caption" textbox below the image2018-12-21T16:54:32ZDaniela RacitiAdd a "Figure caption" textbox below the imageMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/76Add DOI field2018-12-21T20:39:58ZYannis BarlasAdd DOI fieldThis is, for now, a free text field, that is available only to editors.This is, for now, a free text field, that is available only to editors.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/62Add 'Affiliation' box2018-12-27T14:37:19ZDaniela RacitiAdd 'Affiliation' boxCould be inline with each authorCould be inline with each authorMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/26Email notifications2018-12-19T17:57:50ZYannis BarlasEmail notificationsSet up mailer in the system.
From the MVP document in the wiki, email notifications that should go out are as follows:
- [x] _Editor_: Upon initial submission of an article
- [x] _Author_: Upon Editor selecting datatype for one of...Set up mailer in the system.
From the MVP document in the wiki, email notifications that should go out are as follows:
- [x] _Editor_: Upon initial submission of an article
- [x] _Author_: Upon Editor selecting datatype for one of their articles
- [x] _Editor_: Upon full submission of an article
- [x] _Science Officer_: Upon editor sending submission to SO
- [x] _Editor_: Upon Science Officer's approval decision
- [x] _Reviewer_: Upon reviewer invitation
- [x] _Editor_: Upon reviewer accepting or declining invitation to review
- [x] _Editor_: Upon the completion of a review
- [x] _Author_: Upon decision renderedMVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/40Warn about changes in the initial submission form2021-05-05T20:40:11ZYannis BarlasWarn about changes in the initial submission formThe context is as follows:
* The author has submitted the initial form
* The editor has assigned a datatype
* The author goes back into the form to fill out the second part of it
At this moment, the author could still make changes to th...The context is as follows:
* The author has submitted the initial form
* The editor has assigned a datatype
* The author goes back into the form to fill out the second part of it
At this moment, the author could still make changes to the initial part of the form.
We should keep track of the touched fields, and show the editors a warning about them.
A first version could simply mark the fields with `colorWarning`.
A future version could also potentially show the field's previous state.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/46Dashboard metadata2021-05-05T20:40:00ZYannis BarlasDashboard metadataWe need to define a list of metadata elements that exist in the dashboard for each section.
Current ideas:
* Link to the live HTML page for accepted articles (when that is built)
* Initial submission date
* Date of last action
* Basic...We need to define a list of metadata elements that exist in the dashboard for each section.
Current ideas:
* Link to the live HTML page for accepted articles (when that is built)
* Initial submission date
* Date of last action
* Basic reviewer information
* A collapsible textarea for notes, attached to each article
* Datatype selected by the editorshttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/72Populate 'Affiliation' with WormBase data2020-04-20T17:07:03ZDaniela RacitiPopulate 'Affiliation' with WormBase dataFor post <MVP> we should have a mechanism to populate the affiliation from WB data and give authors the possibility to update if need beFor post <MVP> we should have a mechanism to populate the affiliation from WB data and give authors the possibility to update if need beYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/77Preview button in submission form2018-12-13T21:01:20ZYannis BarlasPreview button in submission formWe need a "preview" button in the submission form, so that authors can see what their article would look like, before they submit.
The button should open a modal with the preview.
The preview itself should be identical to the preview ...We need a "preview" button in the submission form, so that authors can see what their article would look like, before they submit.
The button should open a modal with the preview.
The preview itself should be identical to the preview page used in the editorial stages.MVPYannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/79Auto save form2019-07-28T20:52:52ZYannis BarlasAuto save formSubmission form data should be saved automatically in the background, so that data is not lost, even if the author does not submit the form.Submission form data should be saved automatically in the background, so that data is not lost, even if the author does not submit the form.0.10.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/84ORCID2020-03-19T22:27:54ZYannis BarlasORCIDThere are 3 points where ORCID is of interest:
##### Authentication
Users could login and sign up via their ORCID (optional).
##### User profile
For when we have such a page of course (#86).
Users could connect their ORCID there and ...There are 3 points where ORCID is of interest:
##### Authentication
Users could login and sign up via their ORCID (optional).
##### User profile
For when we have such a page of course (#86).
Users could connect their ORCID there and optionally log in with it from then on.
Connecting it would also bring some related info about them.
##### Submission form
Give authors the option to use ORCID on the submission form, instead of manually entering their data.
This will be optional, not enforced.nickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/85Popup data display2021-05-05T20:40:59ZYannis BarlasPopup data displayThe current form (not in the pubsweet app) displays a popup that shows additional information associated with the auto-complete suggestions. Similar functionality was requested in the new form. They provide the associated data to displ...The current form (not in the pubsweet app) displays a popup that shows additional information associated with the auto-complete suggestions. Similar functionality was requested in the new form. They provide the associated data to display as "Type Info".https://gitlab.coko.foundation/micropublication/micropublication/-/issues/86User profile page2019-11-16T19:47:10ZYannis BarlasUser profile pageBasic page where users can update their name, username etc.Basic page where users can update their name, username etc.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/87Multiple admins2021-05-05T20:34:19ZYannis BarlasMultiple adminsLook into the use case of having >1 admin user.
This would definitely require some UI to manage permissions (most likely in the current admin team manager interface).Look into the use case of having >1 admin user.
This would definitely require some UI to manage permissions (most likely in the current admin team manager interface).https://gitlab.coko.foundation/micropublication/micropublication/-/issues/88User manager2020-08-07T06:31:03ZYannis BarlasUser managerAdmins should have access to a user manager, where they can view and (if there are no legal issues) create / delete users.Admins should have access to a user manager, where they can view and (if there are no legal issues) create / delete users.Upcomingnickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/89Add free text author names2019-03-14T13:53:20ZYannis BarlasAdd free text author namesie. Do not validate author names against wormbase.
This needs discussion, as we need to figure out how to potentially enable validation.
What I have in mind is, that in a multi-journal system, if the user chooses to submit to wormbase...ie. Do not validate author names against wormbase.
This needs discussion, as we need to figure out how to potentially enable validation.
What I have in mind is, that in a multi-journal system, if the user chooses to submit to wormbase, (only) then the wormbase validations kick in.
This raises a number of workflow questions, so it'll be revisited.0.5.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/93References2021-04-15T17:50:02ZYannis BarlasReferencesWe need a repeater element for references.
As a first iteration, these could be plain text, but we'll need to add options to identify references via a DOI or another identifier via api's.We need a repeater element for references.
As a first iteration, these could be plain text, but we'll need to add options to identify references via a DOI or another identifier via api's.nickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/96Draw attention to actionable articles2018-12-12T16:38:31ZYannis BarlasDraw attention to actionable articlesWe need a smart way to show in the dashboard that an action is currently required of the user for an article.
Things to think about:
* We should probably float articles where an action is required to the top.
* Not all actions are the...We need a smart way to show in the dashboard that an action is currently required of the user for an article.
Things to think about:
* We should probably float articles where an action is required to the top.
* Not all actions are the same (we could do better than "you need to do something" and possibly provide some context as to what that might be)julientaqjulien@coko.foundationjulientaqjulien@coko.foundationhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/97Make dashboard sections sortable2018-12-12T16:39:38ZYannis BarlasMake dashboard sections sortableWe can start with a couple of simple options (name and status) and enhance later.We can start with a couple of simple options (name and status) and enhance later.julientaqjulien@coko.foundationjulientaqjulien@coko.foundationhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/98Make dashboard searchable2018-12-12T16:40:43ZYannis BarlasMake dashboard searchableAs a first iteration, simply by name (and probably for the whole dashboard, not per section).
We can look into search enhancements down the line.As a first iteration, simply by name (and probably for the whole dashboard, not per section).
We can look into search enhancements down the line.julientaqjulien@coko.foundationjulientaqjulien@coko.foundationhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/99Add links to editor2020-02-28T11:57:13ZYannis BarlasAdd links to editorCannot currently enter a link in the editor.Cannot currently enter a link in the editor.nickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/101Allow video upload2021-05-05T20:40:42ZYannis BarlasAllow video uploadWe need to look into how storage and network limitations can create a problem for us with this.We need to look into how storage and network limitations can create a problem for us with this.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/103Suggested reviewer enhancements2021-05-05T20:46:15ZYannis BarlasSuggested reviewer enhancementsA couple of things here:
* Allow more than one suggested reviewers
* Ask for an optional email
* Possibly also allow for free text instead of forcing wormbase validated autocomplete data
Also update placeholder to "Please suggest at lea...A couple of things here:
* Allow more than one suggested reviewers
* Ask for an optional email
* Possibly also allow for free text instead of forcing wormbase validated autocomplete data
Also update placeholder to "Please suggest at least one reviewer"https://gitlab.coko.foundation/micropublication/micropublication/-/issues/107Allow for "other" datatype option2019-03-22T17:27:28ZYannis BarlasAllow for "other" datatype optionThis essentially means a none of the above datatype for cases where it might not be so clear what the answer is.This essentially means a none of the above datatype for cases where it might not be so clear what the answer is.0.6.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/108Species2021-05-05T20:42:27ZYannis BarlasSpeciesFor now this should read Organism and should be a drop down of “Nematode, Fruitfly, Frog, Fission Yeast, Budding Yeast, Fish, Rat, Mouse, Human” in the future, this should trigger a species specific gene set.For now this should read Organism and should be a drop down of “Nematode, Fruitfly, Frog, Fission Yeast, Budding Yeast, Fish, Rat, Mouse, Human” in the future, this should trigger a species specific gene set.https://gitlab.coko.foundation/micropublication/micropublication/-/issues/116HTML dump2019-04-03T14:50:43ZYannis BarlasHTML dumpIntroduce the ability to export an "HTML dump" of the article data and metadata.Introduce the ability to export an "HTML dump" of the article data and metadata.0.7.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/125Add dismissible pop up to acknowledge author submitted successfully2019-02-19T22:13:18ZDaniela RacitiAdd dismissible pop up to acknowledge author submitted successfullyAfter author hits submit author sees the article preview but there’s no acknowledgement message that the submission went through. -> should add one on a dismissible popup window -> we will do a dismissable pop up for now, when doing the ...After author hits submit author sees the article preview but there’s no acknowledgement message that the submission went through. -> should add one on a dismissible popup window -> we will do a dismissable pop up for now, when doing the design with Julien we will explore alternative options0.2Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/126Display author's e-mail in the editor panel2019-02-25T18:05:44ZDaniela RacitiDisplay author's e-mail in the editor panelAs an Editor I cannot see anywhere the e-mail address of the Author that submitted -> Yannis will add in the Editor PanelAs an Editor I cannot see anywhere the e-mail address of the Author that submitted -> Yannis will add in the Editor Panel0.2Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/127Add article preview next to accept/reject invitation in the reviewer's dashboard2019-02-20T21:52:04ZDaniela RacitiAdd article preview next to accept/reject invitation in the reviewer's dashboardAs Reviewer I cannot see the submission: my only actions are to accept or reject the invitation. Add article preview link ![Screen_Shot_2019-01-24_at_10.58.22_AM](/uploads/079e6d365cce4cc6ed9c8c3fb002df1f/Screen_Shot_2019-01-24_at_10.58....As Reviewer I cannot see the submission: my only actions are to accept or reject the invitation. Add article preview link ![Screen_Shot_2019-01-24_at_10.58.22_AM](/uploads/079e6d365cce4cc6ed9c8c3fb002df1f/Screen_Shot_2019-01-24_at_10.58.22_AM.png)0.2Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/137Dashboard view should show next action needed2021-05-05T20:42:04ZDaniela RacitiDashboard view should show next action neededDashboard view needs to show next action needed for an article in addition to the previous action doneDashboard view needs to show next action needed for an article in addition to the previous action donehttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/138email template announcements2021-05-05T20:43:08ZDaniela Racitiemail template announcements@yannis let @karen and @daniela know when you want the e-mail templates from us@yannis let @karen and @daniela know when you want the e-mail templates from ushttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/143Editor-Science Officer communication2019-02-16T19:46:21ZDaniela RacitiEditor-Science Officer communicationAfter the Science Officer approves the submission:
The submission is now with the Editor but the Editor cannot ping again the Science Officer with a button. Tested also post reviewer's response.
We discussed to have a button to ping the ...After the Science Officer approves the submission:
The submission is now with the Editor but the Editor cannot ping again the Science Officer with a button. Tested also post reviewer's response.
We discussed to have a button to ping the Science Officer any time (as the chat does not send direct notifications to the Science Officer). Yannis you said the button was there but I don't see it in the dashboard. See screenshot![Screen_Shot_2019-02-04_at_9.52.26_AM](/uploads/9c7552b534c95bbced712bae10c1a34f/Screen_Shot_2019-02-04_at_9.52.26_AM.png)0.2Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/151Manuscript versioning2019-11-20T17:25:57ZYannis BarlasManuscript versioningWe need to support multiple versions in the same article.
This means that when an editor sends an article back to the author, they should be able to make changes and submit a new version.
Some things that need to be supported:
* Edito...We need to support multiple versions in the same article.
This means that when an editor sends an article back to the author, they should be able to make changes and submit a new version.
Some things that need to be supported:
* Editors should be able to see all versions of the manuscript.
* Reviewers should be able to see all versions of the manuscript that they were assigned to. (eg. if the reviewer was not invited for the second round of review, they should only see the first version)
Pending #15 for proper support of multiple versions.0.16.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/177Re-open submission form to the author when revisions are needed2019-05-14T18:32:51ZYannis BarlasRe-open submission form to the author when revisions are neededThis is supposed to be a temporary solution, in the absence of proper versioning, which will come after the data model refactor.
Once the editors have made a revision decision, the following things will happen:
* The submission form wil...This is supposed to be a temporary solution, in the absence of proper versioning, which will come after the data model refactor.
Once the editors have made a revision decision, the following things will happen:
* The submission form will be editable by the author again in its entirety.
* The editors will not have access to the editor panel until the manuscript is re-submitted.
* The science officer approval status will be reset.
Some gotchas with this temporary solution:
* The science officer will need to approve the manuscript again.
* As we are not implementing proper versioning, we are essentially overwriting the decision of the same manuscript every time. Old decisions will not be available on each re-submission.
* Manuscripts under revision will not be visible to reviewers, even if they have been invited, until they are re-submitted.
* There can only be one review.0.8.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/179Assign science officer2019-06-04T13:41:44ZYannis BarlasAssign science officerWe need the ability to explicitly assign a science officer to a manuscript, just like we do with editors.
Development should also take care of #147.We need the ability to explicitly assign a science officer to a manuscript, just like we do with editors.
Development should also take care of #147.0.9.0Yannis BarlasYannis Barlashttps://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 publishedUpcomingnickstifflernickstifflerhttps://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.nickstifflernickstifflerhttps://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/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/185Reviewer comments to the editor2020-12-01T11:13:09ZYannis BarlasReviewer comments to the editorReviewers need an extra text area to leave private comments to the editors.Reviewers need an extra text area to leave private comments to the editors.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/186Reviewer open acknowledgement2019-09-16T18:12:22ZYannis BarlasReviewer open acknowledgementReviewers need a checkbox to indicate whether they want ‘open acknowledgement’ or
not.Reviewers need a checkbox to indicate whether they want ‘open acknowledgement’ or
not.0.13.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/187QC step2020-06-24T22:52:11ZYannis BarlasQC stepWe need a copyediting - curator QC step in the workflow, after the manuscript has been
accepted and before it goes into production.We need a copyediting - curator QC step in the workflow, after the manuscript has been
accepted and before it goes into production.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/188Editors chat channel with author2020-02-10T14:58:26ZYannis BarlasEditors chat channel with authorWe need to add a chat component that will enable dialogue between the author and the
editors. We discussed how we should differentiate visually between chats so that the
wrong thing doesn’t end up in the wrong channel.We need to add a chat component that will enable dialogue between the author and the
editors. We discussed how we should differentiate visually between chats so that the
wrong thing doesn’t end up in the wrong channel.0.19.0Yannis BarlasYannis Barlashttps://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/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/193Hide decision section in the editor panel from science officers2019-08-05T19:35:11ZDaniela RacitiHide decision section in the editor panel from science officersHi Yannis,
The 'Send to Author' button in the 'Decision' dropdown is not working.
Can you test to see if you can replicate the error?
thxHi Yannis,
The 'Send to Author' button in the 'Decision' dropdown is not working.
Can you test to see if you can replicate the error?
thx0.11.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/194Science officers should not be able to approve their own submissions2019-08-04T13:35:16ZYannis BarlasScience officers should not be able to approve their own submissionsThey should not be able to go through the editorial process generally.
They should be treated as "just an author" for the specific manuscript.They should not be able to go through the editorial process generally.
They should be treated as "just an author" for the specific manuscript.0.11.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/196editorial comments not saved2019-11-20T17:25:57ZKaren Yookeditorial comments not savedhttp://micropublications.coko.foundation/article/144f2bcb-3d3b-46be-8257-7bfb058aff16
for this article i had submitted editorial comments via the decision letter. As an author, I received this message:
The editors have requested revis...http://micropublications.coko.foundation/article/144f2bcb-3d3b-46be-8257-7bfb058aff16
for this article i had submitted editorial comments via the decision letter. As an author, I received this message:
The editors have requested revisions for your article "Testing of author revision access and function for author and what the editor can see".
Decision letter:
the article needs you to test the revision function
View it on the microPublication platform.
As an editor, I no longer see my comments to the authors. Did we decide to throw out decisions, if so I think they are necessary to keep so we can make sure the authors addressed everything.0.16.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/197Add email notification on revision submission2019-08-28T17:12:53ZYannis BarlasAdd email notification on revision submissionEmail should go to the assigned editor.Email should go to the assigned editor.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/198Cannot ping reviewer again2019-08-29T15:58:53ZYannis BarlasCannot ping reviewer again@draciti do you want to elaborate a bit on this?@draciti do you want to elaborate a bit on this?Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/220Lock version tabs2019-12-05T21:07:24ZYannis BarlasLock version tabsLock the version tabs in sync between the left and right hand panel of the split screen preview.
In other words, if you click on version one on the editor / reviewer panel, it should switch to version one of the preview automatically. ...Lock the version tabs in sync between the left and right hand panel of the split screen preview.
In other words, if you click on version one on the editor / reviewer panel, it should switch to version one of the preview automatically.
Probably worth introducing a toggle to unlock them as well.0.17.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/224Science Officer section2019-12-15T17:32:45ZYannis BarlasScience Officer sectionScience officers should only see the articles they were assigned to.
Make a separate "Science Officer Section" in the dashboard that is filtered accordingly.Science officers should only see the articles they were assigned to.
Make a separate "Science Officer Section" in the dashboard that is filtered accordingly.0.17.0Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/225Highlight differences between versions2020-04-01T14:45:28ZYannis BarlasHighlight differences between versionsThe diff should be between the current tab and the previous tab.The diff should be between the current tab and the previous tab.Yannis BarlasYannis Barlashttps://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/233Reinvite reviewer2020-01-24T14:46:49ZYannis BarlasReinvite reviewerWe need a button or something along those lines in the last version tab of the editor section that will:
* Assign a reviewer of an older version to this version
* Notify the reviewer via email that they need to check the changes
Once th...We need a button or something along those lines in the last version tab of the editor section that will:
* Assign a reviewer of an older version to this version
* Notify the reviewer via email that they need to check the changes
Once this button and chat with reviewers is implemented, we can hide the "Request Reviewer's attention" buttons.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/240Chat autosave2021-04-15T17:43:02ZYannis BarlasChat autosavenickstifflernickstifflerhttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/241Remove science officer approval2021-05-05T20:34:57ZYannis BarlasRemove science officer approvalApproval will now happen through chat.
Hide the SO section in the editor panel.
Also make sure that "accept" decisions are not blocked by the lack of SO approval.Approval will now happen through chat.
Hide the SO section in the editor panel.
Also make sure that "accept" decisions are not blocked by the lack of SO approval.UpcomingYannis BarlasYannis Barlashttps://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/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/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/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/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/251Section editors2020-05-06T17:04:19ZYannis BarlasSection editorsWe need a new role: Section editors.
SE's will have the same access rights as global editors, but only for manuscripts they've been assigned to.We need a new role: Section editors.
SE's will have the same access rights as global editors, but only for manuscripts they've been assigned to.Yannis BarlasYannis Barlashttps://gitlab.coko.foundation/micropublication/micropublication/-/issues/252Curators2021-04-15T17:42:27ZYannis BarlasCuratorsNew role: Curators
Curators will have pretty much the same interface as reviewers, but will be assigned instead of invited, like editors and SO's.New role: Curators
Curators will have pretty much the same interface as reviewers, but will be assigned instead of invited, like editors and SO's.Yannis BarlasYannis Barlashttps://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.Upcomingnickstifflernickstifflerhttps://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/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/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/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/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/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/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/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/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/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/273Respond to reviewer invitation from within email2020-04-01T18:02:43ZYannis BarlasRespond to reviewer invitation from within emailhttps://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/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/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/282Add twiiter to notifications2020-05-21T19:42:03ZnickstifflerAdd twiiter to notificationshttps://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/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/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/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 up