Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-3994

Send a custom event to track more about the Galaxy landing page in Bioviz

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Send a custom event to track more about the Galaxy landing page in Bioviz. Like which page the user lands on when coming from Galaxy and whether they can successfully run IGB and get the Success page in Galaxy. For this, send page view events for both scenarios in viewing the Galaxy page, successfully running IGB: "Galaxy bridge - IGB running" and for the IGB not running scenario: "Galaxy bridge - IGB not running".

        Attachments

          Issue Links

            Activity

            Hide
            nfreese Nowlan Freese added a comment -

            Tested on Mac using Chrome. I can see Galaxy bridge - IGB running, Galaxy bridge - IGB not running, Galaxy bridge - Genome Version Not Attached, and Welcome Galaxy User in Google Analytics. I am also not sure how to test the Galaxy bridge - File Not Found.

            Closing ticket.

            https://usegalaxy.org/display_application/bbd44e69cb8906b5bf8e2687bc4163b6/igb_bed/View -> IGB is running -> Galaxy bridge - IGB running

            https://usegalaxy.org/display_application/bbd44e69cb8906b5bf8e2687bc4163b6/igb_bed/View -> IGB is not running -> Galaxy bridge - IGB not running

            https://usegalaxy.org/display_application/bbd44e69cb8906b5607af416a6679b9e/igb_bed/View -> IGB is running or not running, no dbkey -> Galaxy bridge - Genome Version Not Attached

            Show
            nfreese Nowlan Freese added a comment - Tested on Mac using Chrome. I can see Galaxy bridge - IGB running, Galaxy bridge - IGB not running, Galaxy bridge - Genome Version Not Attached, and Welcome Galaxy User in Google Analytics. I am also not sure how to test the Galaxy bridge - File Not Found. Closing ticket. https://usegalaxy.org/display_application/bbd44e69cb8906b5bf8e2687bc4163b6/igb_bed/View -> IGB is running -> Galaxy bridge - IGB running https://usegalaxy.org/display_application/bbd44e69cb8906b5bf8e2687bc4163b6/igb_bed/View -> IGB is not running -> Galaxy bridge - IGB not running https://usegalaxy.org/display_application/bbd44e69cb8906b5607af416a6679b9e/igb_bed/View -> IGB is running or not running, no dbkey -> Galaxy bridge - Genome Version Not Attached
            Hide
            ann.loraine Ann Loraine added a comment - - edited

            Update:

            To test:

            • Probably need to wait for one day to pass for Google Analytics to update
            • Log into Google Analytics and observe the BioViz.org Web site google analytics statistics by selecting the "Pages and screens" option and then one of the "Page title" views in the table you will see on this page
            • You should now see the following pages getting tracked, under the following scenarios:

            Page title "Galaxy bridge - IGB running" tracked when a user clicks "view in IGB" link on a Galaxy data set page and IGB is running on the user's computer.

            Page title "Galaxy bridge - IGB not running" tracked when a user clicks "view in IGB" link on a Galaxy data set page and IGB is *NOT* running on the user's computer.

            Page title "Galaxy bridge - File Not Found" may or may not get tracked when a user clicks "view in IGB" link on a Galaxy data set page. We are not sure what workflow triggers this event. So far as we know, the only way that this event / page would appear is if the data set in Galaxy did not exist, but how could that happen? The only way to "get to" the Galaxy Bridge page is to click on the "View in IGB" link on a data set page. For that page to exist, the data set would have to exist, also.

            Page title ""Galaxy bridge - Genome Version Not Attached" tracked when a user clicks "view in IGB" link on a Galaxy data set page and the data set does not have a "dbkey" variable attached to the Galaxy data set within the Galaxy system.

            Unfortunately, I don't know how to test that the above configurations are working as expected because I don't know how a tester can track their own interactions, which I think is what we would need to be able to do to ensure that the analytics is working the way we designed it to!

            Show
            ann.loraine Ann Loraine added a comment - - edited Update: Merged the PR to main branch in team repository - https://bitbucket.org/lorainelab/bioviz/src/main/ Ran bioviz playbooks to deploy the new bioviz javascript and html code to bioviz.org main site Ready for testing To test: Probably need to wait for one day to pass for Google Analytics to update Log into Google Analytics and observe the BioViz.org Web site google analytics statistics by selecting the "Pages and screens" option and then one of the "Page title" views in the table you will see on this page You should now see the following pages getting tracked, under the following scenarios: Page title "Galaxy bridge - IGB running" tracked when a user clicks "view in IGB" link on a Galaxy data set page and IGB is running on the user's computer. Page title "Galaxy bridge - IGB not running" tracked when a user clicks "view in IGB" link on a Galaxy data set page and IGB is * NOT * running on the user's computer. Page title "Galaxy bridge - File Not Found" may or may not get tracked when a user clicks "view in IGB" link on a Galaxy data set page. We are not sure what workflow triggers this event. So far as we know, the only way that this event / page would appear is if the data set in Galaxy did not exist, but how could that happen? The only way to "get to" the Galaxy Bridge page is to click on the "View in IGB" link on a data set page. For that page to exist, the data set would have to exist, also. Page title ""Galaxy bridge - Genome Version Not Attached" tracked when a user clicks "view in IGB" link on a Galaxy data set page and the data set does not have a "dbkey" variable attached to the Galaxy data set within the Galaxy system. Unfortunately, I don't know how to test that the above configurations are working as expected because I don't know how a tester can track their own interactions, which I think is what we would need to be able to do to ensure that the analytics is working the way we designed it to!
            Hide
            jsirigin Jaya Sravani Sirigineedi (Inactive) added a comment -

            As discussed, we will be leaving the testing part of the fileNotFoundError scenario for now as we weren't able to replicate it. But the tracking for it is added in the code, we will be able to track it if a user lands in that scenario. Also, we decided to keep the original event as it is and not remove it. Tested the scenarios in Safari as well. Everything working as expected, except the navigation bar and footer aren't visible in Safari, I also observed that when we change the URL from HTTP to HTTPS it works again, created a new ticket for investigating this (IGBF-3996). Got the code reviewed from Ann Loraine. Submitting the PR: https://bitbucket.org/lorainelab/bioviz/pull-requests/164

            Show
            jsirigin Jaya Sravani Sirigineedi (Inactive) added a comment - As discussed, we will be leaving the testing part of the fileNotFoundError scenario for now as we weren't able to replicate it. But the tracking for it is added in the code, we will be able to track it if a user lands in that scenario. Also, we decided to keep the original event as it is and not remove it. Tested the scenarios in Safari as well. Everything working as expected, except the navigation bar and footer aren't visible in Safari, I also observed that when we change the URL from HTTP to HTTPS it works again, created a new ticket for investigating this ( IGBF-3996 ). Got the code reviewed from Ann Loraine . Submitting the PR: https://bitbucket.org/lorainelab/bioviz/pull-requests/164
            Hide
            jsirigin Jaya Sravani Sirigineedi (Inactive) added a comment - - edited

            Made changes to send pageview event to Google Analytics for which scenario the galaxy page is loaded. I have added the error scenarios as well for fileNotFoundError and error-container (genome version not found) divs that aren't mentioned in the description. Tested, three scenarios are working, but I am not able to test the fileNotFoundError scenario, unable to replicate it. I have the following two questions:

            • How to get the fileNotFoundError scenario?
            • After these changes do we want the original pageview event, that just says "Welcome Galaxy User"?

            Here is the updated code: https://bitbucket.org/jaya-sravani/bioviz/branch/IGBF-3994

            Show
            jsirigin Jaya Sravani Sirigineedi (Inactive) added a comment - - edited Made changes to send pageview event to Google Analytics for which scenario the galaxy page is loaded. I have added the error scenarios as well for fileNotFoundError and error-container (genome version not found) divs that aren't mentioned in the description. Tested, three scenarios are working, but I am not able to test the fileNotFoundError scenario, unable to replicate it. I have the following two questions: How to get the fileNotFoundError scenario? After these changes do we want the original pageview event, that just says "Welcome Galaxy User"? Here is the updated code: https://bitbucket.org/jaya-sravani/bioviz/branch/IGBF-3994

              People

              • Assignee:
                jsirigin Jaya Sravani Sirigineedi (Inactive)
                Reporter:
                jsirigin Jaya Sravani Sirigineedi (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: