Le 19/02/2010 21:52, Owen Leonard a écrit :
>> OK, I sent a patch for this, hopefully it was intact, but I am setup to
>> enhance
>> if more is needed.
>>
> It seems to be working great--very seamless. Did you create the sounds
> or did you find them somewhere?
>
Seems some of you are stil
Le 22/02/2010 06:43, Bob Birchall @ Calyx a écrit :
> Before we lodge on Bugzilla, are there any comments?
>
yes: sound fine to me ;-)
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08
___
Ko
On Mon, Feb 22, 2010 at 11:13 AM, Bob Birchall @ Calyx
wrote:
> We propose adding a syspref 'OpacNotPublic' or similar which when set to
> 'OFF' will cause no change to current behaviour. When set to 'ON' a
> different template will be called by opacmain.pl that will display:
> - a login
+1
On Mon, Feb 22, 2010 at 4:39 AM, Indranil Das Gupta wrote:
> On Mon, Feb 22, 2010 at 11:13 AM, Bob Birchall @ Calyx
> wrote:
>
>
>> We propose adding a syspref 'OpacNotPublic' or similar which when set to
>> 'OFF' will cause no change to current behaviour. When set to 'ON' a
>> different t
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
This is a good idea.
However, I'm not sure that just calling a different template from
opacmain.pl is enough. Unless I'm missing something, people will still
be able to access other pages if they know the URL.
I think that adding the OpacNotPublic is necessary.
Why not using this value to s
Hi,
On Mon, Feb 22, 2010 at 9:11 AM, Eric Bégin wrote:
> Why not using this value to set the 'authnotrequired' in the code,
> instead of having this value hardcoded. That way, every pages would be
> protected.
Agreed - this is more comprehensive.
Regards,
Galen
--
Galen Charlton
gmcha...@gma
Sounds like a good starting place.
More generally, I'd like to see visibility configured on a Patron Type/Item
Type level. That is, items of type X can only be seen by patrons with item
type X viewing permissions, with limits on whether patrons have to be from a
specific library or library group.
Galen,
Thanks; that helps a lot.
Galen and/or Erik,
Since you mentioned that the SIP2 interface would be the logical way to
interact with the circulation system, I took a look at it. It looks
easy enough to configure, using the Koha Manual as a guide:
http://koha.org/documentation/manual/3.
Hi, one of my supervisor just checked the "Browse Shelf" of 3.0.5 today and
asked me about some problemetic issue. When, we go for "Browse Shelf" point,
it shows some weird images there instead of showing actual book cover page.
As for example: I am searching for "Computer Algorithm" book but "Brow
> I'm going to see if any of Aeon's developers are fluent in SIP; in
> case I have to set this up myself, can you recommend a good source of
> documentation for using SIP2 with Koha?
Have you read 3M SIP2 protocol reference document? It's here:
http://solutions.3m.com/wps/portal/3M/en_US/
Frédéric,
I did see that documentation. I was hoping for some more Koha-specific
docs that would assist with field mapping & interfacing.
We'd primarily be using the "11 Checkout" and "09 Checkin" messages, but
I'm uncertain what data to include in some of the message required
fields, such
OK, thanks for the suggestion. We will add that to the spec.
Regards,
Bob
> -Original Message-
> From: Galen Charlton [mailto:gmcha...@gmail.com]
> Sent: Tuesday, 23 February 2010 3:58 AM
> To: Eric Bégin
> Cc: Bob Birchall @ Calyx; koha-devel
> Subject: Re: [Koha-devel] OPAC Secured
>
>
13 matches
Mail list logo
