You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to display the following columns:
Column Name
Minimum fetaure
json key
Always Visibly
Visible by default
Could be empty
Type
Description
Y
Y
checkbox
N
option used to select one or more species
Name
Y
name
Y
Y
N
String
Genus and Species name
Taxid
Y
taxon_id
Y
Y
N
Number
Taxonomic identifier
# assemblies
Y
num_assemblies
Y
Y
Y
Number
Number of assemblies for species.
N50
N
n50
N
Y
Y
Number
n50 value for best assembly, if any exist
Scaffolds
N
scaffolds
N
Y
Y
Number
number of scaffolds for best assembly, if any exist
Project
N
project
N
Y
Y
String
project(s) where the species is included
Progress
N
progress tag
N
Y
Y
List of String
progress of assembly construction
Assembly Data
N
tags_assembly
Y
N
Y
List of String
Tags indicating what assemblies exists
Genomic Data
N
tags_genomic
N
N
Y
List of String
Tags indicating what kind of raw genomic data exist
Transcriptomic Data
N
tags_transcriptomic
N
N
Y
List of String
Tags indicating what kind of raw transcriptomic data exist
Some thoughts:
For the first column, it could also be an option to instead have it possible to select multiple rows in the table by clicking on a row.
After the user has selected one or multiple species we need an intuitive way of providing the option to move to the Genome Page. Possible options could be, when at least one species have been selected:
a button appears.
a existing button goes from disable to enabled.
other suggestions?
We should maybe add the option of entering the Species Page, the name could be a link to that page.
I have divided the implementation into three phases:
Initial Setup – The goal of this phase is to get a basic version up and running. This will serve as the foundation for implementing other pages. I believe we have everything needed to generate the required data.
Enhancements using NCBI API – Once we have a simple page working, we will expand it by incorporating additional information from the NCBI REST API.
Additional Data Integration – In this final phase, we will integrate raw data and other generated information to enrich the content further.
The main goal to divide the implementation into multiple steps is to get a page up and running.
Initial Setup (Minimum feature)
The following columns should be included:
Name
Taxid
assemblies
And make it possible to select one or multiple species.
Enhancements using NCBI API
The following columns should be included:
N50
Scaffolds
In these step we need to extend the data extraction script to fetch more information from the NCBI API
Additional Data Integration
Project
Assembly Data
Genomic Data
Transcriptomic Data
Assemblies found in the s3 bucket
We extend the data extraction script to fetch information about raw data belonging to the assemblies. We should also look into adding path/displaying data from downstream analysis.
The text was updated successfully, but these errors were encountered:
List view
It would be useful to display the following columns:
Some thoughts:
I have divided the implementation into three phases:
The main goal to divide the implementation into multiple steps is to get a page up and running.
Initial Setup (Minimum feature)
The following columns should be included:
And make it possible to select one or multiple species.
Enhancements using NCBI API
The following columns should be included:
In these step we need to extend the data extraction script to fetch more information from the NCBI API
Additional Data Integration
We extend the data extraction script to fetch information about raw data belonging to the assemblies. We should also look into adding path/displaying data from downstream analysis.
The text was updated successfully, but these errors were encountered: