[Koha] Koha Digest, Vol 49, Issue 59
Amir Seni
amirseni at gmail.com
Tue Nov 17 18:15:32 NZDT 2009
-----Original Message-----
From: koha-request at lists.katipo.co.nz
Sent: Monday, November 16, 2009 19:47
To: koha at lists.katipo.co.nz
Subject: Koha Digest, Vol 49, Issue 59
Send Koha mailing list submissions to
koha at lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.katipo.co.nz/mailman/listinfo/koha
or, via email, send a message with subject or body 'help' to
koha-request at lists.katipo.co.nz
You can reach the person managing the list at
koha-owner at lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."
Today's Topics:
1. koha 2.2.8 + ubuntu (Kete Jourge)
2. Re: koha 2.2.8 + ubuntu (Chris Cormack)
3. Re: Acquisitions Vendor addresses (Paul Poulain)
4. Mitali P (phmitali at gmail.com) has sent you a private message
(Mitali P)
5. Re: Importing barrowing information - answer (Agnes Rivers-Moore)
6. Re: Barcodes on Label Batches (Davita Janto)
7. DBD driver has not implemented the AutoCommit attribute
Problem (DIMITRIOS A. KOUIS)
----------------------------------------------------------------------
Message: 1
Date: Sun, 15 Nov 2009 16:23:59 -0800 (PST)
From: Kete Jourge <activekete at yahoo.com>
Subject: [Koha] koha 2.2.8 + ubuntu
To: koha at lists.katipo.co.nz
Message-ID: <880638.79245.qm at web111919.mail.gq1.yahoo.com>
Content-Type: text/plain; charset="us-ascii"
hi
i'm tried to install koha 2.2.8 on ubuntu and i finished installation and can't open opac or intranet give me this page .. any help
thank's
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator, admin at root and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
More information about this error may be available
in the server error log.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20091115/e40d348e/attachment-0001.htm
------------------------------
Message: 2
Date: Mon, 16 Nov 2009 13:32:34 +1300
From: Chris Cormack <chris at bigballofwax.co.nz>
Subject: Re: [Koha] koha 2.2.8 + ubuntu
To: Kete Jourge <activekete at yahoo.com>
Cc: koha at lists.katipo.co.nz
Message-ID:
<606aab810911151632j2b026eb4mc5135d26fe531d60 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
2009/11/16 Kete Jourge <activekete at yahoo.com>:
> hi
> i'm tried to install koha 2.2.8 on ubuntu and i finished installation and
> can't open opac or intranet? give me this page .. any help
> thank's
>
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> Please contact the server administrator, admin at root and inform them of the
> time the error occurred, and anything you might have done that may have
> caused the error.
>
> More information about this error may be available in the server error log.
>
> ________________________________
Hi
Koha 2.2.8 is a very old, and totally unsupported version of Koha ....
why are you trying to install it?
Chris
------------------------------
Message: 3
Date: Mon, 16 Nov 2009 09:04:04 +0100
From: Paul Poulain <paul.poulain at biblibre.com>
Subject: Re: [Koha] Acquisitions Vendor addresses
Cc: "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz>
Message-ID: <4B010774.5010506 at biblibre.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Walls, Ian a ?crit :
> In the long run, I think it might be a good idea to allow for arbitrarily many addresses to be attached to any institution. This would separate the physical locations (like vendor PO boxes, shipping addresses, libraries branches) from the financial institutions (vendors, library Accounts Payable, etc.), and allow us to mix library financial institutions together with vendors (making consortial purchasing of resources easier to trace)
>
> Additionally, I really think that Vendor Contact should not be stored with the Vendor itself, but rather linked, again allowing for arbitrarily many contacts (each with a role). This would be extremely valuable for the development of a Koha Electronic Resources Management (ERM) system, since one often has different contacts at a company (sales, technical support, billing, etc.). Vendor contacts could then be assigned a level of permission on the system (or not), as the library deems appropriate.
>
> I have the beginnings of a proposal in the works, and I will publish it as an RFC when I'm confident it makes sense.
>
In the new_acq, that should be merged to main trunk as soon as galen can
take care of it, you can specify the "delivery branch". It can be
choosen from the branches list, and/or, a free text can be added (to
specify something that is not in the branches table, or to specify an
address that is not in the table at all).
That's a 1st step in the direction you suggest, Ian.
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08
------------------------------
Message: 4
Date: Mon, 16 Nov 2009 23:52:00 +1300 (NZDT)
From: Mitali P<noreply at ci.faniq.com>
Subject: [Koha] Mitali P (phmitali at gmail.com) has sent you a private
message
To: koha at lists.katipo.co.nz
Message-ID: <20091116105200.145951EF09E1 at daddy.katipo.co.nz>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20091116/50799c59/attachment-0001.htm
------------------------------
Message: 5
Date: Mon, 16 Nov 2009 12:28:50 -0500
From: Agnes Rivers-Moore <arm at hanover.ca>
Subject: Re: [Koha] Importing barrowing information - answer
To: Koha List <koha at lists.katipo.co.nz>
Message-ID: <4B018BD2.4090903 at hanover.ca>
Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
Forwarded solution
Agnes et Bernardo,
Because I so greatly appreciated your help getting this off the ground,
I decided to write up the steps I took to import the currently borrowed
book information from my old filemaker database into issues.
First step: The only useful information I had from my Filemaker database
was the borrower's First Name and the Barcode number for the book he has
checked out. (BTW, if you are working with Linux, you can install the
30 day trial of Filemaker 10 no problem with wine to export all your
data into CSV files.) Once I exported the data, I opened up the file in
a OOCalc, fixed the formating of names, looked for different versions of
the same person etc. I saved it as a tab file, and opened it in a
simple text editor. Then I made sure to find/replace and remove any
enclosing " or ' around string data, and saved it with tab delimiters.
Second step: open mysql (mysql -uroot koha -p)
Create a tempory table that will contain data agglomerated from your old
database and tables: issues, items, and borrowers:
mysql> create table borrowtemp ( barcode int(11), firstname text,
borrowernumber, itemnumber);
Import your tab delimited values file into the table:
mysql> load data local infile 'borrower.tab' into table borrowtemp;
Now, update borrowers with any borrower names that have checked out
books but haven't been added to "Patrons":
mysql> insert into borrowers (firstname, categorycode, branchcode)
select distinct borrowtemp.firstname, 'FRERE' as categorycode, 'RIM' as
branchcode from borrowers inner join borrowtemp on borrowers.firstname
!= borrowtemp.firstname order by borrowtemp.firstname;
(note, 'FRERE' is a category of Patrons that must already exist, and
'RIM' is the library code for a library which must already be created)
Now that the Patrons (borrowers) is populated and have all been assigned
a borrowernumber, you can update your borrowtemp with that information:
mysql> update borrowtemp, borrowers set borrowtemp.borrowernumber =
borrowers.borrowernumber where borrowtemp.firstname = borrowers.firstname;
Now, before we can get the barcodes of the books checked out to
borrowernumber, we have to grab the itemnumber corresponding to the
barcode in items:
mysql> update borrowtemp, items set borrowtemp.itemnumber =
items.itemnumber where borrowtemp.barcode = items.barcode;
Finally, the issues table can be populated with the borrowed books:
mysql> insert into issues (borrowernumber, itemnumber, date_due,
branchcode) select borrowtemp.borrowernumber, borrowtemp.itemnumber,
date_add(CURDATE(), interval 8 month) as date_due, 'RIM' as branchcode
from borrowtemp;
(As you can see, I set the date_due to eight months from the current
date, which you can change as you see fit - our old system did not have
due dates! And of course, once again 'RIM' is the Library code.)
Thanks again for your help! I hope this can help someone who finds
themselves in a similar migration situation!
-BFT
On Tue, Nov 10, 2009 at 5:21 AM, Agnes Rivers-Moore <arm at hanover.ca
<mailto:arm at hanover.ca>> wrote:
Hi
I'm afraid I can't help with MySQL. This all depends so much on what
data you have in your old system, and how it is stored.
There is a summary at http://www.kohadocs.org/migrating_to_koha.html,
for a much older version of Koha but the principles and main tables are
still relevant. Many more useful notes at http://wiki.koha.org/doku.php
A diagram of the tables with the field names on
http://wiki.koha.org/doku.php?id=en:development:dbschema:3.01 and see
others on the wiki.
However, it will be up to you how to decide which piece of data from
your old system should be mapped to which field of the new one. When you
have all your borrowers and books in Koha, you will need to identify
borrower by barcode, extract the borrowernumber, identify the book,
extract the itemnumber, and insert those to the issues table with some
kind of due date.
HTH
Agnes
Br. Francis Therese Krautter wrote:
Thank you for the reply...
The only information I need is to attach a patron's name, or the inverse
to a barcode to show that they currently have the book. You are talking
about the different tables - the idea seems ok conceptually, but I have
no idea how to go about doing it - as I am brand new to koha and have
very limited experience with mysql. I am just starting to get
comfortable with the marc system, though I still seem to be importing
values for something (other than state) which cause books to become
"missing" or lost, when they are not.
Maybe you could point me to the references I need in order to make some
progress with the tables thing.
Your aide is greatly appreciated!
-BFT
On Mon, Nov 9, 2009 at 12:43 AM, Agnes Rivers-Moore <arm at hanover.ca
<mailto:arm at hanover.ca> <mailto:arm at hanover.ca <mailto:arm at hanover.ca>>>
wrote:
This is a fairly complicated process, it depends how much of the
circulation data you hope to transfer.
You can add some of it to the 952 field in a MARC record - this
can accommodate fields such as $l (letter l) number of times
borrowed, and $q due date of item if currently checked out. If you
can tell where this information resides in your old system, you
can write a script to insert it to the MARC records and them the
bulk MARC import process will include that in the item details.
However this does not tell you who has each item. That would need
to be imported to the issues table, as Chris says, and link to the
borrowers table for the details of the person who has the item.
Issues link to the borrower table through 'borrowernumber' and to
the items table through 'itemnumber', and needs data such as
branchcode, issuingbranch, date_due, issuedate, and timestamp.
There is also oldissues, which holds the history of all completed
checkouts.
HTH
Agnes
Br. Francis Therese Krautter wrote:
> Hello,
>
> I am still working on importing data into koha. We have a rather
> large database and I am trying to move it over, most of it has moved
> so far, but one major importation I can't figure out how do is all the
> currently borrowed books. I can't find a marc field or a koha
> variable that looks like it contains this information. There are over
> 1000 books currently checked out, I really don't want to have to do it
> by hand!
>
> -BFT
> ------------------------------------------------------------------------
>
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
> ------------------------------------------------------------------------
>
> This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com
--
Agnes Rivers-Moore
Assistant Librarian
Hanover Public Library
--
Agnes Rivers-Moore
Assistant Librarian
Hanover Public Library
------------------------------
Message: 6
Date: Sun, 15 Nov 2009 20:37:48 -0800 (PST)
From: Davita Janto <davita.janto at yahoo.com.au>
Subject: Re: [Koha] Barcodes on Label Batches
To: Chris Nighswonger <cnighswonger at foundations.edu>
Cc: koha at lists.katipo.co.nz
Message-ID: <761893.60192.qm at web110003.mail.gq1.yahoo.com>
Content-Type: text/plain; charset="utf-8"
Legend! Thank you very much for your help.
Using the other labels.pm
Davita.
__________________________________________________________________________________
Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7.
Enter now: http://au.docs.yahoo.com/homepageset/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20091115/69c43c09/attachment.htm
------------------------------
Message: 7
Date: Sun, 15 Nov 2009 13:34:54 -0800 (PST)
From: "DIMITRIOS A. KOUIS" <dkouis at gmail.com>
Subject: [Koha] DBD driver has not implemented the AutoCommit
attribute Problem
To: koha at lists.katipo.co.nz
Message-ID: <26363659.post at talk.nabble.com>
Content-Type: text/plain; charset=us-ascii
Hi all,
We are facing the DBD driver autocommit problem with debian-lenny and koha
3.0.4.
The system works fine at the initial installation and after the first reboot
the problem appears.
Is this logical ? Has anyone solved this problem (we followed the guidelines
for seperate installation of certaion components but nothing....)
Thanks in advance,
Dimitris Kouis
--
View this message in context: http://old.nabble.com/DBD-driver-has-not-implemented-the-AutoCommit-attribute-Problem-tp26363659p26363659.html
Sent from the Koha - Discuss mailing list archive at Nabble.com.
------------------------------
_______________________________________________
Koha mailing list
Koha at lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
End of Koha Digest, Vol 49, Issue 59
************************************
More information about the Koha
mailing list