feature request #8182
show blast search result
0%
Description
the json result of the blast search should be displayed and the accession number needs to be a link to the corresponding specimen.
The search result should be displayed as a table with title of the result, genetic accession number, % coverage, length (t.b.c.)
the name should be shortened because sometimes it is too long (for example show the first 10 characters)
more details could be displayed in a details field.
Clicking on the genetic accession number should open a view with the hierarchy of the derived unit of the sequence (like the tree entry in specimen view)
Related issues
Associated revisions
implement blast search table for the result
ref #8182 sloving problems with blast search menu items and renaming constants
remove blast tab if blast is not enabled
ref #8182: fix error ín cdm_dataportal_preprocess_menu_local_tasks()
ref #8182: adapt occurrence DTOs to use them in details page of blast result
ref #8182: specimen tree is collapsable, blast result table with clickable details
ref #8182: remove local server for blast ws and add collabsible rows in specimen table and blast result table
ref #8182: handle not existing dna for accession number
ref #8182: add link to ncbi for blast result
ref #8182: add header to failed response
ref #8182: accession number is required in webservice
ref #8182: minor
ref #8182: Dna should be DNA
ref #8182: use bgbm-import instead of ip address
History
#1 Updated by Katja Luther over 2 years ago
- Related to feature request #7433: new service method to get specimen by genetic AccessionNumber added
#2 Updated by Katja Luther over 2 years ago
- Status changed from New to In Progress
- Target version changed from Release 5.7 to Release 5.8
#3 Updated by Andreas Müller about 2 years ago
is this ready or should we create ticket for open issues?
#4 Updated by Katja Luther about 2 years ago
- Description updated (diff)
#5 Updated by Katja Luther about 2 years ago
- Description updated (diff)
#6 Updated by Andreas Müller 7 months ago
is this still an open issue? Should it be reviewed? Should open issues be moved to new ticket?
Is there an example link for the result?
#7 Updated by Katja Luther 27 days ago
- Target version changed from Release 5.8 to Release 5.27
need to have a look whether this is completely fixed.
