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

Implement index files made public with respective bam file

        Details

        • Type: New Feature
        • Status: To-Do (View Workflow)
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
          None

          Description

          Situation: When I uploaded bam files and their indexes to CyVerse/BioViz Connect and then made the bam files public, the index should have also become public automatically. See linked issue below. This does not appear to have happened.

          Task: Investigate if bam index files are automatically being made public when their respective bam file is made public. If the indexes are not becoming public, then change this ticket to a "Fix" issue and address the issue.

          Implement a change where bam index files become public when a user makes the respective bam file public in the Manage Link right panel.

            Attachments

              Issue Links

              blocks

              Improvement - An improvement or enhancement to an existing feature or task. IGBF-1654 Make index files public automatically

              • Major - Major loss of function.
              • Closed

                Activity

                Hide
                Permalink
                nfreese Nowlan Freese added a comment -

                The IGBF-1654 ticket was part of the original build of BioViz Connect prior to moving to Django. The functionality of 1654 was not copied over to the current version of BioViz Connect, and the code would need to be re-implemented in its entirety, so this is not a bug but would instead be a new feature.

                I have made this ticket an implement ticket and have moved it to the backlog as it is a good idea to eventually implement.

                Show
                nfreese Nowlan Freese added a comment - The IGBF-1654 ticket was part of the original build of BioViz Connect prior to moving to Django. The functionality of 1654 was not copied over to the current version of BioViz Connect, and the code would need to be re-implemented in its entirety, so this is not a bug but would instead be a new feature. I have made this ticket an implement ticket and have moved it to the backlog as it is a good idea to eventually implement.

                  People

                  • Assignee:
                    Unassigned
                    Reporter:
                    nfreese Nowlan Freese
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated: