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

Email about open flags added on data entry #1702

Closed
Jegelewicz opened this issue Sep 19, 2018 · 2 comments
Closed

Email about open flags added on data entry #1702

Jegelewicz opened this issue Sep 19, 2018 · 2 comments

Comments

@Jegelewicz
Copy link
Member

Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html

From Taxonomy Committee Notes: On entering new records, when two identifications are available, it is difficult to remember to go back and add the second after data is loaded. Dusty suggests adding a flag, but that might be forgotten as well. Mariel suggests a notification of outstanding flags

Is your feature request related to a problem? Please describe.
Flags to remind operators that additional data needs to be entered for a record can be overlooked.

Describe the solution you'd like
Add "you have Needs additional data flags to review" to monthly notification email.

Describe alternatives you've considered
Get a bigger brain - Remember you have entered flags (or gather through some mysterious method that those entering data for you have entered them)

Additional context
Add any other context or screenshots about the feature request here.

Priority
I would like to have this resolved by date: 2018-10-31

@dustymc
Copy link
Contributor

dustymc commented Sep 27, 2018

I think two things came up at about the same time.

  1. There are too many emails, we don't have time, they don't get read.
  2. Please send more email.

If we're getting overwhelmed - and we probably are - I'm hesitant to add to the pile with low-priority/non time-sensitive notifications.

#1419

@Jegelewicz
Copy link
Member Author

Closing for lack of participation.

@dustymc dustymc mentioned this issue Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants