Details
-
Type:
Epic
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Epic Name:Connect Integrated Genome Browser and CyVerse
Description
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user.
Key features of the site:
- It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only.
- The site will be lightweight, requiring minimal resources, and will be easy to deploy.
- The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer
- The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer
- The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see.
This work is funded by an R01 grant to Ann Loraine: Linking Integrated Genome Browser and CyVerse
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Epic Child |
|
| Epic Child | IGBF-1484 [ 17570 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1487 [ 17573 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1487 [ 17573 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Rank | Ranked higher |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1667 [ 17757 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1742 [ 17832 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1802 [ 17892 ] |
| Epic Child | IGBF-1803 [ 17893 ] |
| Epic Child | IGBF-1810 [ 17900 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1962 [ 18053 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Workflow | Loraine Lab Workflow [ 18198 ] | Fall 2019 Workflow Update [ 18930 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Summary | Open CyVerse files in IGB via BioViz bridge | Open CyVerse files in IGB |
| Epic Name | Open CyVerse files in IGB via BioViz bridge | Open CyVerse files in IGB |
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-2028 [ 18119 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Workflow | Fall 2019 Workflow Update [ 18930 ] | Revised Fall 2019 Workflow Update [ 21056 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-2266 [ 18413 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-2266 [ 18413 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | IGBF-1962 [ 18053 ] |
| Epic Child |
|
| Epic Child |
|
| Assignee | Ann Loraine [ aloraine ] |
| Epic Child |
|
| Epic Child |
|
| Epic Status | To Do [ 10001 ] | Done [ 10003 ] |
| Summary | Open CyVerse files in IGB | Connect CyVerse to IGB |
| Summary | Connect CyVerse to IGB | Connect Integrated Genome Browser and CyVerse |
| Epic Name | Open CyVerse files in IGB | Connect Integrated Genome Browser and CyVerse |
| Description |
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user. *Key features of the site*: * It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only. * The site will be lightweight, requiring minimal resources, and will be easy to deploy. * The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer * The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer * The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see. |
| Description |
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user. *Key features of the site*: * It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only. * The site will be lightweight, requiring minimal resources, and will be easy to deploy. * The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer * The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer * The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see. |
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user. *Key features of the site*: * It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only. * The site will be lightweight, requiring minimal resources, and will be easy to deploy. * The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer * The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer * The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see. This work is funded by an R01 grant to Ann Loraine: [Linking Integrated Genome Browser and CyVerse |https://reporter.nih.gov/project-details/9750774] |
| Description |
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user. *Key features of the site*: * It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only. * The site will be lightweight, requiring minimal resources, and will be easy to deploy. * The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer * The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer * The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see. This work is funded by an R01 grant to Ann Loraine: [Linking Integrated Genome Browser and CyVerse |https://reporter.nih.gov/project-details/9750774] |
Starting January 2019, we began creating Web site middleware to let Integrated Genome Browser users visualize data using CyVerse resources. By connecting the rich client IGB with cloud resources managed by the CyVerse project, we can give IGB users more power to execute compute-intensive visual analytics algorithms "in the cloud" and then visualize the results within IGB.
Our first idea was to build the CyVerse access component into IGB itself as an IGB App. However, after looking into the challenges, we realized that a far better approach would be to create an intermediary, a Web site, that would manage interactions with the CyVerse resources on behalf of the user. *Key features of the site*: * It will manage user logins using OAuth, ensuring that our site gains no knowledge of a user's password. Our site will learn their user name, but that is all. All user account management will occur using CyVerse resources only. * The site will be lightweight, requiring minimal resources, and will be easy to deploy. * The site will enable users to launch compute-intensive visual analytics functions, including: creating scaled coverage graphs to enable visual inspection of differential gene expression across samples and sample types, a function that is currently very difficult and inconvenient for user's to execute on their own, using their personal computer * The site will enable users to store data in the cloud, in their CyVerse accounts, but still be able to visualize the data within IGB, running on the user's personal computer * The site will enable users to annotate data, adding information about the genome version (if relevant) and information about how the data should appear when loaded into IGB. These attributes will enable other users looking at the same data to see what the data's owners also see. This work is funded by an R01 grant to Ann Loraine: [Linking Integrated Genome Browser and CyVerse|https://reporter.nih.gov/project-details/9750774] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| 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 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |