Why three levels in ACQ (Order, Basket. Basket group) ?
Hi to all, I'm trying to understand in deep the ACQ modules. For me now is not clear why there are three levels (Order, Basket. Basket group). I don't' understand well the use of Basket group. The manual is not very clear on this point. Cheers Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate
On Thu, Sep 5, 2013 at 5:23 AM, Zeno Tajoli <z.tajoli@cineca.it> wrote:
I don't' understand well the use of Basket group. The manual is not very clear on this point.
That would be because I too am not really clear on the purpose of basket groups :) So I didn't document it very throroughly. Great question!! Nicole
Hello, I have always thougt the UX of acq module is very poor, and this is one of the most annoying point : In our library, we need to print the order to send it to the vendor. The only way to do that is to create a "basketgroup" and print it in pdf. No way to do that for baskets... But in each basketgroup, we put only ONE basket. So we don't need the basket grouping feature, except for printing orders. The complete workflow in Koha is unnecessarily complex for us. M. Saby Le 05/09/2013 13:04, Nicole Engard a écrit :
On Thu, Sep 5, 2013 at 5:23 AM, Zeno Tajoli <z.tajoli@cineca.it> wrote:
I don't' understand well the use of Basket group. The manual is not very clear on this point. That would be because I too am not really clear on the purpose of basket groups :) So I didn't document it very throroughly.
Great question!!
Nicole _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
On Thu, Sep 05, 2013 at 01:47:28PM +0200, Mathieu Saby wrote:
But in each basketgroup, we put only ONE basket. So we don't need the basket grouping feature, except for printing orders. The complete workflow in Koha is unnecessarily complex for us.
I think that is a generally held view. I know a number of libraries who not only tend to use one basket per basket group but also one order per basket. When people move to electronic ordering that seems to be the norm. Certainly in the English speaking world librarians find the terminology a bit odd initially. I dont think many use the term basket until they encounter Koha. The koha basket corresponds to what they tend to think of as an order. and the koha order corrsponds to the orderline. Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com
Colin Campbell a écrit :
On Thu, Sep 05, 2013 at 01:47:28PM +0200, Mathieu Saby wrote:
But in each basketgroup, we put only ONE basket. So we don't need the basket grouping feature, except for printing orders. The complete workflow in Koha is unnecessarily complex for us.
I think that is a generally held view. I know a number of libraries who not only tend to use one basket per basket group but also one order per basket. When people move to electronic ordering that seems to be the norm. Certainly in the English speaking world librarians find the terminology a bit odd initially. It is odd in french too ;-) We did not translate "basket group" litteraly but as "bordereau", which can be translated as "purchase order".
M. Saby
I dont think many use the term basket until they encounter Koha. The koha basket corresponds to what they tend to think of as an order. and the koha order corrsponds to the orderline.
Colin
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
Le 05/09/2013 13:04, Nicole Engard a écrit :
On Thu, Sep 5, 2013 at 5:23 AM, Zeno Tajoli <z.tajoli@cineca.it> wrote:
I don't' understand well the use of Basket group. The manual is not very clear on this point.
That would be because I too am not really clear on the purpose of basket groups :) So I didn't document it very throroughly. This question is probably for me ;-)
The idea behind this is that some libraries have the following workflow: * a *librarian* prepares the basket during the week * on friday, a *administrative Assistant* put all baskets into a single order, that is sent to the vendor (and yes, the vendor want only one order, with 200+ lines, where there can be 20 librarians that made the basket, each being responsible of buying for a branch/topic/material/...) ATM, when you close a basket, you have an option to automatically create a basketgroup with the same name as the basket, and it is immediately closed for being printed. I think/suspect that it is Mathieu Saby library behaviour. A possible improvement could be to have a syspref to completely hide the basketgroup level: you close the basket, you get the PDF, and that's all. In this case, the basketgroup level would still be here, but unused & unnecessary. HTH -- Paul POULAIN - Associé-gérant Tel : (33) 4 91 81 35 08 http://www.biblibre.com Logiciels Libres pour les bibliothèques et les centres de documentation
Le 05/09/2013 14:21, Paul Poulain a écrit :
Le 05/09/2013 13:04, Nicole Engard a écrit :
On Thu, Sep 5, 2013 at 5:23 AM, Zeno Tajoli <z.tajoli@cineca.it> wrote:
I don't' understand well the use of Basket group. The manual is not very clear on this point. That would be because I too am not really clear on the purpose of basket groups :) So I didn't document it very throroughly. This question is probably for me ;-)
The idea behind this is that some libraries have the following workflow: * a *librarian* prepares the basket during the week * on friday, a *administrative Assistant* put all baskets into a single order, that is sent to the vendor (and yes, the vendor want only one order, with 200+ lines, where there can be 20 librarians that made the basket, each being responsible of buying for a branch/topic/material/...)
ATM, when you close a basket, you have an option to automatically create a basketgroup with the same name as the basket, and it is immediately closed for being printed. I think/suspect that it is Mathieu Saby library behaviour.
Yes, this is our behavior.
A possible improvement could be to have a syspref to completely hide the basketgroup level: you close the basket, you get the PDF, and that's all. In this case, the basketgroup level would still be here, but unused & unnecessary.
It could be a good idea, but we need to develop the ability to export the basket in pdf, like the basketgroup (by the way, the current way of creating pdf for basketgroups could be improved, by using perl > html> pdf instead of direct perl > pdf ). M. Saby
HTH
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
participants (5)
-
Colin Campbell -
Mathieu Saby -
Nicole Engard -
Paul Poulain -
Zeno Tajoli