[Koha-bugs] [Bug 10858] Browse selected biblios

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10858

M. de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |m.de.rooy at rijksmuseum.nl
         QA Contact|testopia at bugs.koha-communit |m.de.rooy at rijksmuseum.nl
                   |y.org                       |

--- Comment #26 from M. de Rooy <m.de.rooy at rijksmuseum.nl> ---
Some prelimary QA comments/questions:

>From a functional perspective: I would like to see this feature in Koha. In
earlier comments some mentioned the cart. But this is an interesting addition!
Note also that I more than once heard the question: Why does Koha not remember
the items I selected on another search result page? So even without browsing,
you make some people happy.
If you browse the selection, it would imo be good to show that you are doing so
(Browse selected results vs. Browse results).
If we use the js plugin, it would be good to acknowledge that on About,
separate from the question if this specific MIT license needs that by law or
so.
Also I do not think that remembering a few biblios in a cookie, would be a big
legal problem. We c/should clear the contents every time we start a new search.
And if we are not allowed to create it, well we do not.. (We have some laws in
the Netherlands too about confirming the use of cookies, but in the meantime
things seem to go already in a less 

More technically:
There is a small merge conflict in koha-tmpl/opac-tmpl/prog/en/css/opac.css.
Note that I would like to see the bootstrap patch here also instead of on
another report. Bootstrap is now leading and should be pushed first. (Is there
any trouble there with less files?) 
>From a "minimalistic approach" I do wonder if we really need a new plugin (156
lines) for storing just a few checkboxes (no offense). This is more a personal
opinion too and would not be blocking. But could you on the other hand make
more clear why we definitely need this plugin and cannot do it with what we
have now [ within say 156 lines of code :) ] ?

Waiting for some feedback. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.