Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
purescript-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 140
    • Issues 140
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • purescript-gargantext
  • Issues
  • #692

Closed
Open
Opened Sep 17, 2024 by Grégoire Locqueville@glocqueville
  • Report abuse
  • New issue
Report abuse New issue

Remove the option for users to import term lists from TSV files

Summary

The interface currently supports importing a term list from a TSV file. This option should be removed.

Steps to reproduce

  • Create a corpus
  • Click on the flower of the corpus's Terms subnode
  • Click the "Upload" action

What happens

The file format dropdown features the "TSV" option alongside the "JSON" one. Importing a terms list from a TSV file might already be buggy, and it will become buggy anyway once nested subterms become possible.

What should happen

There should be no option in the dropdown list to import terms from a TSV file.

Note that the option to import a corpus from a TSV file is not in question here, only the option to import terms from a TSV file should be removed.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/purescript-gargantext#692