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

Emails policy needs review #33

Open
kmccurley opened this issue May 24, 2023 · 2 comments
Open

Emails policy needs review #33

kmccurley opened this issue May 24, 2023 · 2 comments

Comments

@kmccurley
Copy link
Member

Part of this is policy, but here's my guess on the behavior regarding emails:

  • An author should only receive one email when they first upload. Subsequent re-uploads should not generate a new email.
  • editors do not need to be told about an upload until it finishes copy editing
  • copy editors should be notified with a deadline for the issue.
  • once copy editing is finished, authors need to be given a deadline to respond to copy editing.
  • once a final version is approved, editors should be notified then
@kmccurley
Copy link
Member Author

Perhaps the notifications should be tied to an account on the site rather than to an email in the config like EDITOR_EMAILS. Then individual accounts can have their own notification preferences, perhaps in a table that links to User. This is related to how we should build role-based permissions, since right now an admin account has access to everything. This needs further thought.

@kmccurley
Copy link
Member Author

How long should we give the author to review copy edits? Investigate other practices. Joppe suggests 3-5 days?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant