Re: [Koha] Problem with migrating barcodes
Clint, Can you tell us more about how you migrating your data ? Are you able to confirm than the export from MS Access was in the right format ? Cheers, Eric BéginSolutions inLibro inc. -------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please. Thank you, Clint. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Dear Clint' physical barcode such as T20132X 2685'We had a same problem with Alice for windows few years back.Seems like the physical barcode number is padded (initialised) with client code, etc in the scanner itself; the actual barcode is as stored in the db.Kind regardsfauzi On Sunday, 6 March 2016, 10:31, Eric Bégin <eric.begin@inlibro.com> wrote: Clint, Can you tell us more about how you migrating your data ? Are you able to confirm than the export from MS Access was in the right format ? Cheers, Eric BéginSolutions inLibro inc. -------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please. Thank you, Clint. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Dear Clint ' physical barcode such as T20132X 2685' We had a same problem with Alice for windows few years back. Seems like the physical barcode number is padded (initialised) with client code, etc in the scanner itself; the actual barcode is as stored in the db. Kind regards fauzi sorry for the previous response -- View this message in context: http://koha.1045719.n5.nabble.com/Problem-with-migrating-barcodes-tp5877307p... Sent from the Koha-general mailing list archive at Nabble.com.
Thank you for the information. How did you solve the problem in the case of Alice? Clint. fauzi @ poizi Abu Bakar wrote:
Dear Clint' physical barcode such as T20132X 2685'We had a same problem with Alice for windows few years back.Seems like the physical barcode number is padded (initialised) with client code, etc in the scanner itself; the actual barcode is as stored in the db.Kind regardsfauzi
On Sunday, 6 March 2016, 10:31, Eric Bégin <eric.begin@inlibro.com> wrote:
Clint, Can you tell us more about how you migrating your data ? Are you able to confirm than the export from MS Access was in the right format ? Cheers, Eric BéginSolutions inLibro inc.
-------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes
I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please.
Thank you, Clint. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Clint, It may be that the Karant software performs a transformation on what is stored in the DB to arrive at the barcode number attached to the physical item. As Fauzi attests, Softlink's Alice has a particular nasty whereby the physical barcode contains a capitalized alpha character that is not stored in the db. The algorithm for discovering the character involves a mod 11 calculation and then the use of a look-up table. Why anyone would do that, you'd have to ask them. I am not familiar with Karant so have no idea whether or not this is what is going on for you. Hope it helps anyway, Bob Birchall Calyx On 06/03/16 17:46, clint.deckard wrote:
Thank you for the information. How did you solve the problem in the case of Alice?
Clint.
fauzi @ poizi Abu Bakar wrote:
Dear Clint' physical barcode such as T20132X 2685'We had a same problem with Alice for windows few years back.Seems like the physical barcode number is padded (initialised) with client code, etc in the scanner itself; the actual barcode is as stored in the db.Kind regardsfauzi On Sunday, 6 March 2016, 10:31, Eric Bégin <eric.begin@inlibro.com> wrote:
Clint, Can you tell us more about how you migrating your data ? Are you able to confirm than the export from MS Access was in the right format ? Cheers, Eric BéginSolutions inLibro inc.
-------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please.
Thank you, Clint.
Bob (and other respondents), I think you are right, I think Karant is transforming the barcode when scanned. T20132X 2685 is recorded as 120132 T22092N 2685 is recorded as 122092 When scanned to a text editor the correct, full barcode is read. 2685 is the school's ID number. The Access field is set as a number, double length. I suspect the next step is to examine the code to find details of the transformation. However, since the seventh character, the letter, is discarded it would seem impossible to build the complete barcode from the 6 numbers recorded. Thank you for your input. Clint. Bob Birchall wrote:
Hi Clint, It may be that the Karant software performs a transformation on what is stored in the DB to arrive at the barcode number attached to the physical item.
As Fauzi attests, Softlink's Alice has a particular nasty whereby the physical barcode contains a capitalized alpha character that is not stored in the db. The algorithm for discovering the character involves a mod 11 calculation and then the use of a look-up table.
Why anyone would do that, you'd have to ask them. I am not familiar with Karant so have no idea whether or not this is what is going on for you.
Hope it helps anyway, Bob Birchall Calyx
On 06/03/16 17:46, clint.deckard wrote:
Thank you for the information. How did you solve the problem in the case of Alice?
Clint.
fauzi @ poizi Abu Bakar wrote:
Dear Clint' physical barcode such as T20132X 2685'We had a same problem with Alice for windows few years back.Seems like the physical barcode number is padded (initialised) with client code, etc in the scanner itself; the actual barcode is as stored in the db.Kind regardsfauzi On Sunday, 6 March 2016, 10:31, Eric Bégin <eric.begin@inlibro.com> wrote:
Clint, Can you tell us more about how you migrating your data ? Are you able to confirm than the export from MS Access was in the right format ? Cheers, Eric BéginSolutions inLibro inc.
-------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please.
Thank you, Clint.
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Dear Clint 1. Barcode number in db is unique; so we have decided to ignore the physical barcode characters. 2. Reset barcode scanner; no issues with the new barcode scanner. Furthermore the existing barcode labels represent the actual barcode number in db. 3. Design new barcode numbers for the new books / resources. Kind regards fauzi izi.my -- View this message in context: http://koha.1045719.n5.nabble.com/Problem-with-migrating-barcodes-tp5877307p... Sent from the Koha-general mailing list archive at Nabble.com.
Eric, I have the database and confirm the the barcode is stored in a truncated manner. Clint. Eric Bégin wrote:
Clint,
Can you tell us more about how you migrating your data ?
Are you able to confirm than the export from MS Access was in the right format ?
Cheers,
Eric Bégin Solutions inLibro inc.
-------- Message d'origine -------- De : "clint.deckard" <clint.deckard@frontiers.co.nz> Date : 05/03/2016 20:53 (GMT-05:00) À : Koha-List <koha@lists.katipo.co.nz> Objet : [Koha] Problem with migrating barcodes
I have been asked to migrate an M$ Access based library system, Karant, which as developed locally by a gentleman that no longer supports the software. The problem is a physical barcode such as T20132X 2685 is recorded in the database as 120132. I wonder if anyone can point me towards what might be happening please.
Thank you, Clint. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
participants (5)
-
Bob Birchall -
clint.deckard -
Eric Bégin -
fauzi -
fauzi ＠ poizi Abu Bakar