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

jquery upgraded on master branch
by Paul Poulain 11 May '12

11 May '12

Hello koha-devel, I just pushed a patch to upgrade jquery to version 1.7.2 (from 1.3.2) It has been tested, but some side effect are always possible. So if you find strange javascript behaviour, go to bug 5184, or think of this upgrade ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Re: [Koha-devel] missing pdf files for Koha 3.6 and 3.8 manuals
by Arslan Farooq 10 May '12

10 May '12

Hi Nicole Can we have the option to download the whole manual (HTML files) as an archive? That will allow us to download the whole thing and memorize it offline (say, when electricity is out). You may set up a script that periodically deletes the zip and creates a new one (so that the zip is always latest). -- arslan > ---------- Forwarded message ---------- > From: Nicole Engard <nengard(a)gmail.com> > To: Mason James <mtj(a)kohaaloha.com> > Cc: koha-devel(a)lists.koha-community.org > Date: Thu, 10 May 2012 07:59:47 -0400 > Subject: Re: [Koha-devel] missing pdf files for Koha 3.6 and 3.8 manuals > There are no PDFs of the 3.6 or 3.8 manual. There were issues with the > script that generated PDFs (as far as I know) and so they aren't > running anymore. > > Nicole

4 4

Re: [Koha-devel] Multi-branch SCO [Was: Re: Branch Specific System Preferences]
by Chris Nighswonger 10 May '12

10 May '12

On Thu, May 10, 2012 at 3:54 PM, David Schuster <dschust1(a)gmail.com> wrote: > OK here is how we have it setup, and I just verified it still works that > way with 3.06.04. > > AutoSelfCheckAllowd - Don't Allow > > The librarian logs into the sco using a "user" setup as lmsxxx/password - > xxx is the location > > All transactions there are associated with the user's location. > > Granted that forces you to setup 67 users and someone has to open that up, > but it has been working well for us for 4 years. > > Does that make sense? I don't want to auto login as you note somehow the > system needs to know where you are from to track stats and route books > correctly. > > This is too easy to be true.... ;-) Let me see if I understand correctly: At Branch A: 1. Log into the staff client using Branch A's SCO account. 2. Navigate to the sco interface. At Branch B: 1. Log into the staff client using Branch B's SCO account. 2. Navigate to the sco interface. Please tell me it works this way and save me lots of hours of coding... ;-) Kind Regards, Chris

2 2

Multi-branch SCO [Was: Re: Branch Specific System Preferences]
by Chris Nighswonger 10 May '12

10 May '12

Hi David, On Thu, May 10, 2012 at 12:38 PM, David Schuster <dschust1(a)gmail.com> wrote: > I'm a little confused by this comment. We do self checkout - but have a > generic user for each branch that they use to login the SCO module. It > then checks out books as if they are at that branch. What part of that > doesn't work? I'm a little confused... > > I'm not sure what version you're using, but in the current master the following sysprefs define the user for the SCO module: AutoSelfCheckAllowed AutoSelfCheckID AutoSelfCheckPass Unfortunately there is only room there for a single user tied to a single branch. This results (for us at least) in all books checked out in the SCO module appearing under the branch of the user listed in these sysprefs. If there is workaround, I'd love to know it while we are in the process of making the SCO module truly multi-branch. Kind Regards, Chris

1 0

Koha 3.6 string freeze
by Jared Camins-Esakov 10 May '12

10 May '12

Greetings, international Koha community! As you may know, I was elected as Release Maintainer for the 3.6.x branch for the Koha 3.10 release cycle. Well, the time has come to do some releasing! Over the weekend I cherry-picked all candidates for inclusion in the 3.6.x into a new branch: 3.6.x-maint/testing. I encourage you to test that branch out, and try to shake out any bugs that there may be. Tomorrow I will be cherry-picking commits into the existing 3.6.x branch for the Koha 3.6.5 release. With the exception of high priority patches, only those commits that were incorporated into Master on or before April 12 will be considered for inclusion. The 3.6.x branch will then enter string freeze on May 10 at 16:00 UTC to give the translation teams time to work their magic. Koha 3.6.5 will be released on May 24. Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 2

Guided report in Koha 3.8.0
by Partha Mukhopadhyay 10 May '12

10 May '12

1 0

marc import/need help
by Samuel Desseaux 10 May '12

10 May '12

Hello I'm trying to convert data in marc format ( a big challenge because our old ILS doesn't respect unimarc): in marc edit, when i have this error "undefined error reported, error number -99" what does it means ? I join to this mail an excel file of my data. Best regards samuel

2 1

error while creating notices
by Samuel desseaux 10 May '12

10 May '12

Hi, Something strange: i creat my notice, my examplar and when i want to record, i've the following error Software error: Can't call method "subfield" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2919 So, i try to understand *problem of encoding in the title tag ? Maybe but, just before, i've added a record without any problems and when i look parameters for encoding characters (mysql and apache), it's ok. *problem of version ? I use debian package (as we are in a period of tests) and my version is 3.07 I join the logs of koha, if it can help Best regards samuel

7 13

MARC::Record, record length and leader
by Julian Maurice 09 May '12

09 May '12

Hello, I know this is an old discussion but I just realized that saving a biblio record longer than 99999 bytes result in a malformed leader. Length of the record takes more than 5 characters and therefore remaining characters in the leader are shifted to the right. This cause the leader to have more than 24 characters. I'm not sure of what have to be done. Should MARC::Record die when encountering such a record? or should it force length to be 99999? or should the record be truncated to fit the spec? Has someone ever faced this problem? How did you handle it? -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

12 18

Re: [Koha-devel] error while creating biblio(part 2)
by Paul 09 May '12

09 May '12

At 04:51 PM 5/9/2012 +0200, Paul Poulain wrote: >Le 09/05/2012 16:47, Paul a écrit : > > At 02:38 PM 5/9/2012 +0200, Zeno Tajoli wrote: > >> Il 09/05/2012 14:24, Samuel desseaux ha scritto: > >> > I join to this e-mail 2 examples of biblio which give this error > >> > >> in your biblio n.23 try to not use accented chars in tag 200 subfield g > > > > Just for my own edification, what is "tag 200" in Marc21? (from the > > attached biblios, the record appears to be based on > > www.loc.gov/MARC21/slim which does not contain a 200.) >It doesn't exist. >But Samuel is french, and, as 99% of french libraries don't use MARC21, >but UNIMARC. >And in UNIMARC, 200 contains very not[*] important informations : the >title and the author ! Yup agreed (we have worked extensively with Isabelle Nadolny on the UNIMARC at z3950.bnf.fr) but I was querying whether the xml record header referencing specifically MARC21/slim could be a source of problems. Amitiés [l'autre] Paul _______________________________________________ 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/ --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://UltraMarine.ca>, <http://AandC.org> and <http://MarDoc.ca>

1 0