Ticket #70 (closed defect: fixed)

Opened 18 months ago

Last modified 16 months ago

subspecific genetic lineage vs. infraspecific name+rank

Reported by: pyilmaz Owned by: pyilmaz
Priority: major Component: MIxS general
Version: 5.0 Keywords:
Cc: Sensitive: no

Description

PY: I honestly don’t see the difference between the three fields. I think it was an oversight when the environmental packages were made by other teams, and the field got duplicated.
In this case, my tendency is to keep the subspecific genetic lineage, because that is a field from the MIxS-core. We can work the definition of it further, and perhaps tweak the name a little bit if that’s necessary.

CH: I like the two fields ("infraspecific name' + ' infraspecific rank') because that gives explicit indication of the type of subspecies rank, e.g.
infraspecific rank= Biovar/cultivar/serovar/subspecies etc....
infraspecific name= bob or nigel or abc123
so unless the "subspecific genetic lineage" has the format defintition to include that info it maybe insufficient. eg.
subspecific genetic lineage = abc123
or
subspecific genetic lineage = biovar:abc123

Change History

comment:1 Changed 18 months ago by pyilmaz

  • Status changed from new to assigned

I'll extend the defintion of subspecific genetic lineage, so that rank is given

comment:2 Changed 16 months ago by pyilmaz

  • Status changed from assigned to closed
  • Resolution set to fixed

Subspecific genetic lineage refers to bacteria, eukaryote etc.. that is being sequences, while the infraspecific lineage/rank refers to hosts that these maybe living on/in. Improved the definition of subspecific lineage, but keeping the others as is

Note: See TracTickets for help on using tickets.