Bug #975

TXM: 0.7.6, corpus import must not accept invalid corpus names

Added by Serge Heiden almost 5 years ago. Updated about 4 years ago.

Status:Feedback Start date:08/08/2014
Priority:Urgent Due date:
Assignee:- % Done:

90%

Category:Import Spent time: -
Target version:TXM 0.7.7

Description

Currently, CQP search engine cannot manage corpora with a name beginning with a digit: 0..9.

More generally, corpus names must follow a 'CQP naming policy' to be manageable by CQP.

Currently, the User Interface of corpus import or corpus load accept corpus names
that don't respect CQP naming policy.

The result is that when the import or the load is finished with success,
the corpus is available in the corpus view but is not useable by CQP.

Solution

  • corpus import:
    • in the import parameters window, the corpus name input field must indicate a corpus naming policy violation if the currently given corpus name doesn't respect it (for example with a red cross) OK the corpus name check is done when the user starts the import process.
    • the import process must NOT start until the corpus name doesn't respect the corpus naming policy. OK

see ticket #1033 for load process changes

Validation test

  • try the "42", "àéuazeDF" corpus names
  • and attempt to start the import the "Nom du corpus* ..." label background must go red

MD: OK Linux64

History

#1 Updated by Serge Heiden almost 5 years ago

  • Subject changed from TBX: 0.7.6, corpus import or corpus load must not accept invalid corpus names to TXM: 0.7.6, corpus import or corpus load must not accept invalid corpus names

#2 Updated by Matthieu Decorde almost 5 years ago

  • % Done changed from 0 to 30
MD: in the import editor :
  • When user select the source directory : the generated corpus ID manages corpus with a name beginning with a digit: 0..9.
  • When user start the import : the corpus ID is validated with the [A-Z][-A-Z0-9]* regular expression

#3 Updated by Matthieu Decorde over 4 years ago

  • Subject changed from TXM: 0.7.6, corpus import or corpus load must not accept invalid corpus names to TXM: 0.7.6, corpus import must not accept invalid corpus names
  • Description updated (diff)
  • Category changed from UI to Import
  • Target version changed from TXM 0.7.7 to TXM 0.7.6

#4 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)
  • % Done changed from 30 to 80

#5 Updated by Sebastien Jacquot over 4 years ago

  • Target version changed from TXM 0.7.6 to TXM 0.7.7

#6 Updated by Matthieu Decorde over 4 years ago

  • Status changed from New to Feedback

#7 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)

#8 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)

#9 Updated by Sebastien Jacquot about 4 years ago

Checked, corpus is not imported but some directories are created, see: #1290

#10 Updated by Matthieu Decorde about 4 years ago

  • Description updated (diff)
  • % Done changed from 80 to 90

Also available in: Atom PDF