| Summary: | The 'set library' functionality should be changed to 'session settings' or similar | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
| Component: | Architecture, internals, and plumbing | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | dcook, lucas, tomascohen |
| 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: | |||
| Bug Depends on: | 24786 | ||
| Bug Blocks: | |||
|
Description
Martin Renvoize (ashimema)
2020-08-07 11:45:46 UTC
The 'catalogue' permission is a strange one to require as the sole permission to use this functionality I believe we should mimick what happens on the log in screen and not allow to change the library. I think the whole point of indybranches is to keep things separate. If you have central cataloguing, we maybe need a 'super' permission for edit_catalogue like we have in other cases. (In reply to Martin Renvoize from comment #0) > The set library controller and template will soon allow the setting of other > session level information like 'desk' and 'cash register'.. as such we > should rename and clean up the controller and template to reflect their new > functionality. Sounds good to me. Wow I do not recall commenting on this previously but still +1 'Session' might be enough? (In reply to Tomás Cohen Arazi from comment #6) > 'Session' might be enough? Thinking about this again... I think that "session" is a developer concept that most staff users wouldn't understand. I think they're all circulation related so maybe "My circulation settings", although that's a lot of text. Maybe "My location"? Since it would be dealing with their branch, desk, cash register... (In reply to David Cook from comment #7) > (In reply to Tomás Cohen Arazi from comment #6) > > 'Session' might be enough? > > Thinking about this again... I think that "session" is a developer concept > that most staff users wouldn't understand. > > I think they're all circulation related so maybe "My circulation settings", > although that's a lot of text. Maybe "My location"? Since it would be > dealing with their branch, desk, cash register... I like 'Location'. The 'My' part of implicit it could be clarified on a drop-down title/header. To understand my opinion, lol at the account info in OPAC and see how redundant it can get! (In reply to Tomás Cohen Arazi from comment #8) > I like 'Location'. The 'My' part of implicit it could be clarified on a > drop-down title/header. To understand my opinion, lol at the account info in > OPAC and see how redundant it can get! Haha. True! I was thinking of keeping it consistent with other items in the dropdown menu but I'm not opposed to dropping the "My". (Also, lovely to hear from you, but you should go to sleep!) I am not sure if session would not be understood, location might get confused with locations in items again. What about something generic like "my settings"? We could imagine using this later for other things like some GUI preferences. What about "User settings"? Hmm, this is not really about the user so much as it's about the current login.. 'Login settings' maybe. Personally, I still think session is pretty clear... A session is a period of time doing something, certainly in British English it would make sense to most I think. Since it's in the staff interface, users can always be trained anyways. So maybe we should just go with "Session settings" after all. |