gmane.education.libraries.koha.devel

Re: Print page - Firefox, etc

Owen Leonard — 2012-05-23T00:32:15

I don't know if this is the best way, but the most basic way is
probably to grab the updated file from the git web interface:

http://git.koha-community.org/gitweb/

I navigated to the 3.6.4 branch and found the most recent version of
the file in question, the staff client print stylesheet:

http://git.koha-community.org/gitweb/?p=koha-small.git;a=blob_plain;f=koha-tmpl/intranet-tmpl/prog/en/css/print.css;hb=441b98cea41ed7d99354195b79d5b4f44b194913

If you replace your file with that one it should be the functional
equivalent of reverting that commit.

  -- Owen

Re: Print page - Firefox, etc

Paul — 2012-05-23T00:15:52

[snip]

Thanks - what's the best way on a *production* server to revert the patch 
and install the better fix?

I must admit to not fully understanding how git (or whatever is most 
appropriate) is setup, and after a look at bug 6291, there appear to be 
quite a few elements touched.  In my sandbox, I once tried (unsuccessfully) 
to have two parallel but different versions of Koha so do not really want 
to try that on the production box.

Best - Paul



---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
<http://UltraMarine.ca>, <http://AandC.org> and <http://MarDoc.ca>

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: KOCT pushed on contrib repo

Chris Cormack — 2012-05-22T21:11:58

Awesome! Thank you

Chris
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

KOCT pushed on contrib repo

Paul Poulain — 2012-05-22T21:07:21

Hello,

I just pushed a few minuts ago a patch with KOCT on the contrib repository
(http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary)

Re: Print page - Firefox, etc

Owen Leonard — 2012-05-22T18:01:32

Probably, in that your description matches exactly the PDF attached to
the bug ;)

However, I can't reproduce the problem in master so this may already
have been fixed. Tested in Firefox 12, Chrome 19, Opera 11, and IE 9
on Windows 7.

Judging from the description and the timeline of Koha 3.6.1 I'm
guessing the bug is caused by my first fix for Bug 6291 which was
subsequently reverted in favor of a better fix.

  -- Owen

Print page - Firefox, etc

Paul — 2012-05-22T15:49:56

Our cataloguers are having a local problem that I was unaware of. This is 
probably Koha bug 7199 which appears to be a tad inactive; I'd be happy to 
assist, but have no knowledge whatsoever of how browsers render 
CSS|templates for printing.

Trying to "print page" after a staff screen listing such as 
<http://koha-admin/cgi-bin/koha/catalogue/search.pl?q=lambert%2C+andrew> 
(the page itself is perfect) gives an oddball output with the "Results" and 
"Location" columns squeezed down to very narrow columns on the right hand 
side of the page. The "check box" column (normally very narrow) expands to 
well over 50% of page width.

This happens (for us at least) in Firefox (v. 12.0), Chrome (build 16.0), 
Safari (5.1) and MSIE (6.0 - we don't have anything more recent in our Win 
machine.)

A quick review of "equivalent" OPAC search pages (rather than staff-admin) 
shows no problems.

Koha 3.06.01.000, on Linux 2.6.38, Perl 5.010001, Apache 2.2.17, mysql Ver 
14.14 Distrib 5.1.54, for debian-linux-gnu

Thanks

Re: Proposed QA Enhancements

Ian Walls — 2012-05-22T15:44:23

For my part, I tend to review patches textual to see if they make sense as
a changeset.  If I cannot tell from reading what this patch does, I'll
either apply and test, or ask for clarification.  Generally, both of those
actions take more effort than reading on Bugzilla, and thus take longer.

I agree that it would be preferable to have the actual QA signoff on the
patch itself when it gets through QA, so that our git signoff stats are
more accurate.  That does add the additional overhead of pulling down and
applying each patch, then amending the commit and firing back up to BZ...
not complicated, but additional steps.  Hence why I haven't been doing it
reliably.

Any QA rules we can put into scripts to automatically check, I'm all for,
as that can relieve some of the more tedious work of checking spacing and
variable name declarations, and let QA look more in-depth about the patch's
implementation.  I know we've got a few such tests... anyone who is willing
to write more goes in my Nice Person book.

My new

Re: Proposed QA Enhancements

Marcel de Rooy — 2012-05-22T15:02:31

Just a quick response on first glance: The numbers in this discussion are imo far from accurate. As for me, I mostly QA without signing off, just to spare time. In most cases I did apply and test (at least some functionality, in other cases much more). I would not recommend doing QA in Bugzilla only, perhaps with the exception of very small things. 
Adding the rule that QA must do an additional signoff too will put more work (better testing etc.) on the QA team, and will result in more delay. If a QA member does not trust a patch, why not ask for a second signoff (older idea..)? 

________________________________________
Van: koha-devel-bounces-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org [koha-devel-bounces< at >lists.koha-community.org] namens Chris Cormack [chrisc-6STWZtX7tXAqAMOr+u8IRA< at >public.gmane.org]
Verzonden: dinsdag 22 mei 2012 10:51
To: Paul Poulain
Cc: koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
Onderwerp: Re: [Koha-devel] Proposed QA Enhancements

* Paul Poulain (paul.poulain-zk

Multi-Lingual SQL & User Defined Parameters

Massoud Alshareef — 2012-05-16T06:03:11

Hello,

I have asked a question about two years ago about when we can have Koha
support of Multi-Lingual SQL files (used for marc21/Auth fields description
in the Staff client) and Multi-Lingual users defined parameters (used for
describing items/ libraries & groups/ locations/ patrons categories/ etc),
and the answer from Koha development then was that it is
under consideration but not in the development pipelines yet, as it will
require some re-structuring in Koha system databases and controls. That
means, Koha will remain a single language in these areas.

With Koha 3.6 release, I noticed the inclusion of "Spanish translation for
SQL files" in the INTERNATIONALIZATION enhancement section. Does this mean
that Spanish Koha, or any non-English Koha, now has both Spanish and
English SQL files, where Koha users can switch between more than one
language when, for instance, editing marc records in the staff client ?

Koha Preferences description used to be in SQL files, which means a single
language prefers, and

Re: Proposed QA Enhancements

Chris Cormack — 2012-05-22T08:51:15

That's what Chris N was asking for, that a sign off is added when the
patch is tested, it must have been applied and tested, so why not sign
off and attach it back on the bug at the same time as changing the bug
status.

I'm not sure we want to get into a who does more for Koha contest, nor
do I think that was the point of this email.

I do think there are too many patches missing getting 2 independent
sign offs, and that is what we need to fix.

Chris

Re: Proposed QA Enhancements

Paul Poulain — 2012-05-22T08:40:22

Le 21/05/2012 19:38, Chris Nighswonger a écrit :
Something I made during the 3.8 release was to add many things to the
coding guidelines. My preference goes to QA rules that are clearly
defined and explained. That will help QAing a lot, and "anyone" with a
good Koha experience, and some time to dedicate should/could do it.

I agree that we *must* have a functional AND a technical review of every
patch, the 2 steps are different.

Most QA is done in bugzilla only: when a patch is QAed, it's not
signed-off & git bz attach most of the time.
(that's also why your numbers below are meaningless : Ian has not made
only 25 QA or joubu 5 ! OTOH, when I, as RM, push a patch, I always add
my signature, that can be as RM or QA)

As I just wrote, I don't do the majority of QA, (even if I agree I do a lot)

As I've said previously, as RM, I dedicate more than half of my time to
this task.
I think that we could have someone dedicated full time to QA and someone
dedicated full time to sign-off. And until we won't... we wil

Re: Koha 3.8.1 released

Chris Nighswonger — 2012-05-21T22:27:32

Huzza!

On Mon, May 21, 2012 at 5:32 PM, Chris Cormack <chris-BI0SDMbrYt0bf4OJjhDl03TaI6DYlTYJ< at >public.gmane.org>wrote:

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Koha 3.8.1 released

Chris Cormack — 2012-05-21T21:32:25

The Koha release team is happy to announce the release of Koha 3.8.1

This is a stable release and contains bugfixes as well as updated translations.

You can download it at

http://download.koha-community.org/

Go forth, download, and enjoy :)


RELEASE NOTES FOR KOHA 3.8.1
21 May 2012
========================================================================

Koha is the first free and open source software library automation package
(ILS). Development is sponsored by libraries of varying types and sizes,
volunteers, and support companies from around the world.
The website for the Koha project is

    http://koha-community.org/

Koha 3.8.1 can be downloaded from:

    http://download.koha-community.org/koha-3.08.01.tar.gz

Installation instructions can be found:

   in the INSTALL files that come in the tarball

Koha 3.8.1 is a bugfix/maintenance release.

Highlights of 3.8.1
======================

7924criticalFix handling of command line arguments in koha-remove
7998critical3.8 UI cleanup, tweaks to new

Re: Proposed QA Enhancements

Galen Charlton — 2012-05-21T17:52:22

Hi,

On May 21, 2012, at 1:38 PM, Chris Nighswonger wrote:

+1 -- this seems like a obvious procedure documentation fix, hopefully one that just more clearly describes existing practice.

[snip]

These go hand-in-hand.  I agree that reducing the QA burden the RM is a good thing, but in order for that to happen, I think one question that needs an answer first is how do we increase the size of the QA team?  Or to phrase it more broadly, what can we do to encourage more people to do QA, whether or not the current QA structure is used as is or changed?

Regards,

Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc-DI3WXjSZzk1VtazZjgo0Tw< at >public.gmane.org
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrw

Proposed QA Enhancements

Chris Nighswonger — 2012-05-21T17:38:58

I am making two proposals that will help "tighten" up our QA procedures a
bit in order to facilitate clarity and transparency in our patch
submission/acceptance workflow. Currently the workflow is described in the
wiki here:

http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow#Steps

1. I propose that we modify step 5 to read:

"The patch is checked and signed-off by the QA team member. Then the bug
status is set to Passed QA"

This will ensure that we have clarity that the patch was, indeed, touched
by a member of the QA team, as well as increasing the accuracy of QA stats
in git.

2. I propose that the RM be the QA of last resort. At present the stats
show that the RM is doing the majority of the QA'ing. "Last resort" is a
condition evoked by all members of the current QA team acknowledging that
no one among them has the time, etc. to do QA on a particular patch the RM
feels needs to be pushed OR by a bug remaining in the "Signed Off" status
beyond a fixed time period of four weeks. This mec

Re: Public IP for Koha

Paul Poulain — 2012-05-21T16:26:33

Le 21/05/2012 18:17, Fridolyn SOMERS a écrit :
Agreed, but you can also achieve that by using a virtual host configured
to listen only on your staff interface (you need a static IP for your
library though). that's how we do for most of our hosted customers afaik.

Re: Public IP for Koha

Fridolyn SOMERS — 2012-05-21T16:17:08

Hie,

Personnaly, I strongly recommand not to use a public access on intranet.

Can't you set up a VPN between your 4 branches libs ?
It is the most secured network solution.
Less secured solution is a reverse-proxy.

Best regards,

On Mon, May 21, 2012 at 4:16 PM, Tim O'brien <obtim123-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Public IP for Koha

Tim O'brien — 2012-05-21T14:16:09

Hi,
I manage  to intall koha 3.6. My institution has four branch libraries and
i wanted to use public IP so that the other three branches can access the
system. I am thinking of using public IP for these purpose. Kindly advice
me: the risks and if there are better options.
Regards,
O'brien
_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: Koha Calendar

Galen Charlton — 2012-05-16T18:57:58

Hi Elliott,

On May 16, 2012, at 12:00 PM, Elliott Davis wrote:

The table special_holidays itself currently just sets closed days, but just using a date field rather than year/month/day seems reasonable.  I'm less sure about using a timestamp field; if we extend special_holidays to cover not just closures but alternative opening and closing times, I think it might be better to use two time fields to set the opening and closing times, e.g.

special_holidays:
  the_date date
  open_time time
  close_time time
  is_open_at_all boolean

Regards,

Galen
--
Galen Charlton
Director of Support and Implementation
Equinox Software, Inc. / The Open Source Experts
email:  gmc-DI3WXjSZzk1VtazZjgo0Tw< at >public.gmane.org
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:    http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.g

Koha Calendar

Elliott Davis — 2012-05-16T16:00:11

As I'm sure everybody running master has realized, bug 5549 introduced a new module Koha::Calendar.  After digging around in the module I realized that the table special_holidays had separate columns for year, month, and date.  I am wondering what the rationale is behind this decision.  If it was simply I preference I would like to propose that we move it to replace the 3 current columns with a timestamp so that the calendar can take advantage of setting open and closed hours and fining for hourly based items accordingly.


      Elliott Davis
      Library Systems Analyst
      Robert R. Muntz Library
[Description: Telephone]903.565.5542<tel:903.565.5542>
[Description: Envelope]tdavis-Zkq3jaIVT4KVc3sceRu5cw< at >public.gmane.org
[Description: Chrome]http://library.uttyler.edu<http://library.uttyler.edu/>

_______________________________________________
Koha-devel mailing list
Koha-devel-yy2XUMoudrGBeeJdjao7tfCrwMbev77B< at >public.gmane.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :

sandbox system

Paul Poulain — 2012-05-16T12:27:36

Hello koha-devel,

I just pushed a few minuts ago the 1st version of the sandbox scripts
I've developped and that is available to facilitate testing of Koha patches.
You'll find everything, including some installation notes at
http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary
(git clone git://git.koha-community.org/contrib/global.git contrib, in
the sandbox directory)

PS: if you want to improve my scripts, you're welcomed !