Skip to content
This repository has been archived by the owner on Oct 5, 2023. It is now read-only.

Recognition model and recognition date as fields per vendor #12

Open
sitescripter opened this issue Sep 3, 2018 · 2 comments
Open

Recognition model and recognition date as fields per vendor #12

sitescripter opened this issue Sep 3, 2018 · 2 comments

Comments

@sitescripter
Copy link

Case 1: Our recognition models are sure to change as we learn. We might want to update all images that were recognized by vendor AWS using model Generic before date 2018-08-30.

Case 2: When users notice an unsatisfactory recognition, we want to know the vendor, model, and recognition date that resulted in the metadata.

The field cf_aiMetadataModified allows us to find by date, but we don't know the model that was used. When using multiple vendors it becomes even more complicated, as Elvis doesn't give us access to the use of the nested data models of Elasticsearch. The cf_aiMetadataModified might not inform us about the recognition date from the vendor we're looking for.

Suggested solution: In lieu of access to nested data, the solution could be to have two fields per vendor:

  1. Recognition model (cf_aiModelAWS, cf_aiModelClaro, ...)
  2. Vendor specific recognition date (cf_aiUpdatedAWS, cf_aiUpdatedClaro,...)
@jaapvanblaaderen
Copy link
Collaborator

Nice suggestion. Note though that we currently only support Clarifai when it comes to using different models. This could be something to further generalize though also for other vendors (See also #13).

@sitescripter
Copy link
Author

Perhaps split it into two and focus on "Vendor specific recognition date"?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants