| Summary: | Allow customization of staff interface based on login location | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Donna <bwsdonna> |
| Component: | Staff interface | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew, aspencatteam, gmcharlt, kebliss, lisettepalouse+koha, lucas, rcoert, sally.healey |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Donna
2020-04-27 18:28:35 UTC
Would the colors be defined in the branch admin section? ( branches.tt )? (In reply to Lucas Gass from comment #1) > Would the colors be defined in the branch admin section? ( branches.tt )? That seems like a good place for it, yes! Giving this another bump after the staff interface design overhaul. This is still something we're accomplishing with jquery and css; it'd be great to have something more stable. We customize our discovery layer already, it would be great to make it easier to put visual branding in for staff, that avoids a lot of jquery and css. We just have too many branches to take that approach. - Bob Bennhoff I agree with Andrew - having a more stable option for this would be ideal. We use our branch "color coding" (different menu bar colors @ each location) as a visual reminder for staff who move between locations. It's a simple yet effective way to cut down on errors. Now that we have OpacUser* options on library level, we could probably do the same for the staff interface? |