Skip to content

Commit da3b94b

Browse files
authored
Text to explain usage of schema ids
1 parent 3a23d5d commit da3b94b

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

examples/annotation_import/video.ipynb

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -372,6 +372,12 @@
372372
"cell_type": "code",
373373
"source": [
374374
"########## Frame Classifications ##########\n",
375+
"\n",
376+
"# Frame base nested classifications do not support using the feature's name to extract ontology features. \n",
377+
"# For this single case we are going to use the classification's featureSchemaId and the answers' featureSchemaId \n",
378+
"# We will update the annotation object with the featureSchemaIds on step 5 after we create the ontology in step 2\n",
379+
"\n",
380+
"\n",
375381
"frame_bbox_with_checklist_subclass_ndjson = {\n",
376382
" \"name\": \"bbox_class\",\n",
377383
" \"segments\": [{\n",
@@ -700,7 +706,6 @@
700706
"cell_type": "code",
701707
"source": [
702708
"## For nested frame base classifications we need to pass a featureSchemaId instead of the name. \n",
703-
"## We are working towards implementing the \"name\" format for frame base classifciations\n",
704709
"\n",
705710
"features = project.ontology().normalized\n",
706711
"\n",

0 commit comments

Comments
 (0)