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
Similar to the queryByMatch assistant (or "query by example"), that let's the user create queries by choosing annotations in the annotation view, a corpusByMatch assistant can help the user to modify a virtual corpus by choosing metadata values in the metadata view.
For example, when the match contains the metadata field corpusSigle with the value BZK and the user clicks on BZK, a line below the metadata view appears saying Limit corpus to: corpusSigle=BZK. When choosing another field pubDate with a value 1990-02-01, the line is expanded to Limit corpus to: corpusSigle=BZK & pubDate=1990-02-01. By clicking on the same value again, the constraint will be removed.
When the user clicks on the line, the chosen constraints will be anded to the virtual corpus and the window scrolls to the VC builder.
This feature won't be available for stored-only fields. At the moment, it would be possible for string and date/number fields. To work for text and keyword fields, KorAP/Krill#32 needs to be resolved.
The text was updated successfully, but these errors were encountered:
Similar to the queryByMatch assistant (or "query by example"), that let's the user create queries by choosing annotations in the annotation view, a corpusByMatch assistant can help the user to modify a virtual corpus by choosing metadata values in the metadata view.
For example, when the match contains the metadata field
corpusSigle
with the valueBZK
and the user clicks onBZK
, a line below the metadata view appears sayingLimit corpus to: corpusSigle=BZK
. When choosing another fieldpubDate
with a value1990-02-01
, the line is expanded toLimit corpus to: corpusSigle=BZK & pubDate=1990-02-01
. By clicking on the same value again, the constraint will be removed.When the user clicks on the line, the chosen constraints will be anded to the virtual corpus and the window scrolls to the VC builder.
This feature won't be available for stored-only fields. At the moment, it would be possible for string and date/number fields. To work for text and keyword fields, KorAP/Krill#32 needs to be resolved.
The text was updated successfully, but these errors were encountered: