Skip to content

RCP: 0.7.2, improve Index to Concordance link

  • does not build the concordance query from the original index query (incomplete)
  • wrong if more that one position (see note 1)

Remove or Document this link until resolved.

Two suggestions for a solution:

The CQL associated to the link must combine the constraints of the original CQL (for example CQL_A=[frpos=“NOM”]) and the constraints expressed by the cell containing the link (for example: CQL_B=[frlemma=“pouvoir”]).

  • solution A) use the “::” operator to combine the queries: CQL_A :: CQL_B; works ?
  • solution B)
      1. if necessary, add the INTERSECTION of two CQP result sets method to the CQi API (the operator is already present in CQP)
      1. resolve CQL_B
      1. return INTERSECTION(CQP(CQL_A), CQP(CQL_B))
  • solution C) create a subcorpus result with CQL_A next to the Index and create its child concordance with CQL_B (Corpus >Index ; Corpus >Subcorpus >Concordance)
  • solution D) create a hidden subcorpus result with CQL_A child of the Index and create its child concordance with CQL_B (Index > hidden Subcorpus >Concordance)
  • solution E) create a concordance with CQL_B child of the Index (Index >Concordance)

Solution A is limited to the cases where CQL_A and CQL_B don’t use the “::” operator thus won’t be used.

Solution B is universal.

Solution C create a subcorpus&concordance are disconnected from the index. The subcorpus may be discontinue (1 tokens matches) but is visible.

Solution D the subcorpus is hidden

Solution E the internal subcorpus does not allow multi-token CQL + the concordance is often not useful when the index query is changed

Solution

Choose a solution

(from redmine: issue id 229, created on 2013/07/09 by Matthieu Decorde)