ng? Could this warning simply be ignored? Should the
"all any" line in the record.abs be removed for authorities or should the 1016
line be added to the record.abs for authorities?
Any comments are welcome.
Regards,
Marcel de Rooy
___
Koha
signed, we could at least have gone up to
255 books per shelf.
Any comments are welcome!
Thanks.
Marcel de Rooy
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
255 should normally be fine.
-Oorspronkelijk bericht-
Van: Galen Charlton [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 16 oktober 2008 15:20
Aan: Marcel de Rooy
CC: [EMAIL PROTECTED]; koha-devel@lists.koha.org
Onderwerp: Re: [Koha-devel] Shelving control number
Hi,
On Thu, Oct 16
]
Authority record 1 ESTABL. TERM 150 Test 450 Oldtezt
Optionally: Auth rec 2TRACED REF 150 Oldtezt 260 Test
When searching the OPAC, I would like my user to find book 1 when typing
Oldtezt in the search bar.
Your response is most welcome.
Thanks,
Marcel de Rooy
uot;all any" line in the record.abs be removed for
authorities or should the 1016 line be added to the record.abs for authorities?
Is there any difference between any and Any ;) ?
Marcel de Rooy
-Oorspronkelijk bericht-
Van: koha-devel-boun...@lists.koha.org
[mailto:koha-dev
=
?
Thanks for responding!
Marcel de Rooy
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
-boun...@lists.koha.org]
namens Marcel de Rooy [m.de.r...@rijksmuseum.nl]
Verzonden: donderdag 22 oktober 2009 15:34
Aan: koha-devel@lists.koha.org
Onderwerp: [Koha-devel] Searching with name=
Hi all,
When I search with name= in OPAC or staff, I have exactly the same results as
with any=. I checked
26 oktober 2009 11:11
Aan: koha-devel@lists.koha.org
Onderwerp: Re: [Koha-devel] FW: Searching with name=
Marcel de Rooy wrote:
> So far no reply on the general list..
> Is anyone of you willing to compare search results with
> name=searchterm and any=searchterm on your opac? Is this an
Hi,
Recently somebody on this list wrote to add the line "encoding utf-8 " to
/etc/koha/zebradb/lang_defs/en/sort-string-utf.chr.
I just discovered that from that time on I have multiple errors in the log of
rebuild_zebra like:
[fatal] Bad value-set specification
[warn] Failed to read character
Does anyone of you know this bug ?
Van: koha-boun...@lists.katipo.co.nz [koha-boun...@lists.katipo.co.nz] namens
Marcel de Rooy [m.de.r...@rijksmuseum.nl]
Verzonden: maandag 4 januari 2010 13:03
Aan: 'k...@lists.katipo.co.nz'
Onderwerp: [Koha] Editin
Found it! Forget my message. For some reason the tab field in that particular
framework was no longer value 10.
Van: koha-devel-boun...@lists.koha.org [koha-devel-boun...@lists.koha.org]
namens Marcel de Rooy [m.de.r...@rijksmuseum.nl]
Verzonden: dinsdag 5
Hi all,
I did already mail to the zebra list, but does anyone of you have experience
with zebrasrv segfaulting? Like this: Jan 14 10:11:43 localhost kernel:
zebrasrv[32625]: segfault at 88 ip 003d45a0e37c sp 7fffa7cca610 error 4
in libyaz_server.so.3.0.0[3d45a0+11000]
Versions are
Hi all,
I stumbled across some garbled characters in Koha 3.0.3 Guided reports,
although we use UTF-8 'everywhere'.
Looking further, I noticed the line binmode STDOUT, ':utf8'; in
guided_reports.pl (line 341).
Since the script is not working here on a binary file, this does not seem
appropriate
Hi all,
Working with Koha 3.00.06.09 from git (origin/3.0.x), I think that there is a
syntax error on the html template opac-detail.tmpl.
For this template, matching the if´s and endif´s etc. by hand is quite
laborious.
Can anyone of you point me to a better way of checking such templates?
Thank
Great! I found it in 30x.
-Oorspronkelijk bericht-
Van: Galen Charlton [mailto:gmcha...@gmail.com]
Verzonden: woensdag 12 mei 2010 14:04
Aan: Marcel de Rooy
CC: koha-devel@lists.koha.org
Onderwerp: Re: [Koha-devel] HTML::Template
Hi,
2010/5/12 Marcel de Rooy :
> Working with K
Hi all,
Just a ´dumb´question from someone who just started submitting a few minor
patches:
Galen wrote:
This patch is similar to commit 731b82f7641565c, which is present in
HEAD and, if this is a significant enough issue in 3.0.x, should be
cherry-picked to that branch. I've marked bug 4159
16 matches
Mail list logo
