Feature #3305
Partition & Subcorpus, create Partition sub-class per construction method
| Status: | New | Start date: | 10/26/2022 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Commands | Spent time: | - | |
| Target version: | TXM 0.8.3 |
Description
Currently the Partition and Subcorpus parameters are only composed of the CQL queries forged by the Partition and Subcorpus dialogs.
This makes it impossible to have different behavior when export/import-ing, naming, cloning, etc. the Partition and Subcorpus results.
Solution¶
Possible Partition types based on current UI:- CQLPartition : named list of query
- OnePropertyAllValuesPartition : one structural unit property
- OnePropertyChoosenValuesPartition : named list of structural unit property + value(s)
- MultiplePropertiesAllValuesPartition : list of structural unit properties (BuildCrossPartition macro)
- ...
- CQLSubcorpus : one CQL
- ContextSubcorpus : one CQL + one structural unit [doesn't exist]
- OnePropertyChoosenValuesSubcorpus : one (structural unit property + values)
- CombinedPropertiesValuesSubcorpus : list (structural unit property + values) + composition rule (| or &)
- ...
Each Partition and Subcorpus type is specialized in export/import-ing, naming, cloning, etc.
History
#1 Updated by Matthieu Decorde 3 months ago
- Description updated (diff)
#2 Updated by Serge Heiden 3 months ago
- Description updated (diff)