You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We already are sending some emails e.g. when notifying users during registration.
DB has email information for dandiset owners and contacts, and all registered users of the archive.
I think it would make total sense to centralize ability to email DANDI users by use via API, so we could potentially use it in services outside of the dandi-archive, e.g. for admins
validation errors reminders -- to corresponding authors of dandisets
audit summaries -- to corresponding authors of dandisets
there could potentially be use cases even for authenticated users, although not immediately needed
dandi-cli reportbug {dandiset_id} (does not exist but could)
So having endpoint(s) allowing for those above would have been nice IMHO. It could potentially also take care about proper re-formatting of markdown message text into html and txt versions, adding "branded" header/footnotes and other conveniences.
We could have per dandiset endpoint /dandisets/{dandiset__pk}/contact and then /users/contact with data fields like
We already are sending some emails e.g. when notifying users during registration.
DB has email information for dandiset owners and contacts, and all registered users of the archive.
I think it would make total sense to centralize ability to email DANDI users by use via API, so we could potentially use it in services outside of the dandi-archive, e.g. for admins
there could potentially be use cases even for authenticated users, although not immediately needed
dandi-cli reportbug {dandiset_id}
(does not exist but could)So having endpoint(s) allowing for those above would have been nice IMHO. It could potentially also take care about proper re-formatting of markdown message text into html and txt versions, adding "branded" header/footnotes and other conveniences.
We could have per dandiset endpoint
/dandisets/{dandiset__pk}/contact
and then/users/contact
with data fields likeRelated
Current functionality which does emailing
so the skeleton is already there in https://github.com/dandi/dandi-archive/blob/HEAD/dandiapi/api/mail.py and there is already the
build_message()
to serve as a starting point!The text was updated successfully, but these errors were encountered: