-
Notifications
You must be signed in to change notification settings - Fork 7
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
Enable capture of image recognition metadata #297
Comments
@kitenetter It's a small task, I can do this as part of #237. |
@JimBacon could you please update the IndiciaAI proxy module on the iRecord site? I need the classifier to process multiple images per request, similar to what we did for the e-Surveyor. |
@kitenetter One unclear area is how to treat a situation where 1) users add several photos 2) use the classifier for suggestions and 3) remove or change those photos. It would be technically incorrect to send the user preference metadata with the new set of photos to the database because the suggestions were different when the user has decided to select the species. Is it OK to not send any classifier metadata where photos were modified or reclassified after the original user decision? |
This requires this warehouse ticket: Indicia-Team/warehouse#534 |
@kazlauskis asked: "Is it OK to not send any classifier metadata where photos were modified or reclassified after the original user decision?" I think we'll have to do that (i.e. not send metadata in such cases) - I can't think of any other practical way of dealing with the complexities of multiple photos and multiple subsequent updates to the ID decisions. |
I've fixed Indicia-Team/warehouse#534. |
Jim tells me that image recognition metadata is being captured within the apps for EBMS and e-surveyor, but not within the iRecord app. We would like to capture this data from the iRecord app as well.
I'm hoping that it will be relatively straightforward to apply the process from the other apps that are already doing this. Can you let me know how big a job this is?
The text was updated successfully, but these errors were encountered: