I have worked around this issue by placing the borrowers cardnumber into a
borrowers_attribute. The attribute is set to unique and is searchable and
can be used to logon to Koha. We simply 'autogenerated' cardnumbers for
the library to use in the borrowers.cardnumber field. This way we left the
Hello Chris and Mark,
Thank you for replying. The information on the deleteditems table was
particularly valuable.
I changed the database and everything went okay smoothly. Our problem, for
now, is solved.
I also saw Mark's links and although the same cause, it's a different
problem.
I guess a
Greetings,
This question reminded of of a blog entry.
http://blog.l2c2.co.in/index.php/2016/09/12/down-the-rabbit-hole-making-cardnumber-field-in-koha-longer-than-16-characters-limit/
It also reminded me of a bugzilla entry.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15690
I
* Pedro Amorim (pjamori...@gmail.com) wrote:
Hello everyone,
I have a question regarding barcode length in Koha.
I'm importing a new biblio database and some barcodes have length of 26 or
28 and so on.
Koha's database schema limits the barcode field in the items table to
varchar(20).
My
Hello everyone,
I have a question regarding barcode length in Koha.
I'm importing a new biblio database and some barcodes have length of 26 or
28 and so on.
Koha's database schema limits the barcode field in the items table to
varchar(20).
My question is:
Is it okay to manually alter this field
5 matches
Mail list logo
