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
For basic stuff, we can test it right on the labelstud.io website. Importing arbitrary "content" and specifying a custom template on their website is pretty straightforward.
With a few standard custom annotation workflows (specified like the Gist above) I think we could have a relatively slick way of identifying key markers of "concepts" in SoilKnowledgeBase. These would then be further processed, defined, categorized, linked to external ontologies and internal resources, etc.
Here are places where this may apply:
identifying logical elements in Soil Taxonomy clauses
The idea is that the annotation of text and images produces JSON markup that refers to unique line/character position, XY position/regions on images, etc. and assigns a particular label. This could be used for guiding e.g. optical character recognition, extraction of elements for processing or referencing in new contexts etc.
These types of annotations would need to be tied to a specific instance of an asset (e.g. via SHA hash) to ensure that they at least invalidate (need to be re-verified) if the resource changes.
The text was updated successfully, but these errors were encountered:
I have worked a bit with label-studio and I would like to integrate it further as a trial way of graphical annotation of various digital assets. Here is a Soil Taxonomy themed Gist for text-based named entity recognition: https://gist.github.com/brownag/c520c0c52fe272341ed7c6ae3c404f05
For basic stuff, we can test it right on the labelstud.io website. Importing arbitrary "content" and specifying a custom template on their website is pretty straightforward.
Playground
With a few standard custom annotation workflows (specified like the Gist above) I think we could have a relatively slick way of identifying key markers of "concepts" in SoilKnowledgeBase. These would then be further processed, defined, categorized, linked to external ontologies and internal resources, etc.
Here are places where this may apply:
The idea is that the annotation of text and images produces JSON markup that refers to unique line/character position, XY position/regions on images, etc. and assigns a particular label. This could be used for guiding e.g. optical character recognition, extraction of elements for processing or referencing in new contexts etc.
These types of annotations would need to be tied to a specific instance of an asset (e.g. via SHA hash) to ensure that they at least invalidate (need to be re-verified) if the resource changes.
The text was updated successfully, but these errors were encountered: