Organization and Location of index pages

Hello,

Smart Proxy index page is getting taxonomy information because they are
usually deployed on remote locations when taxonomy support is enabled in
Foreman [1]. It looks like for the initial implementation, we are going
to simply add Organization and Location columns.

There is a need to implement similar for most relevant index pages. The
question is how to do this from the UX perspective. We need to solve
these issues:

  • There are multiple choices for most resources, how to present them
    efficiently?
  • Taxonomy must not be visible when Org/Loc are disabled by
    configuration.
  • When Organization or/and Location is selected in the Org top-left
    selectors, this information is useless. In this case, we should
    probably hide it.
  • Two more columns takes lot of horizontal space, some pages might not
    have enough room, or it would lead to other columns as unreadable.

It looks like we will need to find a way how to present this cleanly.
The most obvious implementation is to simply show two new columns
Organization and Location and hide them when taxonomy is selected via
the selector. We'd perhaps need to implement something like "weak
columns" - those could be removed, if more space is needed.

Second option is to give total flexibility to users so they can define
their own columns for each individual index table. This will be more
challenging task, but it's up to users what to put on the pages. We'd
still need some logic to hide/show taxonomy based on the selector. This
should be perhaps configurable (some users might prefer to see them all
the time).

What are your opinions on that?

[1] https://github.com/theforeman/foreman/pull/3054

··· -- Later, Lukas #lzap Zapletal

> Hello,
>
> Smart Proxy index page is getting taxonomy information because they are
> usually deployed on remote locations when taxonomy support is enabled in
> Foreman [1]. It looks like for the initial implementation, we are going
> to simply add Organization and Location columns.

I think it would be great to "fix" Any Context in this way: When in Any Context, the org/loc columns are shown and all resources are displayed. Big +1 from me.

>
> There is a need to implement similar for most relevant index pages. The
> question is how to do this from the UX perspective. We need to solve
> these issues:
>
> - There are multiple choices for most resources, how to present them
> efficiently?

Probably ellipsis with tooltip of full list? Agree that multiple orgs/locs will quickly outgrow the column.

> - Taxonomy must not be visible when Org/Loc are disabled by
> configuration.
> - When Organization or/and Location is selected in the Org top-left
> selectors, this information is useless. In this case, we should
> probably hide it.

+1

> - Two more columns takes lot of horizontal space, some pages might not
> have enough room, or it would lead to other columns as unreadable.

If they are taxable, then I'd say columns required.

>
> It looks like we will need to find a way how to present this cleanly.
> The most obvious implementation is to simply show two new columns
> Organization and Location and hide them when taxonomy is selected via
> the selector. We'd perhaps need to implement something like "weak
> columns" - those could be removed, if more space is needed.
>
> Second option is to give total flexibility to users so they can define
> their own columns for each individual index table. This will be more
> challenging task, but it's up to users what to put on the pages. We'd
> still need some logic to hide/show taxonomy based on the selector. This
> should be perhaps configurable (some users might prefer to see them all
> the time).

