Thoughts on grouping of presets

[Dan Morphis]

Currently, we have 1,511 presets :) With about 1,500 of them being device
specific presets.

The original intention had been to filter based on preset name prefix
(Routed_), however somewhere along the way ISP specific presets ended up
with Routed_ as a prefix in some instances (Routed_WanPort,
Routed_No_WanPort, etc).

I understand and appreciate your hesitancy to add new features, features
bring complexity.

-dan

On Mon, Mar 27, 2017 at 3:40 PM, Zaid Abdulla <zaid at genieacs.com> wrote:

> On Fri, 2017-03-24 at 09:13 -0800, Dan Morphis wrote:
> > Before I go to far down the route of implementing this, I thought I
> > would put this out there to see if it would be accepted.
> >
> > We have a lot of presets in our environment. Most of them exist for
> > customer specific settings (Wi-Fi), but a good bit also exist for
> > kicking off provisioning scripts, etc.
> >
> > My thought was to be able to add tags to presets, and query presets
> > based on tags much like devices. This would give you the ability to
> > quickly filter presets to the specific set you want to view/modify.
>
> I'm curious how many presets you have? I can't imagine why you'd need
> more than a few presets unless you have one preset for each device that
> has a customer specific settings?
>
> I like your suggestion but I'm generally hesitant when it comes to
> adding new features. Can you filter based on preset name prefixes
> instead?
>
> --
> Zaid Abdulla <zaid at genieacs.com>
> _______________________________________________
> Users mailing list
> Users at lists.genieacs.com
> http://lists.genieacs.com/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20170327/12bb1b09/attachment.html>