[EMAIL PROTECTED] a écrit :
> Firstly, apologies for the cross list posting. I didn't realise that all
> the other lists had been copied in. Seems that this is a bigger deal than
> I originally thought.
>
>
>> The best way to do that would be to have some kind of official
>> language dictionary
My solution to that was to use a cookie, then have anything that could
accept a specified due date check for the cookie. Like so in
renewscript.pl :
my $date;
if ($input->cookie('stickyduedate')) {
my ($year, $month, $day) = split /-/,
$input->cookie('stickyduedate');
$date = $year ."-".
Hi All
Can someone please help with above.
I need to use the sticky due date also for renewal of allready issued items.
The renewbooks function in circ2.pm allows for a "duedate" parameter.
I need to know how to force the renew functionality to use the sticky due date.
It sounds straight forwar
On Tue, Apr 8, 2008 at 12:56 PM, Owen Leonard <[EMAIL PROTECTED]> wrote:
> > The first one is a bit missleading. It refers to the max number of
> > items to display per bib on the results page.
>
> Ah, that makes more sense now. Does hitting the limit cause the
> results page to display only
> The first one is a bit missleading. It refers to the max number of
> items to display per bib on the results page.
Ah, that makes more sense now. Does hitting the limit cause the
results page to display only the first X items per result, or is there
an indication that there are more to see?
On Tue, Apr 8, 2008 at 12:08 PM, Owen Leonard <[EMAIL PROTECTED]> wrote:
> I see three different system prefs related to the number of search
> results displayed on a page:
>
> maxItemsInSearchResults: Specify the maximum number of items to
> display for each result on a page of results
> numSe
I see three different system prefs related to the number of search
results displayed on a page:
maxItemsInSearchResults: Specify the maximum number of items to
display for each result on a page of results
numSearchResults: Specify the maximum number of results to display on
a page of results
OPACn
Hi,
On Tue, Apr 8, 2008 at 9:43 AM, Henri-Damien LAURENT
<[EMAIL PROTECTED]> wrote:
> Very good.
> just a question.
> How hard would it be to add permisions to a simple link/action ?
I don't think this will be hard to do - just time consuming, given the
number of functions that Koha users may
Galen Charlton a écrit :
> Hi,
>
> For a customer project I've been working on an approach to make Koha's
> staff user permissions more granular. The initial scope of the
> development is restricting access to individual items on the tools
> page, but the mechanism can readily be expanded to cover
Hi,
For a customer project I've been working on an approach to make Koha's
staff user permissions more granular. The initial scope of the
development is restricting access to individual items on the tools
page, but the mechanism can readily be expanded to cover all of Koha's
modules.
My idea is
Nicole Engard a écrit :
> This is a great idea! I actually have a list going that I can share of
> terms that are different throughout. We should certainly have
> different English dictionaries to be the most user friendly.
>
We also face the same demand here in France.
Academic libraries donot
This is a great idea! I actually have a list going that I can share of
terms that are different throughout. We should certainly have
different English dictionaries to be the most user friendly.
--
Nicole C. Engard
Open Source Evangelist, LibLime
(888) Koha ILS (564-2457) ext. 714
[EMAIL PROTECTE
12 matches
Mail list logo
