Bug #2241

RCP: 0.7.7, new corpus architecture and update during TXM installation or TXM update

Added by Matthieu Decorde almost 6 years ago. Updated about 4 years ago.

Status:New Start date:09/22/2015
Priority:Normal Due date:
Assignee:- % Done:


Category:Corpus Spent time: -
Target version:TXM X.X


Mail BP:

I already have a VOEUX corpus in TXM before upgrading to 0.7.7.
When TXM is upgraded to 0.7.7, I see two instances of the VOEUX corpus, one at the top of the list, and the second at the bottom (or near the bottom).
These two instances correspond to the previous version of VOEUX corpus : it is smaller than the one delivered with TXM 0.7.7 (T=61102 vs T=61162) and has no mention of date, author, etc. at the beginning of the Description.
These two instances look like two views of the same object : every modification on one is also applied on the other one. Except deletion : deleting the "bottom" view of VOEUX doesn't suppress the "top" view (but this top view "is not ready").
If one delete every view of VOEUX and then load again this corpus, one gets a warning, like "Le corpus voeux existe déjà".


Implémenter un transfert de politique d'architecture de corpus à l'installation et à la mise à jour de TXM (silencieux).

Implémenter un test de conformité de politique d'architecture de corpus au démarrage et au chargement de corpus.

See: https://groupes.renater.fr/wiki/txm-info/specs_search_engine#evolution_de_l_architecture


#1 Updated by Sebastien Jacquot almost 5 years ago

  • Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0

#2 Updated by Matthieu Decorde about 4 years ago

  • Target version changed from TXM 0.8.0 to TXM X.X

Also available in: Atom PDF