- Koha - lists.katipo.co.nz

more than 1 admin user name and password?
by Octavee Uhl 19 Jan '08

19 Jan '08

Is it possible in koha 2.28 to have more than 1 admin user? Right now we have kohaadmin as the main library user. Since we have several people to do the data entry we would like to have a seperate user name for each. Thanks Octavee -- View this message in context: http://www.nabble.com/more-than-1-admin-user-name-and-password--tp14963095p… Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 2

KUDOS User Group meeting at PLA
by Deb Bergeron 18 Jan '08

18 Jan '08

Good Morning! Forgive the cross-posting. It's time to begin planning the next KUDOS meeting at PLA. Based on the conversation from the KUDOS meeting at ALAMW08, we'd like to have the following: * Break-out sessions for non-hosted Koha Users * Break-out session for hosted (via LibLime) Koha Users * The following agenda for all since we didn't get to it at the last meeting: o * Do we need a formal users group for Koha? * Develop a mission statement. * What type of structure do we need? * Form a committee of three to write a by-laws proposal. * Other issues. * Should there be a dues structure? * Schedule next meeting. I'm looking for volunteers to help organize the PLA meeting. Please let me know if you'd be interested in helping. You don't need to attend PLA to help. I live in Minneapolis, so I'm available to attend the meeting physically. Additionally, there is interest in having audio conferencing available on the day of the meeting as well. If you are interested in helping to organize this meeting, please contact me before the end of the day Wednesday, January 30, 2008. Thanks so much! Deb -- Deb Bergeron <mailto:bergeron@macalester.edu> System Admin: User Support CLIC Consortium <http://clic.edu> 1619 Dayton Avenue, Suite 204A Saint Paul, MN 55104 O:*651.644.3878* C:*651.487.7609* F:651.644.6258

1 0

koha3 import
by Bünzli Daniel 18 Jan '08

18 Jan '08

Hello, I fail to see how one should proceed to import records and link them to author authorities. I thought that importing the authorities first with bulkauthimport.pl and then records with bulkmarcimport.pl would do it but authorities do not get linked to biblios. Is there anything more I need to do/run ? Or should I try to make koha accept my own authority id numbers (how ? bulkauthimport drops 001) for authorities and directly generate my marc records with this id in 7XX $9 ? Besides in the cataloging interface is it possible to force the cataloger to choose an element from the thesaurus ? Currently I can put anything in the fields and it will create a new authority, I don't want this, errors can creep in too easily. Is there a way to change this ? Best, Daniel

1 0

koha3 bulkauthimport problems
by Bünzli Daniel 18 Jan '08

18 Jan '08

Hello, bulkauthimport refuses to import my $b fields. Here's my marc file : > > ./dumpmarc.pl -file ~/tmp/koha/a.marc > > LDR 00116nx a2200061 45 > 001 9461 > 010 _a20080101afref50 ba0 > 200 1 _aPELLETIER > _bWilly > LDR 00144nx a2200073 45 > 001 10813 > 010 _a20080101afref50 ba0 > 200 1 _aROLLAND > _bHugo > 400 1 _aABATE > _bErasmo So everything seems right here. Here's what happens when I import : > > ./bulkauthimport.pl -c UNIMARC -v 2 -d -file ~/tmp/koha/a.marc > deleting authorities > CHAR : UNIMARC > 1 ==>LDR 00116nx a2200061 45 > 001 9461 > 010 _a20080101afref50 ba0 > 200 1 _aPELLETIER > _Ub > _WUNIMARC at ./bulkauthimport.pl line 112. > ADDED authority NB 1 in DB > 2 ==>LDR 00144nx a2200073 45 > 001 10813 > 010 _a20080101afref50 ba0 > 200 1 _aROLLAND > _Ub > _HUNIMARC > 400 1 _aABATE > _Ub > _EUNIMARC at ./bulkauthimport.pl line 112. > ADDED authority NB 2 in DB > 2 MARC record done in 0.281389951705933 seconds But in Koha (3.00.00.046) there's nothing in the $b field Can anyone enlight me ? Best, Daniel P.S. The file can be found here http://erratique.ch/tmp/a.marc

1 1

Re: Re: [Koha] Thumnail images in catalog searchresults? (Was:details automatic
by BWS Johnson 18 Jan '08

18 Jan '08

Salvete! Well shucks that was blush inducing. Thank you so much! You've been a major part of the cataloguing muscle over the years, for which I am very grateful. I, too, have oft mistaken Owen for Stephen. Luckily Stephen is such a solid guy that he points the credit in the right direction. This development over the years of good will has made this community strong. Everyone has a little hand in everything, and there are stellar release managers that give until it hurts, but the quantum leaps of which you speak wouldn't be possible without an army of tiny tweakers. There's the snowball effect, but this is an avalanche :D Thank you everyone! It makes it very easy to get out there and recommend this project. Cheers, Brooke

1 0

Re: Re: [Koha] Thumnail images in catalog search results? (Was:details automatic
by Steven F.Baljkas 17 Jan '08

17 Jan '08

Thursday, January 17, 2008 17:05 CDT Greetings Brooke, et al.! Just a quick response to your posting ... > From: "BWS Johnson" <mhelman(a)illinoisalumni.org> > Date: 2008/01/16 Wed PM 02:10:58 CST > To: <koha(a)lists.katipo.co.nz> > Subject: Re: Re: [Koha] Thumnail images in catalog search results? (Was:details automatic > Salvete! > Is this in the current version? There are so many new bells and whistles > it's staggering :) I know. It's mindboggling to look back over the last several years and see the quantum leaps that the programmers and developpers have achieved. :-) > > Anyone interested can let me know either on the listserv or off > > and I'll get to it pronto. Well, as promised, I found it. More on that in a second. Since no one else expressed interest but Fred, I only had to forward it to him off listserv. I will post the information I retrieved below in a moment, just in case anyone else is curious or might find it useful to follow up on as Joshua suggested (volunteers?). > If it's not, I can only imagine there are a lot of folks that are > interested. There's a way to make images for Patrons show up, and I know > I'm not a coding guru, but I would think that you might wish to look at > the way that code is handled in hopes of saving you a bit of time. As I remarked to Fred, Brooke, that is an EXCELLENT bit of advice. You are the Muse of Koha! :-) > > up one's own number. That way, items without ISBNs could be made to > > display something (now or in the future, as one chooses) e.g. CDs, > > websites. Items with ISBNs could have their numbers copied over into the > > linking field using a utility like MARCEdit, etc. to make such global > > changes easier. > *nod* That sounds great. I abuse the poor 856u field, but this sounds > more flexible than a URL thang, which is awesome. No, it's not an abuse. After all, there is a built-in indicator code for other related resource uses so someone at LC must have imagined this possibility somewhere along the way. > > Very excited about the new release, Joshua. Congratulations to you and > > all the programmers and developpers who've made this great step forward > > possible! > Yes, thanks guys :) > I have to wonder about folks in the Library community starting a hoot > and hollerin' over public domain cover images. It seems as though in an > ideal world LOC would have a bank of images as part of the CIP process > so that everyone would be able to link or copy to it... (I know this is > beyond the scope of the Koha project, but heck, it's important enough to > mention, methinks...) I adore you! I suggested the very same thing back in library tech training in 1998. People are so visual in their search habits, it really only makes sense. <sigh> Well, maybe one day some big organisation will take it on. Or perhaps the sum total of all the littler players will accomplish the same goal. It's a nice idea/dream in any case. And now, back from the reverie to reality: an apology owed Owen. As I discovered, inevitably, my memory had played some tricks on me again: it was Owen Leonard who had provided the answer, and Stephen Hedges who had forwarded the matter to him. Sorry, Owen. My silly brain tends to label things by the person I first asked for help. In any case, I did not intend to remove credit where it is due. The entire contents of the 2 messages (including some irrelevant bits) follows beneath my signature line. Like Brooke, I am no coding guru, but it does seem to me that the last part of his answer below will still apply. In any case, I do hope this helps a bit for anyone interested. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada ============================================================================ MESSAGES FROM OWEN LEONARD REGARDING AMAZON AND COVER IMAGE LINKING ISSUES ============================================================================ From: Owen Leonard Date: September 20, 2005 1:46 PM To: Steven F. Baljkas CC: Steven F. Baljkas; oleonard(a)athenscounty.lib.oh.us <oleonard(a)athenscounty.lib.oh.us>; jferraro(a)athenscounty.lib.oh.us <jferraro(a)athenscounty.lib.oh.us> Subject: Re: Hopefully simple question re: NPL template book cover images > > My two 'experts' thought that linking to internal images would be do-able, > > but suggested I ask a real Koha expert: that means, you! :-D At one point I'd hatched complex schemes for downloading and storing Amazon images on our own server so that we'd be hitting them only once. We switched to direct linking before it could really be developed. > > Would I need to add a field to the MYSQL table to hold the 001 numbers, or > > would there be a way of changing the HTML display template simply to look > > for the number from the 001 as it is in MARC? One option might be to find a field in the Koha tables that you're not using for data and re-purpose it for your 001 number. Then you could map the MARC field to that column in the table. Otherwise you'd have to re-write the scripts to specifically query that MARC field. Right now the search results page and the biblio detail page either use the "old" Koha tables (biblio,biblioitems,items) or query specific areas of the MARC record (for example, detail.pl uses the getMARCnotes subroutine which grabs any field between 500 and 599). You'd have to write your own 'getMARCimage' routine or something like it. > > still not all clear on > > what it is exactly that Koha does with the MARC records, but I thought it > > was just reading the info from the MARC into whatever tables it really > > uses behind the scenes.) Like I said, for the search results page and the detail page, Koha mostly relies on the non-MARC tables, using data that has been mapped from the MARC record to the biblio tables. A couple of subroutines exist to extract MARC-specific data for the detail page (getMARCnotes and getMARCsubjects), but otherwise if you're looking at MARC data (like on the MARCdetail page), you're getting the whole record. That makes it hard to pick and choose what piece of the record you want to display. > > one enhancement that DSA and I had discussed: a pop-up window to afford a > > view of a larger cover image. Here's one way to do it (using Amazon's images):  <a href="http://images.amazon.com/images/P/.01.LZZZZZZZ.jpg" onclick="window.open('http://images.amazon.com/images/P/.01.LZZZZZZZ.jpg','cover','width=325,height=495,toolbar=false,scrollbars=yes'); return false;"> <img src="http://images.amazon.com/images/P/.01.MZZZZZZZ.jpg" alt="Book Cover Image" /> </a> -- Owen ============================================================================ From: Owen Leonard Date: September 21, 2005 9:20 AM To: Steven F. Baljkas Subject: Re: Re: Hopefully simple question re: NPL template book cover images > > switched to direct linking before it could really be developed. > > How will it work in the long term, though? As books are no longer published, Amazon.com changes its numbers from ISBNs to ASINs and deletes the images. Sure, that's a possibility. That's another reason you might want to store your images locally. Won't that mean that patrons will be returning to the OPAC over time but finding the book cover info available constantly in flux? > > > > > Would I need to add a field to the MYSQL table to hold the 001 numbers, or > > > > would there be a way of changing the HTML display template simply to look > > > > for the number from the 001 as it is in MARC? > > > > One option might be to find a field in the Koha tables that you're not > > using for data and re-purpose it for your 001 number. Then you could map > > the MARC field to that column in the table. [snip] > I can recode MARC records easily enough. Are there particular fields that you would recommend in the Koha tables, ones normally unused (if that makes sense)? I'm not at all sure I know which fields in the Koha tables are using what data. It depends on how you did your MARC setup. For instance, we put our whole call number in biblioitems.classification rather than using biblioitems.dewey, biblioitems.subclass, etc. You might have a column that you're not using for any relevant data. > Also: wasn't there are diagram of this at some point in the past (vague memory) of the Koha tables structure? Is something like that still available? There's the 'database' section (5.3.8) of this document: http://www.kohadocs.org/Koha_architecture.html > Does this mean, incidentally, that the problem with the subject headings has been solved? Kim was asking about that earlier this week, n'est-ce pas? There have been a couple of changes to the way subjects are handled recently, so it's possible it is now at a place where it can be considered solved. I'd have to look at it more closely to be sure. > Thank you again for the syntax for that. I am sure it will be of help, although I would remain committed to avoiding use of Amazon.com for cover images. I absolutely understand your reluctance to use Amazon images. I would have preferred that we not link to them directly either, but that was just my personal feeling. The code snippet I sent would only have to be changed with regard to the image location--point it to the image on your server rather than Amazon's. The easiest way to accomplish that is to name the cover images according to the ISBN, or whatever id number you're using to identify the images. -- Owen ============================================================================ ============================================================================ ============================================================================ _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: BulkMarcImport done?
by Lawrence Bean 17 Jan '08

17 Jan '08

>Lawrence Bean writes: >I was able to get the "bulkmarkimport.pl" script to work, with the result: >"3995 MARC record done" >from the Winnebago export file. Let me know if anything looks different >on your end, and what I can do next. Laura Phelps writes: > >I wish I could report that all is well now... but unfortunately, I can't >discern any difference. The items seem to still be in the reservoir and >I can't figure out how to move them. Hello list. I (tech) was able to export our MARC records from our current Winnebago system and used the koha web interface to upload them to the reservoir. Laura and Megan (Librarians) could see the recods in the reservoir, but were daunted by the thought of moving each into the catalog one at a time as an acquisition. The answer appeared to be to use the bulkmarkimport.pl script, which I was able to do successfully with the same marc export file from Winnebago I used for the web interface upload. I watched as the terminal output counted off each marc record as it was processed. The librarians report, however, that after doing this they do not "see" what they believe they should be seeing in the catalog. Would a librarian from the list be willing to communicate directly with them to verify whether or not the bulkmarcimport.pl script did what it was expected to do? LPhelps(a)u47.k12.me.us MFuller(a)u47.k12.me.us We are currently using koha 2.2.9 on Debian, and before this step the only things we have done is the basic setup for fields and branches and such. I saved this initial MySQL database before proceeding on to this step. At this point in time, just starting out, would anyone suggest it would be beneficial for us to jump right to 3.0a before we continue and "restore" the initial saved database (2.2.9->3.0a database upgrade issues?), or as beginners would it be better for us to stick with 2.2.9 until 3.0 is out of alpha?

1 0

Re: About best use of z39.50
by Ata ur Rehman 17 Jan '08

17 Jan '08

Dear Khaled Congratulations on z39.50. For a list of z39.50 databases please follow the link: http://targettest.indexdata.com/ Regards, Ata On Jan 17, 2008 12:48 PM, Mohammed Abu Khaled Chowdhury <makc75(a)yahoo.com> wrote: > Dear Sir, > Thanks again. We have installed Yaz toolkit and now z39.50 protocal working > nicely. Just one thing I would like to informed from you. Would u pls let me > know some more database address ( at this moment we are using default two > database which is not enough to find and import a good number of book. > z3950.libris.kb.se > > z3950.loc.gov) > > Best Regards > Khaled > > > Mohammed Abu Khaled Chowdhury > Librarian > Research and Development Wing > Military Institute of Science and Technology (MIST) > Mirpur Cantonment, Mirpur, Dhaka-1216 > Phone: 88-02-8012511-20, Ext 517 > Fax: 88-02-9011311 > E-mail: makc75(a)yahoo.com and khaled(a)mist.edu.bd > > ________________________________ > Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it > now.

1 0

Seeing help in koha implementation
by deepak 17 Jan '08

17 Jan '08

Hi all, I am working at DESIDOC, the information service provider and technology laboratory of DRDO. It has a huge library too. I am exploring options to migrate to open source ILS KOHA. Presently, we are using in-house developed automated library system called DLAS (developed in VB, MS Access and JSP). I have installed KOHA (v2.2.9) in one server along with other required software and it seems to be working fine. but it is barcoded. our existing ILS can export data in ASCII and ISO 2709 formats which can be used to import data in koha. but the main problem use of barcodes...our library is not barcoeded and koha v 2.2.9 works with barcode... Kinldly let me know whether can we use Koha without getting our library BARCODED. Is there any version of koha wihich works without barcodes (using accession or acquisition number). Looking forward for prompt reply... Regards, Deepak kumar Vishwakarma Scientist, DRDO DESIDOC, Metcalfe House Delhi, India. -------------------------------------------- _______________________________________________________________ The contents of this Email communication are confidential to the addressee. If you are not the intended recipient you may not disclose or distribute this communication in any form but should immediately contact the Sender. The information, images, documents and views expressed in this Email are personal to the Sender and do not expressly or implicitly represent official positions and policies of DRDO and no authority exists on behalf of DRDO to make any agreements, representations or other binding commitment by means of Email.

1 0

Status of Koha 3 Translations (two weeks remaining)
by Joshua Ferraro 17 Jan '08

17 Jan '08

Hi all, Since the announcement on January 8th (8 days ago) that Koha 3 is ready to be translated, we've heard from dozens of translators around the globe who have collectively agreed to translate Koha into over 26 languages! So first off, a big round of applause to all who have volunteered! Just to give you all an update, I just approved all pending translations, and we're up to about 16% completion for all translations. Some are finished, and some haven't been started yet. Please bear in mind the deadline for submissions is 1 February, just two weeks away! I'll send another reminder in about a week. In the meantime, happy translating everyone! Finally, for those who would like to translate Koha into their langauge, and missed the original email, here are the relevant instructions (most folks seem to be using the web-based translation manager FYI): 1. Please take a look at http://translate.koha.org. Some translations already exist; please consider taking over an existing translation rather than starting a fresh one, unless the existing one is un-usably poor :-) 2. Please post your intent to translate Koha to the koha-translate list: http://lists.nongnu.org/mailman/listinfo/koha-translate In your email, please specify your Language, and Country/Region (and if your language uses a non-latin script, please also indicate the Script). Koha uses RFC4646 for managing language subtags, so it's important that we know all of those aspects of the language you're providing. It's important that you post your intent, this way we can avoid overlap and perhaps can even do some collaboration. Note: even if you've contributed a contribution previously, please announce your intent so we can have you on record for the 3.0 version. 3. Determine the application you intend to use to do the translation. You have a few options: a. http://translate.koha.org will allow you to add your translations via a web-based interface. If your language, region, country and script are not listed, please email me and I will add them. b. Desktop Application - there are a few: LocFactory Editor (for OSX), POEdit (for Windows), Kbabel (for Linux). If you use a desktop application, please ensure that your encoding is set either UTF-8 or UTF-16, depending on your language's script support in UTF-8. Most languages should use UTF-8. c. Text file -- yes, you can edit POT files directly in a text editor, but please make sure you have the proper encoding as with the Desktop application. 4. Obtain the Translation Files. (doesn't apply if you use translate.koha.org) You need to copy two files from the Koha 3.0 repository, one for the OPAC, and one for the Staff Client: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=blob_plain;f=misc/translato… 5. Naming your files. (doesn't apply if you use translate.koha.org) Starting with Koha 3, we're using RFC4646 language subtag naming conventions, (have a look at http://www.w3.org/International/articles/language-tags/ for an intro). RFC4646 has a concept of 'extensions' that Koha uses to tag for the 'theme' (t) 'interface' (i) and 'version' (v). For example, if you're creating a French translation from France, for the staff interface, and version 3.00.00.00, the filename would be: fr-FR-i-staff-t-prog-v-3000000.po 6. If you've used translate.koha.org to submit your translation, when you have finished, the system will have that indicated on the report (100%). Otherwise, you'll have to send the file to us somehow. You can do that via email to the list (in which case i recommend creating an archive of the completed files, rather than sending them through in raw format). Or, if you are reasonable comfortable with the command line, you can submit them via Git as a patch. Here are the basic instructions for how to contribute using Git: http://wiki.koha.org/doku.php?id=en:development:git_usage Translations go in the misc/translator/po file, and should utilize the standard naming conventions. If you have a question, don't hesitate to ask. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0