too much buttons (librarian interface) => how to solve.
Hello, In some screens, depending on the situation, we have MANY "action" buttons. for example, in a biblio detail, when there is a subscription & the librarian has all permissions, there are : Edit biblio // Duplicate // Edit items // Delete // Complete view // ISBD view // normal view // add to shelf // Subscriptions // Print // view logs[*] That is 11 buttons !!! Really too much for the user imo. We have various solutions : - let as is, as there are only 2-3 places where there is this problem (mainly : biblio & member) Pro : nothing to do, and 2-3 places, who cares. Cons : not nice to use. - Put those 11 buttons on 3 different lines. Cons : that's many place left, as, sometimes the user has not 11 possibilités (due to permission or biblio). Pro : users used to find actions on the top of the screen. - Put those 11 buttons in a block on the right. It's very easy to do with CSS, functionnal blocks (EDIT / VIEW / OTHER) can be separated by a space (<br/>). Cons : on large screen, the right part can be a little bit far from the mouse. Pro : uses some free place. with a fixed positionning, can be always on screen. Let me know your opinion, but mine is "block on the right". [*] this is a new feature to see who do what on the biblio, if the systempref is set -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Hi
In some screens, depending on the situation, we have MANY "action" buttons. for example, in a biblio detail, when there is a subscription & the librarian has all permissions, there are : Edit biblio // Duplicate // Edit items // Delete // Complete view // ISBD view // normal view // add to shelf // Subscriptions // Print // view logs[*]
That is 11 buttons !!!
Paul could they be grouped perhaps with different css "containers" into their different sorts of actions? Ie Changing the record actions >> Edit biblio, Duplicate, edit items, delete Looking at the record actions :: Complete View, ISBD View, Normal View, Print, Logs And then maybe add to shelf is a bit off by itself.... See my pic attached for what I mean would be good if they could be either accross the top or not I guess Cheers R
I'm wondering about the view buttons Complete view // ISBD view // normal view if you are in one of these views do you need a button for it too? eg if you are in ISBD view would you need a button for ISBD view? or only need the buttons for the other 2 views that could save a button right there Bob Rachel Hamilton-Williams wrote:
Hi
In some screens, depending on the situation, we have MANY "action" buttons. for example, in a biblio detail, when there is a subscription & the librarian has all permissions, there are : Edit biblio // Duplicate // Edit items // Delete // Complete view // ISBD view // normal view // add to shelf // Subscriptions // Print // view logs[*]
That is 11 buttons !!!
Paul could they be grouped perhaps with different css "containers" into their different sorts of actions?
Ie
Changing the record actions >> Edit biblio, Duplicate, edit items, delete
Looking at the record actions :: Complete View, ISBD View, Normal View, Print, Logs
And then maybe add to shelf is a bit off by itself....
See my pic attached for what I mean
would be good if they could be either accross the top or not I guess
Cheers R
------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
-- Robert Lyon Katipo Communications
Robert Lyon a écrit :
I'm wondering about the view buttons
Complete view // ISBD view // normal view
if you are in one of these views do you need a button for it too?
eg if you are in ISBD view would you need a button for ISBD view? or only need the buttons for the other 2 views
that could save a button right there
there are 2 cons with this idea : - the buttons where not always at the same place, which is a pain for the user - toins created a specific .inc for all places where those buttons have to be shown, your idea makes this impossible.
Paul could they be grouped perhaps with different css "containers" into their different sorts of actions?
Very good suggestion : thus, no need to decide wether we have horizontal or vertical button, the library & the css decide it. adopted, toins, will do it immediatly ! -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
eg if you are in ISBD view would you need a button for ISBD view? or only need the buttons for the other 2 views
there are 2 cons with this idea : - the buttons where not always at the same place, which is a pain for the user - toins created a specific .inc for all places where those buttons have to be shown, your idea makes this impossible.
Joshua and I discussed this issue at length for the redesign of the OPAC in dev_week. We came up with a scheme that differentiates between interactions. For example: http://search.athenscounty.lib.oh.us/cgi-bin/koha/opac-detail.pl?bib=179207 A change in 'view' is classified as one particular kind of interaction. For those interactions we used tabs (in this example you don't see ISBD because ISBD is disabled in our system). The buttons on the page are reserved for more "active" actions--things you can do with the item: reserve it, add it to your book bag, print it, etc. I don't see any reason why a similar system of organization couldn't be used for the intranet. I think Paul is right that it creates a problem when a button is present in one view and not another. A tab system helps solve that because the tab is always present but sometimes "active." I object, however, to the notion that we /can't/ make changes to interfaces based on the limitations we impose on ourselves through the use of .inc files or whatever quirk of the technology. Our focus should be on making an interface flexible enough to allow for the best usability possible. -- Owen
Hello, Le 12 janv. 07 à 03:23, Rachel Hamilton-Williams a écrit :
Hi
In some screens, depending on the situation, we have MANY "action" buttons. for example, in a biblio detail, when there is a subscription & the librarian has all permissions, there are : Edit biblio // Duplicate // Edit items // Delete // Complete view // ISBD view // normal view // add to shelf // Subscriptions // Print // view logs[*]
That is 11 buttons !!!
Paul could they be grouped perhaps with different css "containers" into their different sorts of actions?
Yes, good idea, I agree !
Ie
Changing the record actions >> Edit biblio, Duplicate, edit items, delete
Looking at the record actions :: Complete View, ISBD View, Normal View, Print, Logs
And then maybe add to shelf is a bit off by itself....
See my pic attached for what I mean
would be good if they could be either accross the top or not I guess
Cheers R
<MENU-IDEA.jpg> _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
participants (5)
-
Owen Leonard -
Pascale Nalon -
Paul POULAIN -
Rachel Hamilton-Williams -
Robert Lyon