micropublication issueshttps://gitlab.coko.foundation/groups/micropublication/-/issues2021-05-05T20:43:24Zhttps://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.nickstifflernickstifflerhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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 editors