Hello
As a librairian, I think the "any" index defined in record.abs often
return too much results, and inappropriate.
It is *partly *caused by "any" index indexing all fields, including all
notes fields (5XX in marc21, 3XX in unimarc), and of a lot of fields
that could be usefull for staff but
Hi koha-devel,
The 3.10 and 3.12 QA teams ( Mason, Jonathan, Marcel & me, with the
freshly elected Travis, Katrin -and Jared as RM-) have had a discussion
about QA process and would like to propose the 2 following things:
* Create a QA specific mailing list (q...@lists.koha-community.org ?)
This
On 24 October 2012 22:47, Paul Poulain wrote:
> Hi koha-devel,
>
> The 3.10 and 3.12 QA teams ( Mason, Jonathan, Marcel & me, with the
> freshly elected Travis, Katrin -and Jared as RM-) have had a discussion
> about QA process and would like to propose the 2 following things:
>
> * Create a QA s
Hello
I think I have found a little bug, but I am not sure of it.
in C4/Search.pm (sub _build_weighted_query), I found this :
826 $weighted_query .= " $index,ext,r1=\"$operand\"";# exact
index
827 #$weighted_query .= " or (title-sort-az=0 or
$index,startswithnt,st-word,r3
Le 22/10/2012 14:19, Paul Poulain a écrit :
> Hi koha-devel,
Important dddition to the previous mail: the sed is not enough... it
does not change usmarc.mar, that is required for Authorities in grs1
The authority search badly fails until you've updated usmarc.mar to have:
name unimarc
reference un
On 24 October 2012 23:16, Paul Poulain wrote:
> Le 22/10/2012 14:19, Paul Poulain a écrit :
>> Hi koha-devel,
>
> Important dddition to the previous mail: the sed is not enough... it
> does not change usmarc.mar, that is required for Authorities in grs1
> The authority search badly fails until you
On 2012-10-24, at 6:47 PM, Harry Lachanas wrote:
> Hi List,
> I am facing a prob with a setup design that has safety and min-down time
> fail-over etc as a prerequisite.
> This has led me to consider a MySql Cluster setup.
> I've tried to import the database into it and found out that it wasn't
On 2012-10-24, at 10:52 PM, Chris Cormack wrote:
> On 24 October 2012 22:47, Paul Poulain wrote:
>> Hi koha-devel,
>>
>> The 3.10 and 3.12 QA teams ( Mason, Jonathan, Marcel & me, with the
>> freshly elected Travis, Katrin -and Jared as RM-) have had a discussion
>> about QA process and would l
Mason James schrieb
> if people are OK with having the QA-team discuss their stuff on
> the koha-devel list, then i am happy (we could prefix the QA
> email's subject with 'QA: ', so people can ignore them easily, if
> they want too)
>
>
> are people OK with this?
I am. And I think anyone on the
On 24 October 2012 12:49, Mason James wrote:
> if people are OK with having the QA-team discuss their stuff on the
> koha-devel list, then i am happy
> (we could prefix the QA email's subject with 'QA: ', so people can ignore
> them easily, if they want too)
>
>
> are people OK with this?
+1
M
+1 for QA: :)
Van: koha-devel-boun...@lists.koha-community.org
[koha-devel-boun...@lists.koha-community.org] namens Magnus Enger
[mag...@enger.priv.no]
Verzonden: woensdag 24 oktober 2012 13:08
To: Koha Devel
Onderwerp: Re: [Koha-devel] Some thoughts from
>> (we could prefix the QA email's subject with 'QA: ', so people can ignore
>> them easily, if they want too)
>>
>> are people OK with this?
+1
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
___
Koha-devel mailing lis
Mathieu,
> Hello
> I think I have found a little bug, but I am not sure of it.
You have. Quite a big bug, actually.
> in C4/Search.pm (sub _build_weighted_query), I found this :
>
> 826 $weighted_query .= " $index,ext,r1=\"$operand\"";# exact
index
> 827 #$weighted_query .=
Mathieu,
> As a librairian, I think the "any" index defined in record.abs often
return too much results, and inappropriate.
> It is partly caused by "any" index indexing all fields, including all
notes fields (5XX in marc21, 3XX in unimarc), and of a lot of fields that
could be usefull for staff b
> > if people are OK with having the QA-team discuss their stuff on the
koha-devel list, then i am happy
> > (we could prefix the QA email's subject with 'QA: ', so people can
ignore them easily, if they want too)
> >
+1
___
Koha-devel mailing list
Koha-d
On Wed, Oct 24, 2012 at 10:06 AM, Jared Camins-Esakov
wrote:
>
>> > if people are OK with having the QA-team discuss their stuff on the
>> > koha-devel list, then i am happy
>> > (we could prefix the QA email's subject with 'QA: ', so people can
>> > ignore them easily, if they want too)
>> >
> +1
Jared Camins-Esakov a écrit :
Mathieu,
> As a librairian, I think the "any" index defined in record.abs often
return too much results, and inappropriate.
> It is partly caused by "any" index indexing all fields, including
all notes fields (5XX in marc21, 3XX in unimarc), and of a lot of
fiel
Mathieu,
When I wrote "editable by all libraries..", I meant
> editable-in-the-hard-way (record.abs etc). It would be better than
> nothing...
Ah. Yes. This is an excellent idea. :)
>
> As an initial step, you might consider submitting a patch that adds the
>> hardcoded index and allows libra
Greetings,
if people are OK with having the QA-team discuss their stuff
on the koha-devel list, then i am happy
(we could prefix the QA email's subject with 'QA: ',
so people can ignore them easily, if they want too)
are people OK with this?
Yes, +1 to QA tagged subject lines and discussing o
Le 24/10/2012 11:52, Chris Cormack a écrit :
> And if they are patch specific then on the bug itself makes more sense.
> I'd definitely like to see any qa discussions public, but I don't see
> the need for a new list .. am I missing something?
Everybody says +1 to your counter-proposal, but we al
Paul,
Everybody says +1 to your counter-proposal, but we already have a
> koha-translate mailing list, dedicated to translation questions. And a
> koha-zebra one that is almost unused, but exist.
>
I am of the opinion we should close the koha-zebra list, at least. It just
means more mailing lists
Hi,
On Wed, Oct 24, 2012 at 10:34 AM, Paul Poulain
wrote:
> Le 24/10/2012 11:52, Chris Cormack a écrit :
> Everybody says +1 to your counter-proposal, but we already have a
> koha-translate mailing list, dedicated to translation questions. And a
> koha-zebra one that is almost unused, but exist.
Hi all,
I think so far we have a lot of votes for keeping the discussion on the Koha
developer mailing list so it looks to me like this is what we should do. Also a
+1 from me. I think Mirko made a good point that it is interesting for all
developers to know how the QA team works.
On another n
In my opinion, one of the problems of creating an "opac-any" index in
zebra is that many of the fields and subfileds in MARC are not meant to
be shown to the public, and indexing them confuses things. If they don't
appear in the opac, yet do appear in the search results, the patron is
left wo
Hi all,
I agree with Katrin in both points.
Marc V.
Am 24.10.2012 16:53, schrieb Fischer, Katrin:
Hi all,
I think so far we have a lot of votes for keeping the discussion on the
Koha developer mailing list so it looks to me like this is what we should
do. Also a +1 from me. I think Mirko ma
Linda a écrit :
In my opinion, one of the problems of creating an "opac-any" index in
zebra is that many of the fields and subfileds in MARC are not meant
to be shown to the public, and indexing them confuses things. If they
don't appear in the opac, yet do appear in the search results, the
Mathieu,
In my opinion, one of the problems of creating an "opac-any" index in
> zebra is that many of the fields and subfileds in MARC are not meant to be
> shown to the public, and indexing them confuses things. If they don't
> appear in the opac, yet do appear in the search results, the patro
I agree with Marc V. agreeing with Katrin. :)
Ian
On Oct 24, 2012 11:11 AM, "Marc Véron" wrote:
> Hi all,
>
> I agree with Katrin in both points.
>
> Marc V.
>
>
>
> Am 24.10.2012 16:53, schrieb Fischer, Katrin:
>
>> Hi all,
>>
>> I think so far we have a lot of votes for keeping the discussion
If you want, you can make comments on this new bug
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8962
"Create a new index for OPAC simple search, more specific than "any"
Todo :
- check bib1.att & ccl.properties to see if some index not used in Koha today
could be used. If nothing us
Hi
I'm using koha 3.8.5
the bug 7445 is not solved in this version because I have the same error
message
خطأ:Language 'ar' does not exis
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7445
I see that this bug was fixed in the RELEASE NOTES FOR KOHA 3.6.5
http://koha-community.org/koh
On 25 October 2012 10:12, Karam Qubsi wrote:
> Hi
> I'm using koha 3.8.5
>
> the bug 7445 is not solved in this version because I have the same error
> message
>
> خطأ:
>
> Language 'ar' does not exis
>
It is in 3.8.6 .. and was in 3.8.0, 3.8.1 etc
So the fix is in, if it isn't working then it ne
Salvete!
>I agree with Marc V. agreeing with Katrin. :)
Oh yeah, well I triple dog agree with you.
I think a separate list might slightly hinder a would be bug wrangler.
nofences++
Cheers,
Brooke
___
Koha-devel mailing list
Koha-devel@l
Chris Cormack schrieb
> On 25 October 2012 10:12, Karam Qubsi wrote:
>> Hi
>> I'm using koha 3.8.5
>>
>> the bug 7445 is not solved in this version because I have the same error
>> message
>>
>> خطأ:
>>
>> Language 'ar' does not exis
>>
> It is in 3.8.6 .. and was in 3.8.0, 3.8.1 etc
>
> So the f
>
> Am 24.10.2012 16:53, schrieb Fischer, Katrin:
> Hi all,
>
> I think so far we have a lot of votes for keeping the discussion on the
> Koha developer mailing list so it looks to me like this is what we should
> do. Also a +1 from me. I think Mirko made a good point that it is
> interesting for
Hi there,
I am currently working on improving accessibility of koha opac site with
our accessibility expert.
One of the things we noticed is that the advanced search option is not
only confusing for blind
users but also even for normal users.
I have noticed the following issues with it:
1) B
On 2012-10-25, at 1:40 AM, Jonathan Druart wrote:
> Hi Mason,
>
> I did not rebase my qa-tools repo and I found a bug in the check of
> perlcritic.
> So I fixed it and ... I was not able to push, I was not up-to-date :)
>
> In fact you already tried to fix it in the commit "fixed perlcritic te
I'm agreeing with Brooke, who agrees with Marc V., who agrees with
Katrin...
*D Ruth Bavousett*
Lead Migration Specialist
ByWater Solutions
Support and Consulting for Open Source Software
Headquarters: Santa Barbara, CA
Office: Lawrence, KS
Phone/Fax (888)900-8944
http://bywatersolutions.com
r...@
>
> thanks for this, ill do some testing then push your changes up to the kc.rg
> github repo
> https://github.com/Koha-Community/koha-qa-tools
>
Can we get Galen to set up a repo at the official Koha community git
repo (git.koha-community.org) and have these tools there too?
github is nice for a
So I've finally convinced packages to build from master again. At the
moment, the only patch required that's not already in master is the one
on bug 8636, and that's just because I had to make a change to it today.
You can find these in the squeeze-dev repo.
Additionally, and of particular intere
Le 25/10/2012 04:58, Chris Cormack a écrit :
>>
>> thanks for this, ill do some testing then push your changes up to the kc.rg
>> github repo
>> https://github.com/Koha-Community/koha-qa-tools
>>
> Can we get Galen to set up a repo at the official Koha community git
> repo (git.koha-community.org)
40 matches
Mail list logo
