Hi Pawel,
have you been able to solve the problem yet?
I am not sure what happened there, but maybe some more information could
give us an idea:
- Did you update an existing or a fresh installation?
- Which version(s) exactly?
- Where there any error messages during the upgrade process?
- Did
Hi Charles,
in German libraries an acquisition number like this is very common.
There is a specific Koha item subfield for it already: 952$i =
stocknumber or inventory number. It is indexed in Zebra and there are
some value builders (like stocknumberAV.pl) to generate different
sequential number
We have just addressed the exact same problem, and a lot more. We are in the
process of opening up the purchase suggestions functionality and rolling it out
to college library staff in our multi-site setup with some significant
challenges. (Until now we have managed it a headquarters, and are
Great job, Martin!
El lun., 2 dic. 2019 a las 11:40, Renvoize, Martin (<
martin.renvo...@ptfs-europe.com>) escribió:
> Hello everyone,
>
> It is my great pleasure to be able to announce the release and
> immediate availability of Koha 19.11, a major release of the Koha open
> source integrated
Hello,
A bit of fresh news, I have submitted a bunch of patches that is ready
to be tested.
The main bug report is bug 24151 (Add a pseudonymization process for
patrons and transactions)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151
I pushed a remote branch with everything
Hello, all!
I have been asked to add a new indexed item field (subfield, that is).
Here's the story.
My library keeps track of its acquisitions in an old Access database.
Each acquisition is given a unique ID number consisting of two parts: the
year of acquisition and its sequence in the
6 matches
Mail list logo
