Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1.5
-
Epic Link:
-
Sprint:Spring 9 : 25 May to 8 Jun
Description
The genome dashboard (see https://bioviz.org/genome-dashboard) displays images of different species that users can click on to trigger loading of the corresponding genome into IGB.
Currently, our convention is that we use the genius and species name to determine the name of the image to be loaded for a given species.
For instance, we use
C_sativa
in the image name for the plant Camelina sativa, an oilseed plant used since ancient times to make oil for lamps and ointments for the body. In modern times, we use it to make a kind of aviation fuel. It also is a very tasty cooking oil for dishes such as falafel.
However, the image name used has name collision with another plant species – Cannabis sativa – also used since ancient times to make things like rope and also a mood-enhancing, smokeable product enjoyed by many in Canada, California, Colorado, and many other places.
This name collision is a problem and affects other species, as well.
For this task, look into what it would take to modify the current code to support both C. sativa's at the same time.
Deliverables:
Add some comments to this ticket explaining how the image selection works currently. Propose a change to the code, if such a change needs to be made.
Get some feedback on the proposed change from another developer. Proposed a revised code change accordingly. Then, implement the change.
Also, update the story points as needed to reflect the extent of the changes required.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1765 [ 17855 ] |
| Rank | Ranked higher |
| Description |
The genome dashboard (see https://bioviz.org/genome-dashboard) displays images of different species that users can click on to trigger loading of the corresponding genome into IGB.
Currently, our convention is that we use the genius and species name to determine the name of the image to be loaded for a given species. For instance, we use C_sativa in the image name for the plant Camelina sativa, an oilseed plant used since ancient times to make oil for lamps and ointments for the body. In modern times, we use it to make a kind of aviation fuel. It also is a very tasty cooking oil for dishes such as falafel. However, the image name used has name collision with another plant species -- Cannabis sativa -- also used since ancient times to make things like rope and also a mood-enhancing, smokeable product enjoyed by many in Canada, California, Colorado, and many other places. This name collision is a problem and affects other species, as well. For this task, look into what it would take to modify the current code to support both C. sativa's at the same time. Deliverables: Add some comments to this ticket explaining how the image selection works currently. Propose a change to the code, if such a change needs to be made. |
The genome dashboard (see https://bioviz.org/genome-dashboard) displays images of different species that users can click on to trigger loading of the corresponding genome into IGB.
Currently, our convention is that we use the genius and species name to determine the name of the image to be loaded for a given species. For instance, we use C_sativa in the image name for the plant Camelina sativa, an oilseed plant used since ancient times to make oil for lamps and ointments for the body. In modern times, we use it to make a kind of aviation fuel. It also is a very tasty cooking oil for dishes such as falafel. However, the image name used has name collision with another plant species -- Cannabis sativa -- also used since ancient times to make things like rope and also a mood-enhancing, smokeable product enjoyed by many in Canada, California, Colorado, and many other places. This name collision is a problem and affects other species, as well. For this task, look into what it would take to modify the current code to support both C. sativa's at the same time. Deliverables: Add some comments to this ticket explaining how the image selection works currently. Propose a change to the code, if such a change needs to be made. Get some feedback on the proposed change from another developer. Proposed a revised code change accordingly. Then, implement the change. |
| Story Points | 1 | 2 |
| Description |
The genome dashboard (see https://bioviz.org/genome-dashboard) displays images of different species that users can click on to trigger loading of the corresponding genome into IGB.
Currently, our convention is that we use the genius and species name to determine the name of the image to be loaded for a given species. For instance, we use C_sativa in the image name for the plant Camelina sativa, an oilseed plant used since ancient times to make oil for lamps and ointments for the body. In modern times, we use it to make a kind of aviation fuel. It also is a very tasty cooking oil for dishes such as falafel. However, the image name used has name collision with another plant species -- Cannabis sativa -- also used since ancient times to make things like rope and also a mood-enhancing, smokeable product enjoyed by many in Canada, California, Colorado, and many other places. This name collision is a problem and affects other species, as well. For this task, look into what it would take to modify the current code to support both C. sativa's at the same time. Deliverables: Add some comments to this ticket explaining how the image selection works currently. Propose a change to the code, if such a change needs to be made. Get some feedback on the proposed change from another developer. Proposed a revised code change accordingly. Then, implement the change. |
The genome dashboard (see https://bioviz.org/genome-dashboard) displays images of different species that users can click on to trigger loading of the corresponding genome into IGB.
Currently, our convention is that we use the genius and species name to determine the name of the image to be loaded for a given species. For instance, we use C_sativa in the image name for the plant Camelina sativa, an oilseed plant used since ancient times to make oil for lamps and ointments for the body. In modern times, we use it to make a kind of aviation fuel. It also is a very tasty cooking oil for dishes such as falafel. However, the image name used has name collision with another plant species -- Cannabis sativa -- also used since ancient times to make things like rope and also a mood-enhancing, smokeable product enjoyed by many in Canada, California, Colorado, and many other places. This name collision is a problem and affects other species, as well. For this task, look into what it would take to modify the current code to support both C. sativa's at the same time. Deliverables: Add some comments to this ticket explaining how the image selection works currently. Propose a change to the code, if such a change needs to be made. Get some feedback on the proposed change from another developer. Proposed a revised code change accordingly. Then, implement the change. Also, update the story points as needed to reflect the extent of the changes required. |
| Summary | Modify Genome Dashboard to allow different names for genome version images | Modify Genome Dashboard to avoid colliding image names for species |
| Summary | Modify Genome Dashboard to avoid colliding image names for species | Avoid colliding image names for species |
| Assignee | Chester Dias [ cdias1 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Attachment | Screenshot 2020-05-26 at 17.31.14.png [ 14739 ] |
| Attachment | Screenshot 2020-05-26 at 17.31.14.png [ 14739 ] |
| Attachment | Screenshot of proposed change.png [ 14740 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Comment | [ How is the image file name being determined currently? Are they hard-coded in util.js? ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Attachment | falseflax.png [ 14741 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Rank | Ranked higher |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Story Points | 2 | 1.5 |
| Assignee | Chester Dias [ cdias1 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Assignee | Chester Dias [ cdias1 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Chester Dias [ cdias1 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Assignee | Chester Dias [ cdias1 ] |
| Assignee | Philip Badzuh [ pbadzuh ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Assignee | Philip Badzuh [ pbadzuh ] | Chester Dias [ cdias1 ] |