Wishlist: Store web staff workstation settings on the server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
This idea has come up in various conversations (e.g. the hackaway). I was unable to find an LP bug or hackaway notes, though, so I'm staring over from scratch. If someone has notes, please add them to the bug.
The general idea is that values for staff workstation settings that must persist over time should be stored within the Evergreen server and not within the browser. These are things like column settings (see also bug #1702929), locally modified print templates, etc. Storing on the server lets us avoid the problem of settings getting wiped by clearing browser data.
Additionally, it should be possible for admins to provide default values for some settings and it should be possible for admins to prevent staff from applying values to certain settings.
It should be possible to store settings at the user level, the workstation level, and at the org unit level.
The settings in question are currently stored in localStorage or Hatch. Any values stored just for caching purposes or in cookies or sessionStorage will not be stored on the server, since they are intentionally ephemeral.
What we need:
* A way to link settings to users, workstations, and org units.
* A way to define precedence between them.
* A way to control who can apply values on a per-setting level.
* A way to apply values from the client.
* A migration path for current settings
* Removal of data storage options in Hatch. IOW, make Hatch printing only.
I suspect I've missed a few things. Input appreciated.
Changed in evergreen: | |
assignee: | nobody → Kathy Lussier (klussier) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
One thing to keep in mind is that we'll still want to keep a local copy (in localStorage or lovefield) of some settings, as they may be used in the offline UI. In particular, I suspect the user registration page may need some workstation settings. I believe we are caching YAOUSen in lovefield already, though.