Koha's call number vs. our library's call number
As I mentioned in my "hierarchical question" posting, the shelf ordering system for one of our book item types (graded readers) is by reading difficulty level. To accommodate this, I've created an alphanumeric local call number unique to each item (copy of a title) I'm also using this as a barcode number. the first part of the number shows the level, then the set, then the titles, and then the individual copies. So Q010A04 means "the fourth copy of title A in set 010 at reading difficulty level Q". I plan to put this local call number into Koha's barcode field in the items table, and link that field to MARC 852c - please confirm I got at least that right, or should I use a 9xx? But I see that the *Koha* call number field is numeric. Can we just leave the Koha call number field empty? I saw Chris Cormack's tip on changing the dewey column's data type to varchar within SQL, but messing with the internals at my current newbie level makes me a bit nervous. Plus, I will be pulling in deweys from many of my MARC records, so where this is so, I'd rather store them where they're supposed to go in Koha in case we need that data later. So more to the point, how do we ignore this data in the meantime, and use the barcode field everywhere in Koha as a local call number field? I'd really appreciate some details as to how to do this, as pertains to both the opac and the intranet. Or alternatively, I'd also appreciate feedback on how I'm totally off-base regarding normal library practices <g>, along with suggestions on how to accomplish what I'm trying to do. Thanks, Hans
I'd recommend you put your call number in biblioitems.classification and not mess with dewey (everything should still work OK). Use some sort of unique numbering system for barcode. -- SH Hans Henderson said:
As I mentioned in my "hierarchical question" posting, the shelf ordering system for one of our book item types (graded readers) is by reading difficulty level.
To accommodate this, I've created an alphanumeric local call number unique to each item (copy of a title) I'm also using this as a barcode number. the first part of the number shows the level, then the set, then the titles, and then the individual copies. So Q010A04 means "the fourth copy of title A in set 010 at reading difficulty level Q".
I plan to put this local call number into Koha's barcode field in the items table, and link that field to MARC 852c - please confirm I got at least that right, or should I use a 9xx?
But I see that the *Koha* call number field is numeric. Can we just leave the Koha call number field empty?
I saw Chris Cormack's tip on changing the dewey column's data type to varchar within SQL, but messing with the internals at my current newbie level makes me a bit nervous. Plus, I will be pulling in deweys from many of my MARC records, so where this is so, I'd rather store them where they're supposed to go in Koha in case we need that data later.
So more to the point, how do we ignore this data in the meantime, and use the barcode field everywhere in Koha as a local call number field?
I'd really appreciate some details as to how to do this, as pertains to both the opac and the intranet. Or alternatively, I'd also appreciate feedback on how I'm totally off-base regarding normal library practices <g>, along with suggestions on how to accomplish what I'm trying to do.
Thanks,
Hans _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
Stephen Hedges a écrit :
I'd recommend you put your call number in biblioitems.classification and not mess with dewey (everything should still work OK). Use some sort of unique numbering system for barcode. -- SH
Note also that in 2.2 you will have a new field "itemcallnumber" that you will be able to pre-fill with dewey / loc / nothing. It's already in CVS & seems to work like a charm -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Thursday, July 8, 2004 18:08 CDT Salut Paul, Quick question re: your note on Stephen Hedge's answer to Hans Henderson:
Stephen Hedges a écrit :
I'd recommend you put your call number in biblioitems.classification and not mess with dewey (everything should still work OK). Use some sort of unique numbering system for barcode. -- SH
Note also that in 2.2 you will have a new field "itemcallnumber" that you will be able to pre-fill with dewey / loc / nothing.
It's already in CVS & seems to work like a charm
does the new field "itemcallnumber"in 2.2 map to a MARC tag and if so, which one? This will be important for exporting (sharing) MARC record information (or, God forbid, migration). Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.707 / Virus Database: 463 - Release Date: 15/06/2004
Steven F. Baljkas a écrit :
Note also that in 2.2 you will have a new field "itemcallnumber" that you will be able to pre-fill with dewey / loc / nothing.
It's already in CVS & seems to work like a charm
does the new field "itemcallnumber"in 2.2 map to a MARC tag and if so, which one? This will be important for exporting (sharing) MARC record information (or, God forbid, migration).
In MARC21, I don't know. In UNIMARC, it's 995$k 995 being for item information in "recommandation 995", used by 95% of french libraries See http://www.adbdp.asso.fr/outils/infogestion/r995.htm (in french) for more informations -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
Friday, July 9, 2004 17:39 CDT Salut Paul, Thanks very much for the quick response. Grand merci pour ta réponse # From what I read in IFLA's standards for UNIMARC, the 995 tag would be comparable to any of the 9xx tags in MARC21. That is, it's free (like beer or speech ;-) ) to use as system developpers/local librarians decide. J'ai feuilleté la page à http://www.adbdp.asso.fr/outils/infogestion/r995.htm et si j'ai bien compris, le 995 dont les bibliothèques française se servent est comme le 852 de MARC21 (et dans la structure et dans les données y attachées). I skimmed the page you sent the link for and if I understood correctly, the 995 used by French libraries is like the MARC21 852 tag both in structure and data coded there. The question remains though -- I think this was posed months ago now, but I don't remember seeing a response anywhere -- will there be/is there a *Koha MARC field* for the *call number used* ("itemcallnumber")? Donc cette question posée il y a quelques mois sans réponse évidente se présente encore : est-ce qu'il y a ou bien est-ce qu'il y aura *un seul champ de donnés MARC en Koha qui correspond au numéro de classification* (« itemcallnumber »)? This could be a simple question of adopting a default standard which users could change if they desired. But it would be useful to have *one* MARC field that has the function of *call number used*. Many systems use/d tag 090 (as this was LC's itemcallnumber used for years) and many others make use of 852 or a 9xx tag. For simplicity sake, one could certainly use the French standard of 995 since that tag is not prescribed in MARC21. A défaut de tous les choix possibles -- dont les bibliothèques individuelles pourraient changer selon leurs goûts -- ce serait très utile pour les bibliothécaires et les bibliotechniciens d'avoir *un* champ MARC qui a d'abord la fonction du *numéro de classification utilisé*. Il y a plusieurs systèmes intégrés pour les bibliothèques qui utilisent/utilisaient le 090 -- car ceci était pour plusieurs années la norme LC utilisée pour « itemcallnumber » -- et d'autres qui utilisent le 852 ou bien un des 9xx. Pour la simplicité et l'unité de communauté Koha on peut très bien adopter le 995 utilisé en France car ce champ n'est pas prescrit en MARC21. Will there be a decision on this by 2.2 or is this going to be left open? Est-ce qu'il y aura une décision par/avant l'apparence de 2.2 ou est-ce que l'on laisserait ainsi? Merci en avance. TIA Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada From: "Paul POULAIN" <paul.poulain@free.fr> To: "Steven F. Baljkas" <baljkas@mb.sympatico.ca> Cc: "Koha mailing list" <koha@lists.katipo.co.nz> Sent: Friday, July 09, 2004 2:12 AM Subject: Re: [Koha] Koha's call number vs. our library's call number
Steven F. Baljkas a écrit :
Note also that in 2.2 you will have a new field "itemcallnumber" that you will be able to pre-fill with dewey / loc / nothing.
It's already in CVS & seems to work like a charm
does the new field "itemcallnumber"in 2.2 map to a MARC tag and if so, which one? This will be important for exporting (sharing) MARC record information (or, God forbid, migration).
In MARC21, I don't know. In UNIMARC, it's 995$k 995 being for item information in "recommandation 995", used by 95% of french libraries See http://www.adbdp.asso.fr/outils/infogestion/r995.htm (in french) for more informations -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.717 / Virus Database: 473 - Release Date: 08/07/2004
Steven F. Baljkas wrote:
Friday, July 9, 2004 17:39 CDT
Salut Paul,
Thanks very much for the quick response. Grand merci pour ta réponse
From what I read in IFLA's standards for UNIMARC, the 995 tag would be comparable to any of the 9xx tags in MARC21. That is, it's free (like beer or speech ;-) ) to use as system developpers/local librarians decide.
J'ai feuilleté la page à http://www.adbdp.asso.fr/outils/infogestion/r995.htm et si j'ai bien compris, le 995 dont les bibliothèques française se servent est comme le 852 de MARC21 (et dans la structure et dans les données y attachées). I skimmed the page you sent the link for and if I understood correctly, the 995 used by French libraries is like the MARC21 852 tag both in structure and data coded there.
The question remains though -- I think this was posed months ago now, but I don't remember seeing a response anywhere -- will there be/is there a *Koha MARC field* for the *call number used* ("itemcallnumber")? Donc cette question posée il y a quelques mois sans réponse évidente se présente encore : est-ce qu'il y a ou bien est-ce qu'il y aura *un seul champ de donnés MARC en Koha qui correspond au numéro de classification* (« itemcallnumber »)?
This could be a simple question of adopting a default standard which users could change if they desired. But it would be useful to have *one* MARC field that has the function of *call number used*. Many systems use/d tag 090 (as this was LC's itemcallnumber used for years) and many others make use of 852 or a 9xx tag. For simplicity sake, one could certainly use the French standard of 995 since that tag is not prescribed in MARC21. A défaut de tous les choix possibles -- dont les bibliothèques individuelles pourraient changer selon leurs goûts -- ce serait très utile pour les bibliothécaires et les bibliotechniciens d'avoir *un* champ MARC qui a d'abord la fonction du *numéro de classification utilisé*. Il y a plusieurs systèmes intégrés pour les bibliothèques qui utilisent/utilisaient le 090 -- car ceci était pour plusieurs années la norme LC utilisée pour « itemcallnumber » -- et d'autres qui utilisent le 852 ou bien un des 9xx. Pour la simplicité et l'unité de communauté Koha on peut très bien adopter le 995 utilisé en France car ce champ n'est pas prescrit en MARC21.
Will there be a decision on this by 2.2 or is this going to be left open? Est-ce qu'il y aura une décision par/avant l'apparence de 2.2 ou est-ce que l'on laisserait ainsi?
Merci en avance. TIA
(late answer...) In fact, you mix 2 differents things : the classification and the callnumber. The callnumber helps finding the book physically, in a shelf. The classification helps finding the book logically, in the database. Most libraries use as callnumber the same system as the classification. But not all. So, the callnumber is unique, while a given biblio can be classified in X differents classifications (dewey, LoC...) AND more than once for a given classification (2 dewey codes) In Koha 2.2, you will have X classifications (dewey, LoC or Other) and 1 callnumber. The callnumber being by default the same as dewey, LoC, other or empty (defined in systempreferences) HTH. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (4)
-
Hans Henderson -
Paul POULAIN -
Stephen Hedges -
Steven F. Baljkas