Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi corpus selection with conflicting segmentation should default to tokens #539

Closed
amir-zeldes opened this issue Nov 19, 2016 · 1 comment
Labels

Comments

@amir-zeldes
Copy link
Collaborator

If multiple corpora are selected whose corpus properties specify different segmentations are selected, results from corpora missing the selected segmentation cause the result list to get stuck. To reproduce:

  • select besa.letters and coptic.treebank
  • search for pos="ACOND"

See for example:
https://corpling.uis.georgetown.edu/annis/#_q=cG9zPSJBQ09ORCI&_c=YmVzYS5sZXR0ZXJzLGNvcHRpYy50cmVlYmFuaw&cl=5&cr=5&s=0&l=10&_bt=bm9ybV9ncm91cA

Note that switching base text to "tokens" and hitting refresh resolves the problem. The behavior of switching to "tokens" should happen by default (since it is impossible to display using a different segmentation whenever there are results from a corpus that does not support that segmentation).

@thomaskrause
Copy link
Member

This seems to be fixed. When selecting multiple corpora (e.g. besa.letters and Ridges) the "Show context in" field in the search option is reset to "tokens".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants