I think I would still prefer a system preference here. But I also like the idea to remember the last state for each user.
But I think this would be harder to do - while a system preference might be the easier way to go back to former behaviour? Katrin > -----Original Message----- > From: koha-devel-boun...@lists.koha-community.org [mailto:koha-devel- > boun...@lists.koha-community.org] On Behalf Of Gaetan Boisson > Sent: Monday, September 24, 2012 9:29 AM > To: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] Problems with suggestions > > I completely agree that this is confusing, and it took my a while to > figure out that when you reach this screen the filter is not empty. (The > site is picked in "acquisition information"), actually if you play a > little with the filter, then click "clear", you go back to a setting > where you only see suggestions made for the site you are connected to. > > Like Robin suggested, i think adding a sentence like "By default you > will only see suggestions made at the site you are connected to. Use the > filter to change this behaviour." would solve the problem without > resorting to fancy developments, unicorns and poneys. > > Just my 2 cents ;) > > Le lundi 24 septembre 2012 à 18:24 +1200, Robin Sheat a écrit : > > We have had a few queries about suggestions not working correctly in > > 3.8, that seem to be the result of this: > > > > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7300#c6 > > > > can we decide the path to solving this? Making suggestions hidden by > > default is distinctly a regression for many libraries. On the other > > hand, filtering by branch is a genuinely useful thing, as is the > > ability to filter by default. > > > > My suggestion (to avoid a syspref) is that it has big, obvious words > > saying it's filtered and a button to show all, and it remembers the > > last state that user had (filtered or not) to show them next time. But > > I don't have any funding in line for this, so it'd really be up to > > whoever had the time to implement it. > > > > (It also maybe exposed a weakness in the patch signoff workflow, as it > > didn't really get any external review before going in, but that's > > another conversation perhaps.) > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel@lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ git : > > http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ > > -- > Gaetan Boisson > Chef de projet bibliothécaire > BibLibre > 06 52 42 51 29 > 108 avenue Breteuil 13006 Marseille > gaetan.bois...@biblibre.com > > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha- > community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
