Feature #904
Mis à jour par Matthieu Decorde il y a presque 9 ans
Currently to add a new corpus to a portal one has to:
a- upload the binary corpus
b- if updating an existing corpus, one needs to delete the old corpus or shut down corpus application in order to avoid conflict with the old import.xml corpus configuration file
c- remotely unzip the binary corpus
d- provide the path to the unzipped binary corpus
e- run the new corpus command
To provide a better service for portal administrator,
the new corpus operation should be:
a- upload the binary corpus
b- run the Load corpus command
c- ask if an existing corpus should be replaced
h3. Validation test
* run a lexicon on the ABC corpus
* remove the ABC corpus
* upload a new ABC corpus
* load the newly ABC uploaded corpus
* refresh the page
* run a lexicon on the ABC corpus
The first and second results are different
a- upload the binary corpus
b- if updating an existing corpus, one needs to delete the old corpus or shut down corpus application in order to avoid conflict with the old import.xml corpus configuration file
c- remotely unzip the binary corpus
d- provide the path to the unzipped binary corpus
e- run the new corpus command
To provide a better service for portal administrator,
the new corpus operation should be:
a- upload the binary corpus
b- run the Load corpus command
c- ask if an existing corpus should be replaced
h3. Validation test
* run a lexicon on the ABC corpus
* remove the ABC corpus
* upload a new ABC corpus
* load the newly ABC uploaded corpus
* refresh the page
* run a lexicon on the ABC corpus
The first and second results are different