Hi, I'm using Koha 2.0.0 and have a few of questions that I'm hoping someone can help me answer. The Koha I have set up has MARC on and is using simple acquisitions. 1. biblio-to-biblioitems relationship. I have read about the biblio-biblioitems-items relationship that Koha uses. But from what I can see, there seems to be a strict one-to-one relationship between every biblio record created and every biblioitems record created. In other words, for every book I enter there is always one biblio record and one biblioitems record created. It seems there is no way to have 2 biblioitems associated to the same biblio. Looking at the code, it looks like with the configuration MARC=on and acquisition=simple, this will always be the case. Is this true, or am I missing something? 2. MARC links I've seen in previous posts/documents on the topic of creating links from MARC subfields to Koha fields that, for the items table, all MARC subfields must be in the same tag. This raises some questions: a- Can the other subfields of this tag that is not used for linking to an items field be used in other Koha fields (for instance, for a field in the biblioitems table)? b- Is it legal to map the same subfield to 2 different Koha fields? For example, to map Dewey 082$a to both biblioitems.dewey and items.bulk? c- Out of curiousity, what MARC tag are people using for the items fields? I've seen both 852 and 952 mentioned, but 952 seems very limited in the number of subfields that can be used given the number of items fields that are available t be mapped. d- I think I saw it mentioned that subfields of the same tag cannot be spread across more than one of the 10 tab pages; they must reside on the same tab page. Is this true? 3. editing an items record for an existing entry One field that I would like to have available to the librarian for editing is items.itemnotes. However, it seems that the items configuration page (additem.pl) is hidden behind the MARC configuration page (addbiblio.pl); one must select a biblio to edit and then save it before the items configuration page is shown. Is this the only way to reach this page? 4. creating a call number I would like to have a field in the items record that indicates the call number that patrons can use to search for the book on the shelves. Excuse me if my terminology is not accurate; I'm using call number to mean the text on the spine label, e.g.: REF 200.973 BAR I've seen several posts on this topic in the archives, but I have to ask this: how does one get the info from the 3 fields (item type, dewey, author) mapped to, for example, items.bulk? Can this be done programmatically within Koha, or is this intended to be a manual operation? If it is possible to be done programmatically, ideally this items.bulk field will show this data populated once the user saves a new biblio in addbiblio.pl and is is moved to the items configuration page (additem.pl). Has anyone gone through these contortions before? 5. Quick Search on ItemType When I attempt to do a search on ItemType from the Quick Search menu, I find that the search will always fail with no results found unless I put a space in the Author or Title field as well. Anyone notice this? Any help that anyone can shed on this will be MUCH appreciated. Thanks, Lee
Lee, I'll try to answer a couple of questions: Harvey Lee said:
1. biblio-to-biblioitems relationship. I have read about the biblio-biblioitems-items relationship that Koha uses. But from what I can see, there seems to be a strict one-to-one relationship between every biblio record created and every biblioitems record created. In other words, for every book I enter there is always one biblio record and one biblioitems record created. It seems there is no way to have 2 biblioitems associated to the same biblio. Looking at the code, it looks like with the configuration MARC=on and acquisition=simple, this will always be the case. Is this true, or am I missing something?
No, you're not missing anything, it's true. This comes about because of the nature of MARC records, which are "two-part": the basic bibliographic information tags, plus some tags for holdings information. When your try to fit such records into the three Koha tables, the basic bibliographic information gets split into the biblio and the biblioitems tables. So when you use MARC records, you end up with a one-to-one relationship between your biblio records and your biblioitems records. (When you don't use MARC records, this doesn't happen.)
2. MARC links I've seen in previous posts/documents on the topic of creating links from MARC subfields to Koha fields that, for the items table, all MARC subfields must be in the same tag. This raises some questions: a- Can the other subfields of this tag that is not used for linking to an items field be used in other Koha fields (for instance, for a field in the biblioitems table)?
I think not. Nelsonville actually splits it's MARC holdings tag into two separate tags before records are imported (using the MARC::Record module) to work around this.
b- Is it legal to map the same subfield to 2 different Koha fields? For example, to map Dewey 082$a to both biblioitems.dewey and items.bulk?
Nope, Koha will keep the mapping that was defined last, not both.
c- Out of curiousity, what MARC tag are people using for the items fields? I've seen both 852 and 952 mentioned, but 952 seems very limited in the number of subfields that can be used given the number of items fields that are available t be mapped.
I mentioned that Nelsonville splits theirs. The original records before import contain a 952 tag, but part of that information is split out into a 942 tag, which is then mapped to some biblioitems columns.
d- I think I saw it mentioned that subfields of the same tag cannot be spread across more than one of the 10 tab pages; they must reside on the same tab page. Is this true?
The tabs are for displaying your MARC records, so I'm not sure why you would want to split the display of any single tag. (Do you mean like having 245a in one tab and 245b in another?) But I really don't know the answer to this question.
3. editing an items record for an existing entry One field that I would like to have available to the librarian for editing is items.itemnotes. However, it seems that the items configuration page (additem.pl) is hidden behind the MARC configuration page (addbiblio.pl); one must select a biblio to edit and then save it before the items configuration page is shown. Is this the only way to reach this page?
So far as I know, unless you are willing to do some template modifications. (Someone else may have devised a secret shortcut.) -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
Hi everyone, I am new in the field and am really interested in this list. To introduce myself, I am a systems librarian in Moi University, Kenya. Most of the institutions heve not automated their libraries. I was installing Koha and I just landed in a problem with mysql.socket. It keeps disappearing from where it ought to be: /var/lib/mysql/ I am using SuSe Linux version 9.0; could someone tell me how to protect this? I have tried all means but I keep on loosing it and therefore have not managed to fully install Koha. Solomon K. Mutai The Margerat Thatcher Library P.O. Box 3900 Eldoret Kenya TEL: 254-53-43720 FAX: 254-53-43047
Solomon Mutai a écrit :
Hi everyone,
I am new in the field and am really interested in this list. To introduce myself, I am a systems librarian in Moi University, Kenya. Most of the institutions heve not automated their libraries.
I was installing Koha and I just landed in a problem with mysql.socket. It keeps disappearing from where it ought to be: /var/lib/mysql/
Probably a problem of mySQL not being running. Check that the dir of mysql datas can be read & written by mySQL (chown -R mysql.mysql /var/lib/mysql as root on Mandrake) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On Mon 03 May, Solomon Mutai wrote:
Hi everyone,
I am new in the field and am really interested in this list. To introduce myself, I am a systems librarian in Moi University, Kenya. Most of the institutions heve not automated their libraries.
I was installing Koha and I just landed in a problem with mysql.socket. It keeps disappearing from where it ought to be: /var/lib/mysql/
I am using SuSe Linux version 9.0; could someone tell me how to protect this? I have tried all means but I keep on loosing it and therefore have not managed to
The first version of Linux I used was Red Hat. I was not happy with it or the next version I tried (Mandake). I then bought Suse 9 which was *immeasurably* better in my view. YAST, the Suse system of loading software, seemed to me to be so much better than any of the other systems (except Debian which I have not tried). And the inclusion of printed manuals was an advantage. But so far as MySQL is concerned it just does not work. I have tried loading it, and reloading it, and I get the same sort of symptom that you refer to (save that I do not get the socket at all). The cure so far as I was concerned was not to use YAST but to go to the MySQL site and download a RPM file and to install that according to the instructions in the online manual: the socket appeared in the appropriate file. I asked Suse and they said that this was not something covered by their support program and that I was on my own. Since they are trying to suggest that they are the real replacement for MS this seems to me to be a bit stupid, quite apart from presumably being a bug. Roger -- Roger Horne, 11 New Square, Lincoln's Inn, London WC2A 3QB mailto:roger@hrothgar.co.uk http://hrothgar.co.uk/YAWS/
Roger Horne a écrit :
But so far as MySQL is concerned it just does not work. I have tried loading it, and reloading it, and I get the same sort of symptom that you refer to (save that I do not get the socket at all).
The cure so far as I was concerned was not to use YAST but to go to the MySQL site and download a RPM file and to install that according to the instructions in the online manual: the socket appeared in the appropriate file.
I asked Suse and they said that this was not something covered by their support program and that I was on my own. Since they are trying to suggest that they are the real replacement for MS this seems to me to be a bit stupid, quite apart from presumably being a bug.
Try to edit /etc/my.cnf & change socket location : |[client] port=3306 socket=/tmp/mysql.sock HTH, but it's strange that suse is not shipped with mySQL working... | -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
oups... it's |[mysqld] not [client] mail sended a little bit too fast. | -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (5)
-
Harvey Lee -
paul POULAIN -
Roger Horne -
Solomon Mutai -
Stephen Hedges