Details

      Description

      The UDW should have a parameter called discoverRootLocationId. When this parameter is set, the UDW does not allow to pick a Content this is not in the corresponding subtree.

      1. Content_Tree_Browser_1_new.png
        120 kB
      2. Content_Tree_Browser_1.1.png
        120 kB
      3. Content_Tree_Browser_2_new.png
        219 kB
      4. Content_Tree_Browser_2.1.png
        219 kB
      5. UnderContentStructure.png
        56 kB
      6. UnderMediaLibrary.png
        53 kB

        Activity

        Hide
        Stéphane Diot added a comment - - edited

        [~damien.pobel@ez.no] Roland Benedetti Inaki Juaniz-Velilla Bertrand Dunogier Supriya Bhargava
        I'm currently working on the UDW to start with a defined root location.

        As reminder : this is used when we don't want the user to be able to navigate in the locations and sub-locations above the defined root. For example the simplest use case here is when we are in "Media Library" we want to see only the locations in Medias when browsing contents.

        But I was a bit confused by the fact that there are nothing to warn the user that he is under a specific root (see the 2 attached pictures, one is under Content Structure, the other under Media Library, we can see the listed locations aren't the same but nothing to tell the user he is under a specific root.

        Here is a screencast to see the current behavior of the feature: https://youtu.be/D0h6teVxqgY

        Do you have any suggestions guys ?

        Show
        Stéphane Diot added a comment - - edited [~damien.pobel@ez.no] Roland Benedetti Inaki Juaniz-Velilla Bertrand Dunogier Supriya Bhargava I'm currently working on the UDW to start with a defined root location. As reminder : this is used when we don't want the user to be able to navigate in the locations and sub-locations above the defined root. For example the simplest use case here is when we are in "Media Library" we want to see only the locations in Medias when browsing contents. But I was a bit confused by the fact that there are nothing to warn the user that he is under a specific root (see the 2 attached pictures, one is under Content Structure, the other under Media Library, we can see the listed locations aren't the same but nothing to tell the user he is under a specific root. Here is a screencast to see the current behavior of the feature: https://youtu.be/D0h6teVxqgY Do you have any suggestions guys ?
        Hide
        Roland Benedetti added a comment -

        This is good topic for user testing
        I am a bit scared the subtitle is not enough.
        Personally, I think what would be better is the main title, with a clear action:

        "Browsing #name_of_the_subtree#"

        Using "content tree" is not a good idea as we don't use a clear tree visualization any more.

        So I'd go for "Browsing ###", and I'm even wondering if we should not include the path so that the user knows exactly where he is, no?

        • Browsing Media Library
        • Browsing Users / Administrator users
        • Browsing Content Structure / Food / Recipes
        Show
        Roland Benedetti added a comment - This is good topic for user testing I am a bit scared the subtitle is not enough. Personally, I think what would be better is the main title, with a clear action: "Browsing #name_of_the_subtree#" Using "content tree" is not a good idea as we don't use a clear tree visualization any more. So I'd go for "Browsing ###", and I'm even wondering if we should not include the path so that the user knows exactly where he is, no? Browsing Media Library Browsing Users / Administrator users Browsing Content Structure / Food / Recipes
        Hide
        Stéphane Diot added a comment -

        Roland Benedetti You mean a dynamic path updated when user navigate through different explorer levels ? Should it be used for every instance of the UDW ( for example a user copying a content to a different location using the UDW should also have this path shown ? ) ? Or only when we have defined a specific root to start the UDW to ?

        Show
        Stéphane Diot added a comment - Roland Benedetti You mean a dynamic path updated when user navigate through different explorer levels ? Should it be used for every instance of the UDW ( for example a user copying a content to a different location using the UDW should also have this path shown ? ) ? Or only when we have defined a specific root to start the UDW to ?
        Hide
        Roland Benedetti added a comment -

        No, it would not have to be dynamic, that's not what I had in mind.
        I thought it should be the path of the location where you opened the Browser, basically the virtual root for this instance.
        Does it make sens?
        I might miss something but I think that if the user browse with the UDW in a gallery which is for instance in /Media Library/Assets/, he would like to know that information as well.
        Supriya Bhargava what do you think?

        Happy to chat on slack if needs be.

        Show
        Roland Benedetti added a comment - No, it would not have to be dynamic, that's not what I had in mind. I thought it should be the path of the location where you opened the Browser, basically the virtual root for this instance. Does it make sens? I might miss something but I think that if the user browse with the UDW in a gallery which is for instance in /Media Library/Assets/, he would like to know that information as well. Supriya Bhargava what do you think? Happy to chat on slack if needs be.
        Hide
        Stéphane Diot added a comment - - edited

        Roland Benedetti Ok that make sense to me, thanks for the explanation.
        Supriya Bhargava Roland Benedetti Inaki Juaniz-Velilla So should I go for the title or the sub-title place ? (I know it's a detail, but from the technical side it will be two very different way to do... Sub-title place is definitely easier but the two are possible of course)

        Show
        Stéphane Diot added a comment - - edited Roland Benedetti Ok that make sense to me, thanks for the explanation. Supriya Bhargava Roland Benedetti Inaki Juaniz-Velilla So should I go for the title or the sub-title place ? (I know it's a detail, but from the technical side it will be two very different way to do... Sub-title place is definitely easier but the two are possible of course)
        Hide
        Roland Benedetti added a comment -

        Good question. I actually think the search should be limited to the subtree too.
        I have no idea if it's possible, but it would make more sense to provide a consistent user experience.

        For the 1st question, ellipses, but I'll let Inaki answer on that. I know he already played a lot with this kind of interactions.

        Roland

        Show
        Roland Benedetti added a comment - Good question. I actually think the search should be limited to the subtree too. I have no idea if it's possible, but it would make more sense to provide a consistent user experience. For the 1st question, ellipses, but I'll let Inaki answer on that. I know he already played a lot with this kind of interactions. Roland
        Hide
        Bertrand Dunogier added a comment -

        One alternative I did think of would be to show the upper levels (the one above the starting one), but disable interaction on them. They'd get scrolled out to the left, and wouldn't be too intrusive, and would indicate without any doubt where you are located in the tree.

        Furthermore, based on discussions with Stephane, it wouldn't require many changes.

        Show
        Bertrand Dunogier added a comment - One alternative I did think of would be to show the upper levels (the one above the starting one), but disable interaction on them. They'd get scrolled out to the left, and wouldn't be too intrusive, and would indicate without any doubt where you are located in the tree. Furthermore, based on discussions with Stephane, it wouldn't require many changes.
        Show
        Stéphane Diot added a comment - PR : https://github.com/ezsystems/PlatformUIBundle/pull/814

          People

          • Assignee:
            Unassigned
            Reporter:
            Damien Pobel (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: