Another acquisition module ?
Hello I'm working with another student at ESIEE (Michel Lerenard) on an implementation of the Koha 1.9.x system for our school library. Serge Renaux is leading us in this task. It will lead to an install of the Koha 2 system when ready. As our library uses a slightly different way to acquire documents, we have to rearrange the way information are entered by the user. We figured out that one way to do it is to create another template directory and to configure Koha to use this directory. It seems that in our case, template modification is not sufficient so we were thinking of a solution based on another acquisition module. There is already an option in Koha that sets the type of acquisition (normal or simple) but this option doesn't seem to work (we are using Koha 1.9.2). Therefore, our first question is "Is this option not working due to a bug or because of a "non implemented yet" function ?" Our second question is : "Will it be possible to set the option to "esiee" for example so that Koha will use the Perl scripts localised in a "acqui.esiee" directory ?" Thank you in advance. Sincerely Jerome Vizcaino
Hello Jerome, Regarding the state of Acquisitions in 1.9.2, they are a work in progress ;-]. There were a number of bugs filed (and fixed) regarding these problems. In addition, Chris is working on "forward-porting" the simple acqusitions module from 1.2.3 into the pre-2.0 series. As to adding your own acqusitions module, yes, it would be fairly trivial to integrate another Acquisitions module into Koha. Right now, Koha uses the loadmodules.pl script to look up what module to use for acquisitions. All that would be really need to be done is to create the module, and add a line or two to loadmodules.pl. On a related note to developers, how should we go about making it so that the work other libraries do available to everyone? Do we want to include everything in the main releases or should we have a seperate section of a website where these modifications (and how to use them) would be made available? Mike -- Mike Hansen <mwhansen@hmc.edu>
Hello Mike We already made changes to the loadmodule.pl in order to call our own acquisition module. It worked mainly but we wanted to know if there was a proper way (i.e. adding another module without modifying any existing Koha files) to do it. Will further development allow users to select their own acquisition modules name (not only acqui or acqui.simple) from the graphical interface ? Thanks Jerome Mike Hansen wrote:
Hello Jerome,
Regarding the state of Acquisitions in 1.9.2, they are a work in progress ;-]. There were a number of bugs filed (and fixed) regarding these problems. In addition, Chris is working on "forward-porting" the simple acqusitions module from 1.2.3 into the pre-2.0 series.
As to adding your own acqusitions module, yes, it would be fairly trivial to integrate another Acquisitions module into Koha. Right now, Koha uses the loadmodules.pl script to look up what module to use for acquisitions. All that would be really need to be done is to create the module, and add a line or two to loadmodules.pl.
On a related note to developers, how should we go about making it so that the work other libraries do available to everyone? Do we want to include everything in the main releases or should we have a seperate section of a website where these modifications (and how to use them) would be made available?
Mike
I thought I would respond to this one first ( I am in the process of working on your other template question). At the moment, there is no "proper" way to add modules other than the way you did. It would be possible (and not too difficult) in the future to have a more robust modules system using the system preferences table, but we would need to decide on some conventions as to where modules would go. If decide on some "rules", it would be tivial to do. Mike On Mon, 2003-05-12 at 02:13, Jerome Vizcaino wrote:
Hello Mike
We already made changes to the loadmodule.pl in order to call our own acquisition module. It worked mainly but we wanted to know if there was a proper way (i.e. adding another module without modifying any existing Koha files) to do it. Will further development allow users to select their own acquisition modules name (not only acqui or acqui.simple) from the graphical interface ?
Thanks
Jerome
-- Mike Hansen <mwhansen@hmc.edu>
Jerome Vizcaino wrote:
Hello
I'm working with another student at ESIEE (Michel Lerenard) on an implementation of the Koha 1.9.x system for our school library. Serge Renaux is leading us in this task. It will lead to an install of the Koha 2 system when ready.
As our library uses a slightly different way to acquire documents, we have to rearrange the way information are entered by the user. We figured out that one way to do it is to create another template directory and to configure Koha to use this directory. It seems that in our case, template modification is not sufficient so we were thinking of a solution based on another acquisition module. There is already an option in Koha that sets the type of acquisition (normal or simple) but this option doesn't seem to work (we are using Koha 1.9.2). Therefore, our first question is "Is this option not working due to a bug or because of a "non implemented yet" function ?" Our second question is : "Will it be possible to set the option to "esiee" for example so that Koha will use the Perl scripts localised in a "acqui.esiee" directory ?"
Nothing to add to Mike answers. He's 100% right. Rien à ajouter à ce qu'à écrit Mike, c'est 100% exact. PS : content de vous voir à bord. Et bienvenue. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (3)
-
Jerome Vizcaino -
Mike Hansen -
paul POULAIN