openlibhums / openlibhums/janeway

Preprints: Contact email should be configurable at Repository level

Open
#2,861 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new feature Repositories
Dominant language
Python
Stars
238
Forks
97
Avg merge
9d 1h
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
As a Janeway Preprints/Repository administrator, I want apply a contact address at the Repository level. Currently I can only set a contact address at the Press level and that address is applied to all repositories on the server.

I also want to specify a separate 'bounce address' to receive reports of outgoing emails that were returned undeliverable.

Describe the solution you'd like

  1. Create email address settings from Press -> Repository Wizard (or some other setting at Repository level) (here we would probably put a 'no-reply' address)

  2. Add a new address field: Reply-to address. This should be used as the reply address for all automatic notifications (here we would put something like 'contact@preprintservername.com')

  3. Add a new address field: Bounce address. Bounces should be routed to this address. (here we would put something like 'bounces@preprintservername.com')

Additional context
image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the Press → Repository Wizard and the existing Press-level contact setting, but no files or tests. Start by tracing those settings and the automatic notification email path. Done means Repository-level no-reply, Reply-to, and Bounce addresses can be configured and used for the corresponding outgoing emails.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.