- Koha-devel - lists.koha-community.org

880 filed
by Morsy, Amal 25 Sep '13

25 Sep '13

Hallo, We have several books in Arabic and other languages that we like it to be displayed in its original language in the catalog. We would like to make a use of 880 filed. We want to enter the author name in English and display it in the other language as well and make it searchable My question is how I can add 880 filed to the 20000 records in the library without risking losing any of the existing data? And if I want to add 880 filed to a new framework for the future cataloging, how can I do that? I appreciate if there are tutorials about these issues. Thank you in advance for your help Amal -- * Amal Morsy * *Library Director * 202-785-1141 ext. 222 <http://www.mei.edu/> Providing non-partisan, expert information and analysis on the Middle East. For additional information please visit www.mei.edu | 1761 N STREET NW, WASHINGTON, D.C. 20036-2882 <https://twitter.com/MiddleEastInst>@MiddleEastInst<https://twitter.com/MiddleEastInst> | <https://www.facebook.com/middleeastinstitute> Middle East Institute<https://www.facebook.com/middleeastinstitute> | <http://www.mei.edu/feeds/analysis> MEI Analysis & Opinion<http://www.mei.edu/feeds/analysis> **

1 0

Re: [Koha-devel] Test Request
by Paul 25 Sep '13

25 Sep '13

At 09:37 AM 9/24/2013 -0700, Galen Charlton wrote: >Hi, > >On Tue, Sep 24, 2013 at 9:31 AM, Paul Poulain ><<mailto:paul.poulain@biblibre.com>paul.poulain(a)biblibre.com> wrote: >Overall, in public libraries, it's probably a rare situation, while in >an academic one, it's more common. > >We've at least one library that would love this feature ;-) > >Thanks, it is very helpful to know that there is at least one library >(beside's the patch submitter's) who would be interested. I'm also interested, but not certain that the scenario is identical. I'm looking for a way to hide some items from "not-logged-in" users (i.e. the great big public on the WWW), but allow our "logged-in-members" (WAN and LAN) to be able to find them. Best - Paul

2 1

writing a file on server from staff interface
by Mathieu Saby 25 Sep '13

25 Sep '13

Hi for my patch about facets, I currently have 2 problems : 1- how to put the file in /etc/ of installation directory (in discussion) 2- how to allow the perl script (from staff interface) to write or rewrite the yaml configuration file if a librarian decides to change some settings. If I do nothing special, YAML::DumpFile fails to (re)write the file, because - I suppose - the apache user does not have rights to access the server. So, for the moment, the only way I found to make my config file editable is "chmod 666". But I suppose it is not very safe... Do you know if there is a safer way to do that? How is managed for example for SolR configuration files? Regards Mathieu -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

5 8

Test Request
by Mark Tompsett 24 Sep '13

24 Sep '13

Greetings, Seeing as there is very little time left before the feature freeze, I was wondering someone could look at bugs 10900, 10895, and 10589. 10900 corrects a bunch of ugly scariness related to set_userenv in C4::Context. This allows 10895 to be tested on 10589. I realize that I should have put the test for 10589 on the same bug, but at the time, the 10589 was signed off. Sadly, I had to rebase, and all three need sign off. 10589 allows changing the scope of OpacHiddenItems based on Patron Category. For example, one category (let’s say cataloger) could search for hidden items in OPAC for just their branch, while another category (let’s say staff) could search for hidden items in OPAC across all branches, while another category (let’s say patrons) wouldn’t see any of the hidden items. This is configurable via two new system preferences PatronSingleBranch and PatronEveryBranch. GPML, Mark Tompsett

6 11

Looking for installdir... and bug 7167
by Mathieu Saby 24 Sep '13

24 Sep '13

Hi I would like to get the name of installation directory for putting in etc/..... a YAML file for configuring facets. I have been looking at the patch introducing SolR, and I found in "Koha / Koha / SearchEngine / Solr / Config.pm" this line : default => C4::Context->config("installdir") . qq{/etc/searchengine/solr/indexes.yaml}, That's exacty what I want... Except there is no "installdir" in my koha-conf.xml. In fact, I think it was introduced in this attachment http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6415 made for Bug 7167 As Bug 7167 has been reverted, installdir does not exist anymore. But it has "Passed QA" again after it was revert. So, could you tell me if this bug will be pushed into master? And if not, what can I do to get the value of the installation directory ? Regards, M. Saby -- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

3 5

deprecating zebra grs1 one day?
by Mathieu Saby 24 Sep '13

24 Sep '13

Hi As you know, making patches for Zebra has always be a nightmare. Now that DOM indexing is possible, it is a double nightmare, because you need to change 2 mores files (sometimes 4 more files when the bug is related to Marc21 and Unimarc). Unimarc conf files are not yet DOM compliant, but I have made some bugs which were signed off recently, and I hope they will soon pass QA. So, when it is done, so you think we could some day (for 3.14 ? 3.16?) get rid of Zebra GRS1 ? It could make simple further improvements. For example, I would like to make a page for configuring zebra indexes from staff interface. I think it can be done by parsing bib1, ccl.properties and xml DOM conf files. But I don't want to parse record.abs... Regards, M. Saby -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

8 15

: deprecating zebra grs1 / query parser
by David Cook 24 Sep '13

24 Sep '13

+1 for deprecation of GRS1 +1 for query parser by default David Cook Systems Librarian (BA,FRLS,MLIS) Prosentient Systems P/L ABN 31 078 409 168 72/330 Wattle St, Ultimo NSW 2007 tel: 02 92120899 fax: 02 92120885 dcook(a)prosentient.com.au -----Original Message----- Message: 5 Date: Tue, 24 Sep 2013 14:50:39 +1200 From: Chris Cormack <chrisc(a)catalyst.net.nz> To: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] deprecating zebra grs1 one day? Message-ID: <3358a65f-8078-4b4b-8804-9b9e35669c61(a)email.android.com> Content-Type: text/plain; charset=UTF-8 Jared Camins-Esakov <jcamins(a)cpbibliography.com> wrote: >+1 for deprecation +1 from me too Chris > >On Mon, Sep 23, 2013 at 8:42 PM, Galen Charlton <gmc(a)esilibrary.com> >wrote: > >> Hi, >> >> On Sun, Sep 22, 2013 at 10:55 AM, Mathieu Saby < >> mathieu.saby(a)univ-rennes2.fr> wrote: >> >>> So, when it is done, so you think we could some day (for 3.14 ? >3.16?) >>> get rid of Zebra GRS1 ? It could make simple further improvements. >>> For example, I would like to make a page for configuring zebra >indexes >>> from staff interface. I think it can be done by parsing bib1, >>> ccl.properties and xml DOM conf files. But I don't want to parse >>> record.abs... >>> >> >> I don't think there's anything GRS-1 does that DOM cannot do. It's >too >> late by far to consider removing GRS-1 support for 3.14, but it is >not too >> late to make a deprecation announcement with the release of 3.14 and >plan >> on having it be removed in the release after 3.14 (or the release >after >> that). >> >> Consequently, I hereby open a straw poll for folks to indicate >whether or >> not they think that announcing a deprecation is sensible. >> >> Regards, >> >> Galen >> -- >> Galen Charlton >> Manager of Implementation >> Equinox Software, Inc. / The Open Source Experts >> email: gmc(a)esilibrary.com >> direct: +1 770-709-5581 >> cell: +1 404-984-4366 >> skype: gmcharlt >> web: http://www.esilibrary.com/ >> Supporting Koha and Evergreen: http://koha-community.org & >> http://evergreen-ils.org >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >>

1 0

3.14 / vm
by Samuel Desseaux 24 Sep '13

24 Sep '13

Hi, I've a question : As member of the team for the next release, i 've been elected as vm manager (and for the documentation).As it's a new role, I begin to work on it but i 'd like to know where this vm could be hosted and how to plan the release of the vm. I've vm for 3.12 but in french for the moment and could prepare vm for old releases. Best regards samuel

2 2

Queryparser : still experimental?
by Mathieu Saby 24 Sep '13

24 Sep '13

Hi I've never try to activate Queryparser, and I did not follow at all its implementation in Koha (shame!>:o ) So, could someone remind me if it is still "experimental"? Is there some case where activating it could be harmful? Is it planned to make its use mandatory one day and to suppress the syspref dedicated to it? Regards, M. Saby -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

2 1

Voting for the Kohacon 2014 location
by Mirko 23 Sep '13

23 Sep '13

Dear Koha community, you can now vote for the location of the Kohacon 2014 conference. The survey requires your email address, and your IP address is kept until we have the final results. Please be nice and only vote once. Your option are Córdoba (Argentina) and Ibadan (Nigeria). A little information about the locations in question can be found here http://wiki.koha-community.org/wiki/KohaCon2014_Proposals You can vote at http://abunchofthings.net/limesurvey/index.php/952665/lang-en You can vote from now on until October 6, 23:59:59 UTC. -- Mirko

1 0