Problems with suggestions
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.) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
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.boisson@biblibre.com
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-bounces@lists.koha-community.org [mailto:koha-devel- bounces@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.boisson@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/
On Mon, Sep 24, 2012 at 3:45 AM, Fischer, Katrin <Katrin.Fischer@bsz-bw.de> wrote:
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?
+1 ... too many of our libraries are consortia with one central ordering location and they don't want to limit on branch. This is a regression and I think we need a preference, but if we can't have that easily then it must remember the last state and have a message explaining how to remove the filter. Nicole
Op 25-09-12 00:18, Nicole Engard schreef:
+1 ... too many of our libraries are consortia with one central ordering location and they don't want to limit on branch. This is a regression and I think we need a preference, but if we can't have that easily then it must remember the last state and have a message explaining how to remove the filter.
A syspref is in fact easier than what I suggested, I just thought my idea might be more useful. Really, it's up to what people using it would think best, but as it is it's problematic. Robin.
In my opinion, the current branch filtering can be a behavior common to all intranet pages. Maybe a combo-box next to login. In this case, it would be easy to know what is the current filtering. It would be initialized with user's branch and its current value could be saved in cookie to remain after a deconnexion. It would also manage the "IndependantBranch" syspref. My 2c. Le 24/09/2012 09:45, Fischer, Katrin a écrit :
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-bounces@lists.koha-community.org [mailto:koha-devel- bounces@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.boisson@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/
-- Fridolyn SOMERS Biblibre - Pôle Support 09 74 77 07 15 fridolyn.somers@biblibre.com <mailto:fridolyn.somers@biblibre.com>
At 05:07 PM 9/24/2012 +0200, Fridolyn SOMERS wrote:
In my opinion, the current branch filtering can be a behavior common to all intranet pages. Maybe a combo-box next to login. In this case, it would be easy to know what is the current filtering. It would be initialized with user's branch and its current value could be saved in cookie to remain after a deconnexion. It would also manage the "IndependantBranch" syspref.
My 2c.
+1 this would be a very logical step forward, unifying several loose ends. a+ -- paul
Le 24/09/2012 09:45, Fischer, Katrin a écrit :
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: <mailto:koha-devel-bounces@lists.koha-community.org>koha-devel-bounces@lists.koha-community.org [<mailto:koha-devel>mailto:koha-devel- <mailto:bounces@lists.koha-community.org>bounces@lists.koha-community.org] On Behalf Of Gaetan Boisson Sent: Monday, September 24, 2012 9:29 AM To: <mailto:koha-devel@lists.koha-community.org>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:
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 <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha-community.org/>http://git.koha-community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/
-- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille <mailto:gaetan.boisson@biblibre.com>gaetan.boisson@biblibre.com
_______________________________________________ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha>http://git.koha- community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list <mailto:Koha-devel@lists.koha-community.org>Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : <http://www.koha-community.org/>http://www.koha-community.org/ git : <http://git.koha-community.org/>http://git.koha-community.org/ bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/
-- Fridolyn SOMERS Biblibre - Pôle Support 09 74 77 07 15 <mailto:fridolyn.somers@biblibre.com>fridolyn.somers@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/
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
participants (7)
-
Fischer, Katrin -
Fridolyn SOMERS -
Gaetan Boisson -
Marc Véron -
Nicole Engard -
Paul -
Robin Sheat