Hello,
I am working on converting the current System Group page within Katello
to the new UI framework (nutupane). This recently sparked a discussion
as within a system group you can install/update/remove packages and
apply errata. You can also mass change the associated environment and
content view. This means there are 3 places where you can perform these
types of actions actions:
- On an individual system
- On multiple systems within the 'bulk actions' on the system lists
- On the system group page
Since 2 & 3 are basically performing the same operation (doing ______ on
a set of systems), it makes sense to combine these somehow. The easiest
way in my mind is:
- Get rid of system group actions
- Direct users via a link to the systems page with a predefined search
(for systems in the group), all systems selected, and the bulk action
pane opened. (Potentially even enhance the systems page to provide an
easier way to search for a system group)
Thoughts on this approach?
One requirement of this is the ability to select all across all results
of a search query. After some discussions there are lots of ways of
implementing this, a few that stand out:
a) Gmail style (Easier)
Clicking select all takes the user into 'all' mode, un-selecting a
single system un-selects all but that page of items. Performing a new
search unselects all.
b) Gmail style with negative selections (Medium)
Similar to gmail style, but allows the user to unselect items from
their current search. Negative selections are recorded and sent up to
the server with the action to be performed (along with the current
query). Performing a new search clears all selections.
c) Spacewalk style (Harder)
Clicking select all actually selects all individual items. (i.e. if
100 items currently match the current query, all 100 items are selected
and their IDs are kept track of). In addition to the advantages of b),
this allows the user to perform multiple searches, selecting different
items as they search. This is somewhat approaching a shopping cart that
may better suite this type of interaction.
d) Some other option…
Thoughts on these (or new options)? I'm currently leaning towards b),
as it is does not seem much more difficult to implement than a) and
provides a bit more flexibility.
Since neither katello nor foreman have really tackled the issue (to my
knowledge), it would be good to try to agree on a general approach
moving forward.
-Justin
> Hello,
>
> I am working on converting the current System Group page within
> Katello to the new UI framework (nutupane). This recently sparked a
> discussion as within a system group you can install/update/remove
> packages and apply errata. You can also mass change the associated
> environment and content view. This means there are 3 places where you
> can perform these types of actions actions:
>
> 1) On an individual system
> 2) On multiple systems within the 'bulk actions' on the system lists
> 3) On the system group page
>
> Since 2 & 3 are basically performing the same operation (doing ______
> on a set of systems), it makes sense to combine these somehow. The
> easiest way in my mind is:
>
> * Get rid of system group actions
> * Direct users via a link to the systems page with a predefined search
> (for systems in the group), all systems selected, and the bulk action
> pane opened. (Potentially even enhance the systems page to provide an
> easier way to search for a system group)
>
> Thoughts on this approach?
[brad] +1 to having a single location to perform bulk actions. This
will minimize duplication (from development point of view) as well as
give the user a consistent location for performing such actions.
>
> One requirement of this is the ability to select all across all
> results of a search query. After some discussions there are lots of
> ways of implementing this, a few that stand out:
>
> a) Gmail style (Easier)
> Clicking select all takes the user into 'all' mode, un-selecting a
> single system un-selects all but that page of items. Performing a new
> search unselects all.
> b) Gmail style with negative selections (Medium)
> Similar to gmail style, but allows the user to unselect items from
> their current search. Negative selections are recorded and sent up to
> the server with the action to be performed (along with the current
> query). Performing a new search clears all selections.
> c) Spacewalk style (Harder)
> Clicking select all actually selects all individual items. (i.e. if
> 100 items currently match the current query, all 100 items are
> selected and their IDs are kept track of). In addition to the
> advantages of b), this allows the user to perform multiple searches,
> selecting different items as they search. This is somewhat
> approaching a shopping cart that may better suite this type of
> interaction.
> d) Some other option…
>
> Thoughts on these (or new options)? I'm currently leaning towards
> b), as it is does not seem much more difficult to implement than a)
> and provides a bit more flexibility.
>
[brad] +1 on option b). I'd expect it to be a common use case that
users will want to perform an action on only a subset of the systems in
a system group or a subset of systems of a search result. Option b)
seems like it would easily support that.
···
On 11/03/2013 09:06 PM, Justin Sherrill wrote:
> Since neither katello nor foreman have really tackled the issue (to my
> knowledge), it would be good to try to agree on a general approach
> moving forward.
>
> -Justin
>
>
I like the shopping cart style as being high value usefulness. Option C is
my vote
···
On Sunday, November 3, 2013 9:06:50 PM UTC-5, jlsherrill wrote:
>
> Hello,
>
> I am working on converting the current System Group page within Katello
> to the new UI framework (nutupane). This recently sparked a discussion
> as within a system group you can install/update/remove packages and
> apply errata. You can also mass change the associated environment and
> content view. This means there are 3 places where you can perform these
> types of actions actions:
>
> 1) On an individual system
> 2) On multiple systems within the 'bulk actions' on the system lists
> 3) On the system group page
>
> Since 2 & 3 are basically performing the same operation (doing ______ on
> a set of systems), it makes sense to combine these somehow. The easiest
> way in my mind is:
>
> * Get rid of system group actions
> * Direct users via a link to the systems page with a predefined search
> (for systems in the group), all systems selected, and the bulk action
> pane opened. (Potentially even enhance the systems page to provide an
> easier way to search for a system group)
>
> Thoughts on this approach?
>
> One requirement of this is the ability to select all across all results
> of a search query. After some discussions there are lots of ways of
> implementing this, a few that stand out:
>
> a) Gmail style (Easier)
> Clicking select all takes the user into 'all' mode, un-selecting a
> single system un-selects all but that page of items. Performing a new
> search unselects all.
> b) Gmail style with negative selections (Medium)
> Similar to gmail style, but allows the user to unselect items from
> their current search. Negative selections are recorded and sent up to
> the server with the action to be performed (along with the current
> query). Performing a new search clears all selections.
> c) Spacewalk style (Harder)
> Clicking select all actually selects all individual items. (i.e. if
> 100 items currently match the current query, all 100 items are selected
> and their IDs are kept track of). In addition to the advantages of b),
> this allows the user to perform multiple searches, selecting different
> items as they search. This is somewhat approaching a shopping cart that
> may better suite this type of interaction.
> d) Some other option...
>
> Thoughts on these (or new options)? I'm currently leaning towards b),
> as it is does not seem much more difficult to implement than a) and
> provides a bit more flexibility.
>
> Since neither katello nor foreman have really tackled the issue (to my
> knowledge), it would be good to try to agree on a general approach
> moving forward.
>
> -Justin
>
>
>
