• Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.1
    • Component/s: None
    • Labels:
    • Sprint:
      BRCO - r1.4.1


      Comments from Michaela:

      My question is this: I looked at lPCM (precuneus cortex) and its subhierarchy. When I click on lPCM, the region is highlighted in pink, which is great. When I click on a subhierarchy class, let's say a pathway (eg Galactose metabolism, IEV_0001418), then the left PCM is still pink and the right PCM is red. This reflects that BRCO doesn't distinguish between left and right,doesn't it? This is great, too. Additionally, I see a blue arrow pointing to a different brain area. Is this an example of a pathway that is located in more than 1 position in the hierarchy? A pathway that is active in more than 1 region? I have the difficulty, being ignorant where each of the specific brain regions are spatially located in the brain, that I am unable to understand to what region the blue arrow points. But that is probably my personal ignorance of the brain anatomy..... ;-(

      This is actually comment #1, is there any way to make people like me understand which region is affected? A possible solution that I can see is that whenever more than 1 hierarchy position is involved, all of the tree positions are expanded automatically so the user can look up the positions inside the tree. Do you understand what I mean? I am not sure if I was clear enough...

      My second comment is a rather trivial one: I think it would be better to leave the label inside the tree itself. As it is now, people see URIs, which is ok from an ontology point of view, but it doesn't mean much to the user. Can we have this the other way round? Label in the tree and URI in the on-mouse-over? I think that would be great.




            • Assignee:
              lia.domide Lia Domide
              tester TVB Testing environment
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Time Tracking

                Original Estimate - 4 hours
                Remaining Estimate - 0 minutes
                Time Spent - 3 hours Time Not Required