Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Email notification when (last) editor declares conflict of interest. #630

Open
TobiasKappe opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
Enhancement New feature or request

Comments

@TobiasKappe
Copy link

Is your feature request related to a problem? Please describe.
The conflict-of-interest (COI) system currently allows editors to declare a conflict when first opening an article. We are considering to use this at LMCS. Right now, seems that when an editor declares a conflict, they are removed from the article, but nothing else happens. This carries two risks:

  1. Fellow editors also assigned to the article may not be aware of this conflict, and thus silently assume that somebody else is managing the article; or
  2. When the last (or only) editor declares a conflict of interest, this could put the paper in limbo.

Describe the solution you'd like
We think this can be resolved by implementing two separate notifications:

  1. When one editor declares a conflict of interest for an article, the other editors should be notified via email.
  2. When the last editor of an article declares a conflict of interest, the editor in chief should be notified via email.
    This will help prevent articles from getting stuck in the process with nobody to care for them.

Describe alternatives you've considered
We could manually patrol articles that lose their editors, but this seems like an error-prone process as we would have to keep track of which articles had an editor assigned to them at some point.

@TobiasKappe TobiasKappe added the Enhancement New feature or request label Dec 3, 2024
@emperrin emperrin added the new New issue, pending triage label Dec 3, 2024
@rtournoy rtournoy removed the new New issue, pending triage label Dec 4, 2024
@rtournoy rtournoy moved this from Needs triage to Priority 2 in Episciences Issue Triage Dec 4, 2024
@rtournoy rtournoy assigned rtournoy and devletech and unassigned rtournoy Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
Status: Priority 2
Development

No branches or pull requests

4 participants