This has been a long-standing RFE. How I describe it is as "views". Have the dropdown selector to the right of the search fields (or another selector) allow a view to be selected. A view would determine which columns were displayed in the list. The simplest example is in katello where I want to sometimes view content hosts for their errata and other times for their subscription info. Ideally, this "view" choice would trickle down to the API level and allow optimization of results that could greatly impact speed too. (eg. If one doesn't care about current errata count, there is no need to calculate that for the json result.)

··· ----- Original Message -----

What are your opinions on that?

[1] https://github.com/theforeman/foreman/pull/3054


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

> Hello,
>
> Smart Proxy index page is getting taxonomy information because they are
> usually deployed on remote locations when taxonomy support is enabled in
> Foreman [1]. It looks like for the initial implementation, we are going
> to simply add Organization and Location columns.
>

I am failing to see what this adds. Or better put, what question does this
answer when I am viewing an index page. What action am I trying to take
that I would come to the index page and analyze, in bulk, the orgs and
locations of smart proxies? In general, this should be on a case by case
basis where it makes sense, where it enhances a users workflow.

··· On Tue, Jan 19, 2016 at 6:03 AM, Lukas Zapletal wrote:

There is a need to implement similar for most relevant index pages. The
question is how to do this from the UX perspective. We need to solve
these issues:

  • There are multiple choices for most resources, how to present them
    efficiently?
  • Taxonomy must not be visible when Org/Loc are disabled by
    configuration.
  • When Organization or/and Location is selected in the Org top-left
    selectors, this information is useless. In this case, we should
    probably hide it.
  • Two more columns takes lot of horizontal space, some pages might not
    have enough room, or it would lead to other columns as unreadable.

It looks like we will need to find a way how to present this cleanly.
The most obvious implementation is to simply show two new columns
Organization and Location and hide them when taxonomy is selected via
the selector. We’d perhaps need to implement something like “weak
columns” - those could be removed, if more space is needed.

Second option is to give total flexibility to users so they can define
their own columns for each individual index table. This will be more
challenging task, but it’s up to users what to put on the pages. We’d
still need some logic to hide/show taxonomy based on the selector. This
should be perhaps configurable (some users might prefer to see them all
the time).

What are your opinions on that?

[1] https://github.com/theforeman/foreman/pull/3054


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

> There is a need to implement similar for most relevant index pages. The

A need is too strong of a word. AFAIK nobody even opened a ticket
before the current PR was open.

> - There are multiple choices for most resources, how to present them
> efficiently?
> - Taxonomy must not be visible when Org/Loc are disabled by
> configuration.
> - When Organization or/and Location is selected in the Org top-left
> selectors, this information is useless. In this case, we should
> probably hide it.
> - Two more columns takes lot of horizontal space, some pages might not
> have enough room, or it would lead to other columns as unreadable.
>
> It looks like we will need to find a way how to present this cleanly.
> The most obvious implementation is to simply show two new columns
> Organization and Location and hide them when taxonomy is selected via
> the selector. We'd perhaps need to implement something like "weak
> columns" - those could be removed, if more space is needed.
>
> Second option is to give total flexibility to users so they can define
> their own columns for each individual index table. This will be more
> challenging task, but it's up to users what to put on the pages. We'd
> still need some logic to hide/show taxonomy based on the selector. This
> should be perhaps configurable (some users might prefer to see them all
> the time).
>
> What are your opinions on that?

Sorry to be blunt but I don't think maintaining either of the options is
really worth it, especially for most tables. In case I'm missing
something and this should be shown:

'weak-columns' sounds OK at first, and it's something we have through
Patternfly. Just use the 'lg', 'xs' etc attributes on every column to
customize on what kind of display they should be shown.

Writing a system for most other tables is just adding more code we have
to maintain and potential bugs for (what I see as) little benefit.
I only see value for users to customize the Hosts table, and they can do
that through https://github.com/GregSutcliffe/foreman_column_view - maybe
we can improve that and take it into core.

··· > > [1] https://github.com/theforeman/foreman/pull/3054 > > -- > Later, > Lukas #lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.


Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

>
>
>
>> Hello,
>>
>> Smart Proxy index page is getting taxonomy information because they are
>> usually deployed on remote locations when taxonomy support is enabled in
>> Foreman [1]. It looks like for the initial implementation, we are going
>> to simply add Organization and Location columns.
>>
>
> I am failing to see what this adds. Or better put, what question does this
> answer when I am viewing an index page. What action am I trying to take
> that I would come to the index page and analyze, in bulk, the orgs and
> locations of smart proxies? In general, this should be on a case by case
> basis where it makes sense, where it enhances a users workflow.
>
>
the ask is that people identify proxies based on locations mostly,
therefore it would be useful to display that attribute.

··· On Tue, Jan 19, 2016 at 3:36 PM, Eric D Helms wrote: > On Tue, Jan 19, 2016 at 6:03 AM, Lukas Zapletal wrote:

There is a need to implement similar for most relevant index pages. The
question is how to do this from the UX perspective. We need to solve
these issues:

  • There are multiple choices for most resources, how to present them
    efficiently?
  • Taxonomy must not be visible when Org/Loc are disabled by
    configuration.
  • When Organization or/and Location is selected in the Org top-left
    selectors, this information is useless. In this case, we should
    probably hide it.
  • Two more columns takes lot of horizontal space, some pages might not
    have enough room, or it would lead to other columns as unreadable.

It looks like we will need to find a way how to present this cleanly.
The most obvious implementation is to simply show two new columns
Organization and Location and hide them when taxonomy is selected via
the selector. We’d perhaps need to implement something like “weak
columns” - those could be removed, if more space is needed.

Second option is to give total flexibility to users so they can define
their own columns for each individual index table. This will be more
challenging task, but it’s up to users what to put on the pages. We’d
still need some logic to hide/show taxonomy based on the selector. This
should be perhaps configurable (some users might prefer to see them all
the time).

What are your opinions on that?

[1] https://github.com/theforeman/foreman/pull/3054


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

> > There is a need to implement similar for most relevant index pages. The
>
> A need is too strong of a word. AFAIK nobody even opened a ticket
> before the current PR was open.
>
> > - There are multiple choices for most resources, how to present them
> > efficiently?
> > - Taxonomy must not be visible when Org/Loc are disabled by
> > configuration.
> > - When Organization or/and Location is selected in the Org top-left
> > selectors, this information is useless. In this case, we should
> > probably hide it.
> > - Two more columns takes lot of horizontal space, some pages might not
> > have enough room, or it would lead to other columns as unreadable.
> >
> > It looks like we will need to find a way how to present this cleanly.
> > The most obvious implementation is to simply show two new columns
> > Organization and Location and hide them when taxonomy is selected via
> > the selector. We'd perhaps need to implement something like "weak
> > columns" - those could be removed, if more space is needed.
> >
> > Second option is to give total flexibility to users so they can define
> > their own columns for each individual index table. This will be more
> > challenging task, but it's up to users what to put on the pages. We'd
> > still need some logic to hide/show taxonomy based on the selector. This
> > should be perhaps configurable (some users might prefer to see them all
> > the time).
> >
> > What are your opinions on that?
>
> Sorry to be blunt but I don't think maintaining either of the options is
> really worth it, especially for most tables. In case I'm missing
> something and this should be shown:
>
> 'weak-columns' sounds OK at first, and it's something we have through
> Patternfly. Just use the 'lg', 'xs' etc attributes on every column to
> customize on what kind of display they should be shown.
>
> Writing a system for most other tables is just adding more code we have
> to maintain and potential bugs for (what I see as) little benefit.
> I only see value for users to customize the Hosts table, and they can do
> that through https://github.com/GregSutcliffe/foreman_column_view - maybe
> we can improve that and take it into core.

I see a lot of value in allowing custom tables and seems like if it could be done for one table then the rest could use it easily too. The "adding more code" and "bugs" are what we do for a living. :slight_smile:

··· ----- Original Message -----

[1] https://github.com/theforeman/foreman/pull/3054


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

>
>>
>>
>>
>>> Hello,
>>>
>>> Smart Proxy index page is getting taxonomy information because they are
>>> usually deployed on remote locations when taxonomy support is enabled in
>>> Foreman [1]. It looks like for the initial implementation, we are going
>>> to simply add Organization and Location columns.
>>>
>>
>> I am failing to see what this adds. Or better put, what question does
>> this answer when I am viewing an index page. What action am I trying to
>> take that I would come to the index page and analyze, in bulk, the orgs and
>> locations of smart proxies? In general, this should be on a case by case
>> basis where it makes sense, where it enhances a users workflow.
>>
>>
> the ask is that people identify proxies based on locations mostly,
> therefore it would be useful to display that attribute.
>

That's fair, so I'd vote for implementing that and not going beyond that
scope via a column with a comma separated list for starters. We can always
iterate if users find they need more.

Eric

··· On Tue, Jan 19, 2016 at 9:06 AM, Ohad Levy wrote: > On Tue, Jan 19, 2016 at 3:36 PM, Eric D Helms > wrote: >> On Tue, Jan 19, 2016 at 6:03 AM, Lukas Zapletal wrote:

There is a need to implement similar for most relevant index pages. The
question is how to do this from the UX perspective. We need to solve
these issues:

  • There are multiple choices for most resources, how to present them
    efficiently?
  • Taxonomy must not be visible when Org/Loc are disabled by
    configuration.
  • When Organization or/and Location is selected in the Org top-left
    selectors, this information is useless. In this case, we should
    probably hide it.
  • Two more columns takes lot of horizontal space, some pages might not
    have enough room, or it would lead to other columns as unreadable.

It looks like we will need to find a way how to present this cleanly.
The most obvious implementation is to simply show two new columns
Organization and Location and hide them when taxonomy is selected via
the selector. We’d perhaps need to implement something like “weak
columns” - those could be removed, if more space is needed.

Second option is to give total flexibility to users so they can define
their own columns for each individual index table. This will be more
challenging task, but it’s up to users what to put on the pages. We’d
still need some logic to hide/show taxonomy based on the selector. This
should be perhaps configurable (some users might prefer to see them all
the time).

What are your opinions on that?

[1] https://github.com/theforeman/foreman/pull/3054


Later,
Lukas #lzap Zapletal


You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University