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
Hello! I'm not sure if this feature already exists, but we have a fair number of genomes. Nearly 20+, haplotype-resolved. As we get new sequencing data and I return to further curate the actual assemblies, it would be excellent if there was a way to version control them. So for example, if I click the name Genome1A, and I have another (improved version), It'd be great if our users could still select Genome1A, but see the new version, in addition to the old.
For example Genome1A.version1 and Genome1.version2. They could click version 1 or version 2. Along these lines, a meta data descriptor to describe the version publication date/field for describing new changes.
I ask because the current genomes we have already make the drop down menu kind of intense, and multiplying it by 2, with V2 names, may be a somewhat overwhelming list of names for our end users.
Curious to hear your thoughts!
Cheers,
Sam
The text was updated successfully, but these errors were encountered:
this is a good idea.... I have an older issue here to add generic 'grouping' to assemblies #1883
i'm not sure the visual mockup in that issu is a great solution, it might even be better as a 'tree' with (at least one level...if not more) of subcategories and such
Hello! I'm not sure if this feature already exists, but we have a fair number of genomes. Nearly 20+, haplotype-resolved. As we get new sequencing data and I return to further curate the actual assemblies, it would be excellent if there was a way to version control them. So for example, if I click the name Genome1A, and I have another (improved version), It'd be great if our users could still select Genome1A, but see the new version, in addition to the old.
For example Genome1A.version1 and Genome1.version2. They could click version 1 or version 2. Along these lines, a meta data descriptor to describe the version publication date/field for describing new changes.
I ask because the current genomes we have already make the drop down menu kind of intense, and multiplying it by 2, with V2 names, may be a somewhat overwhelming list of names for our end users.
Curious to hear your thoughts!
Cheers,
Sam
The text was updated successfully, but these errors were encountered: