Re: [Koha-devel] Authorities searching (3 things)

2008-04-18 Thread Paul POULAIN
Galen Charlton a écrit :
> Hi,
> 
> On Wed, Apr 16, 2008 at 11:36 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
>>  3 questions/problems/suggestions :
> 
> I'm still working on a response to these, but to add a fourth one,
> with recent work Koha 3 is now in a situation where authority records
> are now *required* -- this was not true prior to the second beta.  In
> order for a cataloger to be able to add or edit a heading in the bib
> record without being *required* to open a popup window for each
> heading, BiblioAddsAuthorities must be turned on.  However, I don't
> think turning BiblioAddsAuthorities on is suitable for every library.
> as automatically creating authority records is a good way to enshrine
> typos.
> 
> I propose adding another syspref (perhaps called
> RequireAuthoritySearch) that controls whether a heading field is
> readonly or not in the bib editor.  This would be orthogonal to the
> BibilioAddsAuthorities syspref.

I think you don't need this syspref :
3 use case :
- library has a strong thesaurus, that should not be modified 
automatically : BiblioAddsAuthorities = OFF, and it's forbidden to enter 
something without using the ...

- library has a thesaurus, but not a strong one : BiblioAddsAuthorities 
   = ON and adding an authority in the biblio add it in the authorities

- library don't care : remove authorities link the the cataloguing 
frameworks ;-) [1]

with your 2 sysprefs, you could reach a situation where you have a 
thesaurus, and you have biblios that have authorities values that are 
not in the authorities. In UNIMARC, it's strictly forbidden ;-)

HTH


[1] that's why, in french UNIMARC installer, you have the choice between 
2 UNIMARC : "lecture pub" (public library), that don't have a thesaurus, 
and "specialised library", that has a thesaurus.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : 04 91 31 45 19
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel


Re: [Koha-devel] Vote NOW for the Koha Community Website Theme

2008-04-18 Thread Paul POULAIN
Darci Hanning a écrit :
> Dear Koha Community,
> 
> You may now vote for the Koha Community Website Theme here:
> http://www.surveymonkey.com/s.aspx?sm=cXmKffvDeO7c48PVcFB4BA_3d_3d 

OK,
After investigating much more on the survey & on the demo sites, my 
conclusion :
- the new features that plone will add are really nice : documentation, 
download, forums... So I vote "yes" to move to plone, i'm convinced 
(nobody asked my opinion, but I give it anyway :-D )
- i've given "1" ratings to theme 2 and 3 and poor ratings to theme 1.

#2 and #3 are really too bright/white for me. I don't like the colors, I 
don't like anything.
I don't like #1 either, but if I really have to choose between only 
those 3, I could live #1.

But definetly, I prefer the actual design of www.koha.org, and hope we 
will decide to switch to plone with a design like the one we have atm.

(maybe change a little #1 to be closer to the actual one, because, yes, 
#1 is the closest ?)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : 04 91 31 45 19
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel


Re: [Koha-devel] Vote NOW for the Koha Community Website Theme

2008-04-18 Thread Owen Leonard
Paul is right, I agree with those who say the current Koha.org design
is preferable to the options we've been shown.

> I'm sorry if my suggestion is out of place - but wouldn't it be best
>  if we just got a site up and running that was multi-lingual and then
>  worry about the design issues?

I think Nicole makes an excellent point. I also think that we need to
consider the option of saying, "Sorry, there were no winners this
time."

  -- Owen
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel


[Koha-devel] Re: interest in improving automated tests with a testing database

2008-04-18 Thread Andrew Moore
Hi again Koha developers -

Galen and I just submitted a few patches that implement this new
testing method. I'm interested in any feedback you have before they're
committed.

http://lists.koha.org/pipermail/koha-patches/2008-April/000172.html
http://lists.koha.org/pipermail/koha-patches/2008-April/000171.html
http://lists.koha.org/pipermail/koha-patches/2008-April/000173.html
http://lists.koha.org/pipermail/koha-patches/2008-April/000174.html
http://lists.koha.org/pipermail/koha-patches/2008-April/000175.html

These create a new t/Makefile which runs a t/database_dependent.pl
test script which creates a test database and runs some automated
tests against it. Those tests are in the new t/lib directory and use
Test::Class to organize and run them.

The way that you use this is to re-run the top level 'perl
Makefile.PL' which will prompt you for some information about a test
database that can be built. Then, you can 'cd t' and run 'make test'
in there. This will make sure that your new test database is created
and used for the test suite. I expect that eventually this process
will be made easier, but this is a first stab at a solution, and I'm
trying to avoid interfering with normal installation as much as
possible.

I'm interested in hearing suggestions about how the process of setting
up the database and running the zebra stuff works. I'm also interested
in hearing about any of these tests that fail. I may take the
opportunity to fix some of these before the code is committed, or fix
them later.

Thanks for your help.
-Andy



On Thu, Mar 27, 2008 at 1:43 PM, Andrew Moore <[EMAIL PROTECTED]> wrote:
> Hi Koha developers -
>
>  I have caught some of you on IRC and such, but for the rest of you,
>  I'm a new developer at LibLime working on Koha.
>
>  I'm interested in improving the automated test suite a little bit, and
>  I'm hoping to get some feedback from any interested developers and
>  users. There are some database specific tests in the t/db_dependent
>  directory, but I think they can be improved quite a bit. I'll lay out
>  what I'm picturing, and please let me know if you picture a different
>  plan, or have any ways to improve this one.
>
>  I'd like to have a 'make' target similar to 'make test' that would
>  build a nearly empty, skeleton database that we could run some
>  automated tests against. Since this would not be the same database
>  that live data is held in, we wouldn't have to worry about deleting or
>  overwriting any useful data. The testing could insert example data and
>  data known to trigger past bugs to ensure that they don't recur. I
>  don't imagine making this a standard part of 'make test', at least at
>  first, since I don't imagine that all end users want to have a second
>  database built just to test against. I think it could be immensely
>  useful for us developers, though, right away.
>
>  One useful way I've seen this done in the past is trough the use of
>  the Test::Class perl module. It's similar to the xUnit framework (or
>  jUnit or nUnit) in that it lets you run a bit of code before and after
>  each test to set up the environment (the test fixture). That way, you
>  can ensure that the database looks clean between when different pieces
>  of the test suite runs so that one test script doesn't interfere with
>  another. It also lets your test scripts inherit from each other so
>  that similar test scripts can share the same code to set up their
>  fixtures.
>
>  I have a small working prototype of this, but before I get much
>  further, I want to ask if you have any suggestions or advice for this.
>  Please let me know if this sounds like something that would be useful
>  to you, and if there's anything I need to make sure I consider.
>
>  Thanks,
>  -Andy
>


___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/koha-devel
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel


[Koha-devel] .gitignore

2008-04-18 Thread Ryan Higgins
I'd like to suggest that the .gitignore recently pushed to the public repo
be removed,
and that Koha not enforce any conventions via .gitignore .

-- 
Ryan Higgins

LibLime * Open-Source Solutions for Libraries
Featuring KohaZOOM ILS
888-564-2457 x704
___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/koha-devel
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel


Re: [Koha-devel] Vote NOW for the Koha Community Website Theme

2008-04-18 Thread Rick Welykochy
Owen Leonard wrote:

> I think Nicole makes an excellent point. I also think that we need to
> consider the option of saying, "Sorry, there were no winners this
> time."

Does that mean we are all lusers?



-rickw


-- 

Rick Welykochy || Praxis Services || Internet Driving Instructor

We like to think of ourselves as the Microsoft of the energy world.
  -- Kenneth Lay, former CEO of Enron
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel