I have a page in a web app that displays a large amount of tabular data regarding certain resources. With this release, in addition to standard columns, there can be an arbitrary number of user-defined fields that are set and show up as columns in the same table.
You can hide or show individual columns, but this isn't persisted across logins. Since the addition of user-defined fields, I'm adding the ability to save 'views', which is basically just a list of displayed columns and the sort order.
At first I was thinking of having three actions for saving/loading.
- Load saved view (select list of options)
- Save current view (+ textbox to enter name for new view)
- Update current saved view (if the current view was loaded from a saved view)
but now I'm not sure if that's intuitive, or when if once view is 'loaded', changes to the currently displayed columns should just be updated back to the saved view automatically.
Any opinions about which is better?
I've rambled a bit, but hopefully that's fairly clear.