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
Let's go to party(1)<{E1}part{E2}parties>. We will have lots of fun.
Over here {E1} and {E2} refers to edition 1 and 2. the part and parties and spelling variant found in different editions. Party is the latest edition spelling.
I have parser which parse the annotation in a dictionary where it saves:
STAM is very open to however you want to model your data, so there is no single correct answer to this.
I'm not sure if I'm interpreting your use-case correctly, but you could make an annotation data set named spelling_variants with keys variant_text and edition (or variant_source?), and then do three annotations with a Text Selector on the same text span, each with annotation data like text = party, edition = LE etc... That way you can always independently add spelling variants from new editions as they become available and it's fairly easy to query variants given a specific edition.
Annotated data:
Over here {E1} and {E2} refers to edition 1 and 2. the part and parties and spelling variant found in different editions. Party is the latest edition spelling.
I have parser which parse the annotation in a dictionary where it saves:
I able to save the span in target, but i am not able to save spelling variant in annotationdata. Kindly help me.
The text was updated successfully, but these errors were encountered: