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
following a discussion with @dimus , the following use case would allow users to help classify / annotate bad names and suggest alternative valid names:
A checklist contains the species name Airius felis
a program X send the name to the resolver api at resolver.globalnames.org
resolver replies that the name Airius felis is bad and includes a feedback url
program X sends the feedback url to a user Y
User Y clicks on the feedback url
On the name feedback webpages, user Y confirms that the name is bad, indicates that the name contains a typo (e.g. Arius felis), is outdated, and that the valid name is Ariopsis felis .
next time program X sends the name Airius felis resolver replies that the name is bad, and include a suggestion to use the name Ariopsis felis suggested by user Y.
@dimus let me know if I captured the use case properly. I do realize that this use case if very specific to GloBI . . .
The text was updated successfully, but these errors were encountered:
I think your description is good, I would extend 6th point where most usual case would be not
to confirm that bad name is bad, but to complain when bad name is marked good and vice versa
following a discussion with @dimus , the following use case would allow users to help classify / annotate bad names and suggest alternative valid names:
@dimus let me know if I captured the use case properly. I do realize that this use case if very specific to GloBI . . .
The text was updated successfully, but these errors were encountered: