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.

Sign up for GitHub

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

Jump to bottom

Add delay to new upload approval email reporting #554

Open
roikle opened this issue Sep 8, 2016 · 1 comment
Open

Add delay to new upload approval email reporting #554

roikle opened this issue Sep 8, 2016 · 1 comment
Labels
Enhancement Desired improvement to design or implementation that adds value.
Milestone
2.2.9

Comments

@roikle
Copy link

roikle commented Sep 8, 2016

When a new upload to an atlas is made an email is reported to vetters of the atlas. Would it be possible to have delay (e.g. 30-60 mins) before this email was sent by Nunaliit? If the upload is still waiting for approval after the specified delay, than the email is sent, otherwise no email is sent out.
@roikle roikle added Enhancement Desired improvement to design or implementation that adds value. Question Issue related to implementation whose answer would benefit others. Added to FAQ. labels Sep 8, 2016
@jpfiset jpfiset modified the milestone: 2.2.9 Sep 21, 2016
@roikle
Copy link
Author

roikle commented Sep 27, 2016

If we set the option vetterNotificationDaily to true by default and the vetterNotificationInstant option to false by default, this could address this issue. Assuming the daily notification only reports outstanding submissions at the end of day. Does this make sense?

@roikle roikle removed the Question Issue related to implementation whose answer would benefit others. Added to FAQ. label Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement Desired improvement to design or implementation that adds value.
Projects
None yet
Milestone
2.2.9
Development

No branches or pull requests
2 participants
@jpfiset @roikle