Hello,
I wonder if you can point use in the right direction to modify the Koha
system we’ve just installed?
We’ve set up a basic system to use with barcodes and barcode readers for
both items and patrons.
The problem is that our ID card barcodes add two leading 0s to staff IDs (7
digits vs 9
Hello Jeremy,
I'd say the easiest solution for you would be to have some Javascript or
JQuery function to do this processing.
Then you can associate the execution of this function to the "onsubmit"
event of the desired form with JQuery.
To add some Javascript code easily to your Koha installatio
Hello,
But itype must not be null if syspref item-level_itype is on, isn't it ?
S. Meynieux
--
Responsable support
BibLibre
+ 33 (0)4 91 81 35 08
http://www.biblibre.com
Le 29/07/2019 à 20:17, Katrin Fischer a écrit :
+1
With a on delete set null?
On 29.07.19 19:39, Tomas Cohen Arazi wrote
Hi Sophie,
I think on database level we need to allow NULL, because of the
item-level_itype 'record level' setting. I understand that itemtypes are
not set on item level at all in that case?
Katrin
On 30.07.19 16:32, Sophie Meynieux wrote:
Hello,
But itype must not be null if syspref item-le
We can set a FK constraint while allowing NULL too. The reason for me to
post this on the list is to hear (probably) historical reasons for this
constraint not to be set already at DB level.
Thanks for your replies!
El mar., 30 jul. 2019 a las 16:05, Katrin Fischer ()
escribió:
> Hi Sophie,
>
>
If we set items.itype to NULL, aren’t we potentially causing problems for
people who want to JOIN “statistics” and “items” tables?
Do we already have software logic to prevent Item Types from being deleted if
they’re used in items or biblioitems?
David Cook
Systems Librarian
Prosentien
