ISSUE-347: new Vector (*768) and a new internal sequence for Flavor IDs *using a dash* #348
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
But we provide in the deployment a fixed field type for this. This is a binding
…rate ...
Multiple extractions/annotations or vectors:
New way for this
$sequence_parts = !empty($sequence_id) ? explode('-', $sequence_id) : [1,1];
We check for the new properties which are `internal_sequence_id` and defaults to NULL for anything pre-generated to this new SBR feature
and
vector_768
DiegoPino
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #347
The new SBF ID structure (for Solr) allows a dash. Only ML generated SBF have this allowing a File level sequence (e.g a PDF, let's say Page 2) to have a subsequence, e.g Annotation 1, 2, 3.
Basically allowing something like this
{"id":"3byiu5-default_solr_index-strawberryfield_flavor_datasource/313796:1-2:en:548e48f0-a703-4101-875c-b6f9779c5dbf:chained_mobilenet_child"}Notice the
313796:1-2being 313796 the NODE, 1 the File level sequence (1 by default, and -2) being the second annotation generate by an ML ProcessorIIIF Content Search API (Format Strawberryfield) will also get a pull to allow that second level one to not confuse the search/matching (tested, works well)