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/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/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/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/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/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/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/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.foundation