Bug #1516
Mis à jour par Serge Heiden il y a plus de 9 ans
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à".
h3. Discussion
MD:
* due to corpora architecture evolution in 0.7.8, some corpora directories have the same name in lower and uppercase.
* those corpora may have the same CQP name (in the registry file), this incoherence prevents to load the second corpus (the second corpus cannot be loaded at startup or session time).
h3. Solution
h4. Rustine 1
The rustine is to prevent loading corpus with the same name (lower or upper cased). The corpus less recent is not loaded and removed from the loaded corpus list (in the "$TXM/workspaces/default.xml" file).
Note: the files of the corpora not loaded are not removed from disk.
h4. Solution
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
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à".
h3. Discussion
MD:
* due to corpora architecture evolution in 0.7.8, some corpora directories have the same name in lower and uppercase.
* those corpora may have the same CQP name (in the registry file), this incoherence prevents to load the second corpus (the second corpus cannot be loaded at startup or session time).
h3. Solution
h4. Rustine 1
The rustine is to prevent loading corpus with the same name (lower or upper cased). The corpus less recent is not loaded and removed from the loaded corpus list (in the "$TXM/workspaces/default.xml" file).
Note: the files of the corpora not loaded are not removed from disk.
h4. Solution
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