RCP: x.x, add concordance context cut

See #943

Currently “text” is the only structure used to cut concordance contexts.

• We must be able to cut several structures (for example “text” or “plu” & “deplu” or “p”)
• The import parameters defines which structures to cut in the concordance
  • Step 1: add “context_limit” parameter to “import.xml” file.
    • default text value is “text”
    • default type value is "list" *** can contain multiple values (ex: "text,plu,deplu") *** if type=“list”, the context limit query will be []|[]|…|[]
    • if @type=“query”, text value must be a CQL query
  • document how to patch “import.xml” for this parameter
  • test with Apocalypse corpus
  • Step 2: replace patch by complete import parameter interface
    • build an import UI for this parameter with a new section “Commands/Commandes” and the “Concordance context structure limits/Structures de limite de contextes de concordance”
    • save the field in “import.xml”

Add in admin documentation the new import parameter element : uis/ui@command=concordance/context_limit, @type attribute and text value

Validation test - Step 1

* Call concordance on DISCOURS corpus with query "

[]"

* exit TXM

* add the new import configuration in the DISCOURS corpus “import.xml” file (in ~/TXM/corpora/discours)

...
<uis>
  <ui command="concordance">
    <context_limits type="list">text,p</context_limits>
  </ui>
</uis>
...

* re-start TXM

* Call concordance on DISCOURS corpus with query "

[]", ensure left contexts are empty

Validation test - Step 2 (using UI)

* Call concordance on DISCOURS corpus with query "

[]"

* open the import parameters

* select the DISCOURS corpus source folders

* in the “Commands preferences” section, set the “concordance context structure limits to ”p" (list of structure separated by comma)

* start the import

* Call concordance on DISCOURS corpus with query "

[]", ensure left contexts are empty

(from redmine: issue id 1124, created on 2014/11/14 by Alexey Lavrentev)

• Relations:
  • relates #1093 (closed)

added Commands type::feature + 1 deleted label

changed milestone to %TXM 0.7.7

I don’t understand why this feature is linked to the import section, shouldn’t it be a dynamic TXM preference editable between two query executions ?
(and better, a Corpus preference in future)

(from redmine: written on 2015/04/23 by Sebastien Jacquot)

The origin of that ticket comes from the observation of incoherent reading of concordance contexts for a certain type of corpus, hence the import parameter setting to resolve that specific case.

More globally in TXM, there are transition laws between local and global (see https://groupes.renater.fr/wiki/txm-info/public/specs_parametres_preferences_commands) command parameters (corpus, query, threshold, etc.), user preferences (parameter default value, parameter value, etc.) and corpus parameters (font, default concordance reference, default edition type, previous queries, home page, etc.).

That ticket could be related to a specification defining those relations and how to manage them.

(from redmine: written on 2015/04/23 by Serge Heiden)

closed

assigned to @mdecorde