Re: [Koha-devel] IMPORTANT: Git branch master is now main

[Magnus Enger via Koha-devel]

Kia ora!

Thanks for the heads up!

Den 19.04.2024 16:41, skrev Fischer, Katrin via Koha-devel:
Please note that this change doesn’t only affect the Koha repository, 
but also our side project and tool repositories. In your local 
repositories you will want to rename the local branch to main and then 
set it to track main in the upstream repository:


git config --global init.defaultBranch main

git branch --move master main

git branch –u origin/main

git pull


I did the above, but got this:

~/code/kohaclone (master)$ git config --global init.defaultBranch main
~/code/kohaclone (master)$ git branch --move master main
~/code/kohaclone (main)$ git branch –u origin/main
fatal: Not a valid object name: 'origin/main'.
~/code/kohaclone (main)$ git pull
remote: Enumerating objects: 667, done.
remote: Counting objects: 100% (667/667), done.
remote: Compressing objects: 100% (236/236), done.
remote: Total 545 (delta 364), reused 435 (delta 289), pack-reused 0
Receiving objects: 100% (545/545), 132.56 KiB | 161.00 KiB/s, done.
Resolving deltas: 100% (364/364), completed with 104 local objects.
From https://git.koha-community.org/Koha-community/Koha
 * [new branch]main   -> origin/main
Your configuration specifies to merge with the ref 'refs/heads/master'
from the remote, but no such ref was fetched.

I had this in .git/config:

[branch "main"]
remote = origin
merge = refs/heads/main

And had to change it to this, to make it work:

[branch "main"]
remote = origin
merge = refs/heads/master

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL

[Magnus Enger via Koha-devel]

Den 12.04.2024 08:24, skrev David Cook:

Not yet. At some point I need to get better at sharing Koha plugins more widely.


Just dump it to Github or similar, and set the version to 0.0.1. ;-) 
Release early, release often.


Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL

[Magnus Enger via Koha-devel]

Den 12.04.2024 04:13, skrev David Cook via Koha-devel:
I have a RepairRecord plugin, so I might do a version in that first, and 
if that goes well I could look at upstreaming a patch…


Intriguing! :-) Is it available somewhere?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL

[Magnus Enger via Koha-devel]

Hi!

Den 12.04.2024 03:36, skrev David Cook via Koha-devel:

Hi all,

I just wanted to share a (MariaDB) SQL report that I wrote for finding 
bib records with invalid XML characters:


select biblionumber from biblio_metadata where metadata REGEXP 
'[^\\x{0009}\\x{000A}\\x{000D}\\x{0020}-\\x{D7FF}\\x{E000}-\\x{FFFD}\\x{1}-\\x{10}]+';


Newer versions of Koha strip invalid character from the XML so that you 
can fix your records. I figure this report is very valuable when coupled 
with that functionality. In fact, I just advised a library today to use 
them together to fix up some bad data in their catalogue.


--

On a related note, I’ve noticed that you can have a record with good bib 
XML but invalid item XML, and you won’t notice until your record fails 
to be indexed. So I’m planning on writing a report for that too.


I’m thinking it might be good to add these reports to core Koha, so that 
people can find and fix their own metadata problems. What do people think?


Sounds like an excellent idea! Sounds kind of similar to "MARC 
bibliographic framework test" at /cgi-bin/koha/admin/checkmarc.pl


The report could also be added to 
https://wiki.koha-community.org/wiki/SQL_Reports_Library for older Kohas 
and to be immediately useful.


Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

[Koha-devel] The Global Bug Squashing Day just started (in Kiribati)!

[Magnus Enger via Koha-devel]

Kia ora, dear Community!

If you are in Kiribati (or if you choose Kiribati as your time zone) you 
are in luck, because the Global Bug Squasing Day just started for you!


More information and resources here:
https://wiki.koha-community.org/wiki/2024-03-22_Global_bug_squashing_day

I just copied some numbers related to different bug statuses into the 
wiki page, so we can try and see how much progress we made at the end.


For more individual stats, you can try and see how far you can get your 
name up the lists for "March" (and "2024") on the dashboard: 
https://dashboard.koha-community.org/


But don't get too hung up on those numbers either, *everything* helps 
and *everything* counts:


- Answer a question on IRC or the mail lists

- Add a comment in Bugzilla

- Tall a friend about Koha :-)

And most important: Have fun!

Best regards,
Magnus
Libriotech/imCode

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

[Koha-devel] Reserve the date! There will be a GBSD on 2024-03-22!

[Magnus Enger via Koha-devel]

Kia ora!

The poll has spoken, and there will be a GBSD on 2024-03-22, in the 
timezone of your choice.


More information:

https://wiki.koha-community.org/wiki/2024-03-22_Global_bug_squashing_day

Mark the date in your calendar and come join the fun! How far can we get 
the numbers on https://dashboard.koha-community.org/ to change, and how 
far up the lists can you get your own name?


Best regards,
Magnus
Libriotech/imCode

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

[Koha-devel] Choose your preferred dates for a Gloabl Bug Squashing Day in March

[Magnus Enger via Koha-devel]

Kia ora!

Trying to get another Gloabl Bug Squashing Day (GBSD) going.

Which dates would you prefer?
https://terminplaner6.dfn.de/en/p/4939a0075ab483d3d337f955859f824f-633050
Please reply by Wednesday 2024-03-13.

What's a GBSD, you say? It's fun, that's what it is! See this old page 
for an example and some more information:

https://wiki.koha-community.org/wiki/2020-02-14_Global_bug_squashing_day

TL; DR: Get your name as high up the "Signoffs" list on 
https://dashboard.koha-community.org/ as you can in a given day. (Or the 
other lists, if you prefer.)


Best regards,
Magnus
Libriotech/imCode

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Override sysprefs in Apache config

[Magnus Enger via Koha-devel]

Hi!

Den 16.02.2024 06:56, skrev David Cook via Koha-devel:

I think it might be partially broken.

As per https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16520 
 I 
added the following to the OPAC and the staff interface:


RequestHeader add X-Koha-SetEnv "OVERRIDE_SYSPREF_LibraryName Potato\, 
Potato"


It did indeed load into the OPAC.

In the past, I think it used to fill in and lock the syspref in the 
staff interface as well…  but maybe not anymore. Maybe because it would 
just affect the staff interface, and yet sometimes maybe you only want 
to affect the staff interface… hmm…


We have used this a fair bit to set up alternative/infividual OPACs for 
individual libraries, but I have never seen a setting like that fill in 
or otherwise affect the actual syspref. And how would that work when you 
have 5 different VirtualHost configs all setting their own 
OVERRIDE_SYSPREF_LibraryName?


I can confirm that settings like these work for us:

RequestHeader add X-Koha-SetEnv "OVERRIDE_SYSPREF_LibraryName Grundskolan"
RequestHeader add X-Koha-SetEnv "OPAC_SEARCH_LIMIT 
branch:multibranchlimit-23"

RequestHeader add X-Koha-SetEnv "OPAC_LIMIT_OVERRIDE 1"

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] borrower_message_preference_id reaches limit - quickfix?

[Magnus Enger]

Den 04.01.2023 16:41, skrev Galen Charlton:

Hi,

On Wed, Jan 4, 2023 at 4:28 AM Magnus Enger <mailto:mag...@libriotech.no>> wrote:

 > Bug 32556 - borrower_message_preference_id reaches limit
 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32556 
<https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32556>

 >
 > Has anyone else run into this, and found a quickfix that works?
 >
 > I tried dumping the database, changing the id columns from INT to
 > BIGINT, but got a foreign key error when loading the database back in.

I responded in the bug, but it is possible to remove and recreate the 
specific foreign key constraint that references 
borrower_message_preference_id when changing the type of that column and 
its referrer.


Thanks, Galen!

I was able to modify my dump/edit/load approach to fix the problem. I 
also documented this in Bugzilla.


Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

[Koha-devel] borrower_message_preference_id reaches limit - quickfix?

[Magnus Enger]

Kia ora and happy new year, Koha!

Yesterday I reported this bug:

Bug 32556 - borrower_message_preference_id reaches limit
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32556

Has anyone else run into this, and found a quickfix that works?

I tried dumping the database, changing the id columns from INT to 
BIGINT, but got a foreign key error when loading the database back in.


I have tried to Google this problem, and several solutions suggest 
turning off foreign key checks temporarily. How risky would that be?


Best regaqrds,
Magnus Enger
Libriotech AS
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] My dev list for 22.05

[Magnus Enger]

Bonjour!

Den 03.12.2021 11:00, skrev Paul Poulain:

Hello all,

Regarding this topic : why not also investigate the new data models that 
will replace MARC ?


We store the data in original form (marcxml) and move to 
biblio/biblioitems a part of the data that is useful for basic operation 
(like getting the title and the author).


We could import different data models with the same mechanism (RDA, DC, 
...). The biblio_metadata.format and schema fields were created with 
this idea in mind. That would require an additional layer for 
transforming format/schema to internal Koha and many more things, it's a 
long term goal.


Yeah, that would be an awesome development!

Best regards,
Magnus
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Koha logging out staff users

[Magnus Enger]

Den 19.05.2021 09:28, skrev dc...@prosentient.com.au:

Hi all,

  


Does anyone have an issue where staff users are being logged out of Koha?


What is the setting for SessionStorage?

Is everyone logged out at the same time, or is it more random?

Best regards,
Magnus
Libriotech AS
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] XSLT to display keywords with 650$2 = x

[Magnus Enger]

Den 02.03.2021 23:17, skrev Katrin Fischer:

Hi Magnus,

a slightly different approach I use when I need to filter on $2, below
an example for 084. It has an advantage if you need to add separators
between the fields as the for-each only has the nodes matching your
criteria:


Thanks for your input everyone! I am using the approach provided by 
Katrin, and I'll add it to the wiki when everyone is happy with it.


Best regards,
Magnus
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Rolling DB upgrades

[Magnus Enger]

Den 02.03.2021 15:33, skrev Joonas Kylmälä:

Hi,

I opened a bug report for introducing rolling DB upgrade support for
Koha. I would like to hear if you have anything to object to that or
should we just go ahead and develop that? :)


I must confess I am not 100% certain what you mean by rolling updates 
here. Could you give some more details?


Best regards,
Magnus
Libriotech

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

[Koha-devel] XSLT to display keywords with 650$2 = x

[Magnus Enger]

Kia ora!

I want to display most keywords as usual, but with an exception for 
those from the 650 field. Specifically, I want to display only those 
keywords that has the value "x" or "y" in subfield $2, and hide the 
other 650-keywords. Any hints on how to this in XSLT would be infinitely 
appreciated, and added to the wiki, so others can benefit from the 
solution.


Here is an example:

  
    A
    x
  
  
    B
    y
  
  
    C
    z
  
  
    D
  

I want to display A and B (because they have $2 = x or y), and D 
(because it is not 650), but not C (because it is 650 and $2 is neither 
x nor y).


Best regards,
Magnus
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Elasticsearch changing licences

[Magnus Enger]

Den 19.01.2021 10:09, skrev Paul Poulain:

Hello all,

in the blog Entry, I read : "The SSPL allows free and unrestricted use 
and modification, with the simple requirement that if you provide the 
product as a service to others, you must also publicly release any 
modifications as well as the source code of your management layers under 
SSPL. "


Could Koha be considered to be a "management layer"?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Re: [Koha-devel] Impossible to export config backups when using Debian packages

[Magnus Enger]

Den 16.11.2020 11:36, skrev dc...@prosentient.com.au:

I thought there was a Bugzilla issue for this but I couldn't find it, so I
thought that I'd email the listserv to see what people think (and if anyone
knows the bug reference number).


There are several:

Bug 8437 - Large database backups and large exports from export.pl fail 
under plack

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8437
Released in versions 20.11.00, 20.05.06
Earlier versions of this had a fix for the permissions, but they have 
not been pushed:

https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=11354

Bug 14564 - Export configuration: Unfortunately, no backups are available
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14564
Status: REOPENED

Bug 22143 - Fix permission and owner of configuration backups
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22143
Status: RESOLVED DUPLICATE of bug 14564

Best regards,
Magnus
Libriotech AS
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://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-devel] Assigning TCP ports to per-instance Koha services (e.g. koha-sip)

[Magnus Enger]

Den 12.08.2020 02:49, skrev dc...@prosentient.com.au:

So maybe just hard-coding a default into a per-instance Koha service makes
sense? Or having an option on CLI scripts like koha-sip to define a port (to
ease things for vendors) while leaving the default for users with less
complex requirements?


A --port command line option to koha-sip, with a sane default if not 
activated, sounds like an excellenet idea to me!


Best regards,
Magnus
Libriotech AS
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://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-devel] announcing Urungi, business intelligence made easy for Koha

[Magnus Enger]

On Fri, 15 Mar 2019 at 11:09, Paul Poulain  wrote:
> Hi Magnus & others,
>
> Urungi can't be compared to Grafana, the goal of both tools are not the same. 
> The goal of Urungi : "make librarians being able to build their own 
> statistics and dashboard by drag-and-dropping". The goal of grafana : "The 
> leading open source software for time series analytics" (motto on the 1st 
> page)
>
> The keywords here :
>
> Urungi= building dashboard by end-users. Grafana = building dashboards for 
> end users
> Grafana = time series analytics. Urungi = generic.
>
> For example : "how many active patrons do I have by category and their 
> registration library, zipcode starting by '13%' " ? I don't think it's 
> feasible with grafana. With Urungi, it's done in less than 10 seconds (once 
> you have the layer)

That makes good sense. Thanks for explaining, Paul!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] announcing Urungi, business intelligence made easy for Koha

[Magnus Enger]

Bonjour!

And congratulations Paul & BibLibre! This looks like a really
interesting project. Thanks for sharing!

I am a bit curious about why you created a whole new project instead
of bulding on something like Grafana, for example. Could you say
something about what makes this project special?

Au revoir!
Magnus

On Thu, 14 Mar 2019 at 18:09, Paul Poulain  wrote:
>
> Hello all,
>
> BibLibre is working for a while on a new tool to build statistics & dashboard 
> (http://www.urungi.org) to complete the Koha reports module (Unix philosophy 
> : 1 tool for 1 thing).
>
> I consider that it's now ready for production (we'll begin to deploy it to 
> our customers)
>
> We still have many things on our roadmap 
> (https://kanboard.biblibre.com/public/board/fc524fef4df4404a551f2315511d15d384f4d36ad99c7e36bd05155ed037).
>  What exist works well though
>
> What's next for the Koha community & developers ?
>
> play a bit with our demo platform: https://demo-urungi.biblibre.com/#/home 
> (test/test), linked to a koha DB (French inside !)
> give it a try : https://github.com/biblibre/urungi/
> you'll need to create layers for Koha. The good news is that we already have 
> made some for you. The bad news is that we made it in French. So, just ask, 
> I'll send it to you, translate to English, the Koha community will thank you 
> ;)
> the "hidden" feature : URL #/export => export anything from Urungi #/import 
> => import anything into Urungi
> share your layers, dashboards, ...
> join the fun, submit pull requests, ...
>
> PS: if anyone is using Mantis as support platform, we're also creating 
> layers for Mantis. Next will probably be Coral.
>
> PS2: if anyone is willing to sponsor some features, we're open, as usual.
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Is finesMode = test still operational and sending emails?

[Magnus Enger]

Hi!

The help of the cronjob fines.pl says:

This script calculates and charges overdue fines to patron accounts.
The Koha system preference 'finesMode' controls whether the fines are
calculated and charged to the patron accounts ("Calculate and
charge"); calculated and emailed to the admin but not applied
("Calculate (but only for mailing to the admin)"); or not calculated
("Don't calculate").

I have a library set up with finesMode = test and as far as I can tell
everything is as it should be. But no emails are sent to
KohaAdminEmailAddress. Reading through fines.pl I can see it
generating a file, but not doing any emailing. Am I missing something
or did we loose the emailing somewhere along the way?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Norwegian help needed for fuller testing

[Magnus Enger]

Kia ora!

On 8 May 2018 at 01:24, Mark Tompsett  wrote:
> Greetings,
>
> I was looking around the swarm of bugs that came in recently and found bug
> 20719.
> One of the template files I needed to modify, as far as I can tell, was
> nl-search.
> Could someone who understands the Norwegian system preferences please check
> my patch?

Looks harmless to me!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 0000-00-00 is expired?

[Magnus Enger]

Hiya!

On 13 February 2018 at 20:06, Jonathan Druart
 wrote:
> It would be useful to know the return of
>   SELECT COUNT(*) FROM borrowers where dateexpiry="-00-00"
> on old installations.

I just checked my 5 oldest instances (upgraded regularly since
2009/2010) and none of them had any users meeting this criterium.

Best regards,
Magnus
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Next hackfest in Marseille (March 2018)

[Magnus Enger]

On 16 November 2017 at 15:16, Paul Poulain  wrote:
> Hello,
>
> It's time for me to decide when the next hackfest in Marseille will happen.
>
> Save this date: March 12th-16th. Hoping to see you here !
>
> PS: BibLibre turned 10 last month. We will probably do something special
> during this hackfest (but haven't decided what yet)

Happy anniversary, BibLibre!

I will - sadly - miss the hackfest in Marseille, it is the same week
as our big, national library conference here in Norway.

Is there any chance you could consider moving the hackfest a month or
two closer to summer? In the beginning the focus of the hackfest was
very much signing off and fixing things for the coming release, but it
has grown to be more like a developer conference, I think, and so the
timing with the upcoming release might be less important these days?

Just my NOK 0.02. :-)

Au revoir!
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] FW: Where is the BIG RED WARNING button?

[Magnus Enger]

Kia ora!

I agree that there should be *one* place to get an overview of the
health of the project and what needs doing (at least as far as bugs
go), and for me the natural place for that is the dashboard:
http://dashboard.koha-community.org/

We could probably do more with that, and the data behind it (from
Bugzilla). Like:
- display blockers/critical bugs in big red letters across the top.
(Or use tags to let the RM choose bugs that should be specially
highlighted.)
- make the favicon red when there are such blockers (developers could
have the dashboard always open in a pinned tab)
- highlight the people who helped signoff and qa those critical patches

As for what to work on and when: With a lot more customers there is a
lot less time to sign off patches. So if I am going to do it I need to
find one that
- fits in the time I have available
- is relevant to my customers
- is in a part of Koha I know, or it will take a lot more time
(signing off patches in unknown parts of Koha is great for learning,
of course, but it will take more time)

Just my NOK 0,02.

Best regards,
Magnus
Libriotech

On 11 August 2017 at 02:01, David Cook  wrote:
> I have Arduinos and Raspberry Pis at my desk. Maybe making a literal big red
> warning light isn’t a bad idea… ;). We could call it “The Bug Signal” after
> The Bat Signal. We could make a Kickstarter!
>
>
>
> I’m joking about the Kickstarter, but I kind of like the idea of a little
> physical Koha bug display :p.
>
>
>
> David Cook
>
> Systems Librarian
>
> Prosentient Systems
>
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Direct: 02 8005 0595
>
>
>
> From: koha-devel-boun...@lists.koha-community.org
> [mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan
> Druart
> Sent: Friday, 11 August 2017 1:14 AM
> To: Indranil Das Gupta 
> Cc: Koha-devel 
> Subject: Re: [Koha-devel] FW: Where is the BIG RED WARNING button?
>
>
>
> Hi Indranil,
>
>
>
> Of course I was not talking about new contributors. My main goal for this
> release is to help new people to come on-board.
>
> We refreshed the wiki, wrote a step-by-step how-to "signoff and write
> patches", etc.
>
> I give personal answers to new contributors, guide them, give them quick and
> early feedbacks on their patches in order to keep them motivated.
>
>
>
> This button I am asking for is to alert support companies and regular
> developers that something is (very) urgent and need their attention. I would
> like to stop gesticulating to try getting this attention. I would like a
> button I can push to make a red blinking light on some desks. Then everybody
> is free to ignore it, but they saw it and I will not push it again. It will
> be easier for me to know that people knows, than sending emails, pinging on
> #koha, adding card to the kanban, CCing people on the bug report, without
> never knowing if they are aware of the problem.
>
>
>
> About the kanban: its goal is NOT to replace bugzilla, it has never been and
> will never be.
>
> We are talking about two different tools. One is a bug tracker, the other
> one is a tool to manage/prioritize different tasks, group them under "Epic"
> (big works), form working groups, etc. Moreover community tasks are not
> always one entry in bugzilla, we want to track, discuss and keep history of
> more stuffs than just bugs. Taiga answered this lack. Please re-read the
> wiki page of the kanban if its goal is not clear (or ask me to update it).
>
>
>
> Cheers,
>
> Jonathan
>
>
>
> On Thu, 10 Aug 2017 at 06:43 Indranil Das Gupta  wrote:
>
> Hi
>
> On Wed, Aug 9, 2017 at 7:25 PM, Jonathan Druart
>  wrote:
>
>> I do not see the point to sign-off and QA trivial string patches when
>> blockers are in the queue for weeks (no need to tell me everybody does
>> what
>> do they want, I still agree with that).
>
> I completely get that blockers need to be sorted out. But personally I
> got into Koha dev stream with string patches. How to write the tests
> was a mystery to me in the initial days and I was afraid to get in
> there. And when I did, I made mistakes which others helped clean up
> and that's how I learnt and I'm still learning.
>
> For a newbie, seeing their trivial patch being signed off and pushed
> is a shot of adrenaline and it gives them the confidence to bite into
> bigger pieces. I'm sure that we do not want Koha development to be
> seen as an oligarchy of expert devs, by not pushing the insignificant
> patches when there are blocker patches, especially when there is a
> call up for more "hands on the deck".
>
> Personally I was *not* happy with the shift to taiga. I knew my way
> around BZ. Kanban was a new format to me and having to spend time to
> learn a new pm tool was something that had me dragging my feet. But
> then its human nature.to resist  change. :-)  I will 

Re: [Koha-devel] [Koha] NCIP project

[Magnus Enger]

On 19 May 2017 at 09:07, vikram zadgaonkar  wrote:
> We are working on NCIP server integration with koha.We are looking for
> support for the same.
>
> Currently, ncip framework (server and responses etc) appears to be working.
> However, data from koha db is not being picked up. There appears to be some
> communication error between the koha library (C4) and ncip server's modules.

Are you using the NCIPServer created by Chris Cormack/Catalyst and
later forked/developed by several people, including ByWater and
myself? If so:

How are you running it? I run it something like this:

$ sudo KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml perl
-I/home/magnus/kohaclone/ bin/ncip_dancing.pl --port 80

KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml is the path to the
koha-conf.xml of the Koha instance that NCIPServer should be talking
to.

-I/home/magnus/kohaclone/ is the path to where the C4 and Koha folders
are. This is how NCIPServer knows where to find the C4:: and Koha::
modules it needs.

Hope that helps,
Magnus
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Sending email on behalf of customers

[Magnus Enger]

Thanks for your input, folks! Much appreciated! I will be looking more
closely at your answers in the near future. I'll summarize my findings
here when I have worked out a solution.

Best regards,
Magnus Enger
Libriotech

On 14 February 2017 at 14:46, Hugo Agud <i...@orex.es> wrote:
> Hi
>
> We experienced the same problem, we fixed it using Amazon SES, is like a
> certificate e-mail, it is very easy to use.. Amazon just send a verify mail
> to the address from you're going to send mails, and once is verified it
> becomes a 'certified' mail and all the major firewall, gmail allow to
> delivery them.
>
> Obviosusly you have to configure your mta to send mails using Amazon SES and
> it also have a cost, but it is quite low
>
> If you need more detailed info, just send me a mail
>
> Kindest Regatds
> Hugo
>
> 2017-02-13 16:50 GMT+01:00 SUZUKI Arthur <arthur.suz...@univ-lyon3.fr>:
>>
>> It has nothing to do with SPF, DKIM and such gadget (though it may help).
>>
>> Google wants your mail host to have consistent reverse-dns records (ptr).
>>
>> Which means :
>>
>> host [your ip address]
>>
>> should gives such results :
>>
>> Using domain server:
>> Name: 8.8.8.8
>> Address: 8.8.8.8#53
>> Aliases:
>>
>> [your ip address].in-addr.arpa domain name pointer [your mailhost fqdn]
>>
>> Google's mail servers are really quite a pain to mail to.
>> Also beware if your mailhost has ipv6 enable, the reverse dns record
>> should be consistent for ipv6 too.
>>
>>
>> Le 13/02/2017 à 13:40, Marcel de Rooy a écrit :
>>>>
>>>> My server is available at something like myserver.libriotech.no.
>>>> Should KohaAdminEmailAddress (which is used for From by default) be
>>>> libr...@myserver.libriotech.no or just libr...@libriotech.no?
>>>
>>> Depends on your exact configuration. Both domains may go the same ip
>>> address.
>>> Also check your reverse dns.
>>> When I check via mxtoolbox.com I do not get a response on
>>> myserver.libriotech.no
>>> But I cannot smtp check libriotech.no either.
>>>
>>> ___
>>> Koha-devel mailing list
>>> Koha-devel@lists.koha-community.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/
>>
>>
>> --
>> Arthur SUZUKI
>> Service informatique des bibliothèques
>> BIBLIOTHÈQUES UNIVERSITAIRES
>> Université Jean Moulin Lyon 3
>> 6 Cours Albert Thomas - B.P. 8242 – 69355 Lyon Cedex 08
>> ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr
>> L'Université Jean Moulin est membre fondateur de l'Université de Lyon
>>
>>
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.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-devel mailing list
> Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Sending email on behalf of customers

[Magnus Enger]

Thanks Marcel!

I'll definitely give this a try!

On 13 February 2017 at 11:44, Marcel de Rooy  wrote:
> As a workaround: Use real library email address in ReplyToDefault and 
> ReturnpathDefault.
> Use the real server domain in the From address like library@[yourserver]

My server is available at something like myserver.libriotech.no.
Should KohaAdminEmailAddress (which is used for From by default) be
libr...@myserver.libriotech.no or just libr...@libriotech.no?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Sending email on behalf of customers

[Magnus Enger]

Hi!

I run Koha for several customers, and a number of them have email
enabled. The sender of these emails is set to be the email of the
library in question, e.g. libr...@example.org.

Now, the problem is that services like GMail and Hotmail are not
accepting these emails, because they see them as non-legitimate, in
the sense that they are sent from some random server somewhere on the
internet, that is not in any way associated with example.org.

And they are right, of course! I *am* sending email on behalf of
libraries from some random server on the internet. So, the question
is: how to get around this? I see two possibilities:

1. Work with the sysadmins of the organizations of each library and
have them include my servers in their "published lists of trusted
servers" (I am thinking of stuff like SPF, PTR, OpenDKIM etc - I have
not gotten my head around all of the details.) This would entail
talking to lots of different sysadmins (if there is one) at lots of
different organizations = lots of work...

2. So I was thinking about a second optoin - paying my way out,
through some service like the ones listed here:
https://zapier.com/learn/email-marketing/best-transactional-email-sending-services/
My thinking is that GMail and Hotmail would "think" like "hm, this
email says it comes from example.org, but it originated from some
random server. BUT it was sent through ServiceX, which you have to pay
to use, so it is probably legit". But I have no idea if GMail and
Hotmail works like that at all. Does anyone else have a clue about
this? Or some other way to solve the problem?

Best regards,
Magnus Enger
Libriotech
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Koha 3.22/16.05 & Apache, Plack for a high load/large library

[Magnus Enger]

On 3 October 2016 at 14:21, Petter Goksøyr Åsen
 wrote:
> I don't know if it's related, but we've had lots of troubles with Plack 
> sessions and caching.
> The only reliable option at the moment seems to be caching on disk in /tmp.

I had a problem with sessions and memcached. The solution was to store
sessions in the database. This has worked well for several sites that
are used in production.

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Coding patterns discussion

[Magnus Enger]

Oops, looks like we have created two things with very similar names:

https://wiki.koha-community.org/wiki/Developers_Handbook
https://wiki.koha-community.org/wiki/Developer_handbook

The second one was started by me to try and tie together all the pages
in the wiki that a developer should know.

Coule we rename one of them?

Best regards,
Magnus

On 13 September 2016 at 12:19, Kyle Hall  wrote:
> On Mon, Sep 12, 2016 at 7:38 PM, David Cook 
> wrote:
>>
>> I didn’t even know Koha::Exceptions was a thing! How does it work? Wasn’t
>> Kyle going to work on some sort of developer handbook so there would be a
>> central repository of guidelines/patterns?
>
>
> You can find it here:
> https://wiki.koha-community.org/wiki/Developers_Handbook
>
> It doesn't have any documentation on using Exceptions, and that would
> definitely be a good addition. I feel like it's a bit "messy" as I started
> it by using the coding guidelines as a base, but it's not a bad start! If
> anyone wants to work on it, please do!
>
>>
>>
>>
>> I read the Koha Coding Guidelines many moons ago, but it would be nice to
>> know when there are updates. Since I’m not as active in the community these
>> days, I don’t know if I have much of a say over things anymore, but it would
>> be good to be informed of updates to the guidelines, so that a person can
>> contribute more efficiently when one does contribute.
>>
>>
>>
>> TryCatch requires Moose while Try::Tiny is lightweight, but I guess we’re
>> going down the Moose rabbit hole anyways these days? Doesn’t TryCatch just
>> do try/catch/catch instead of if/elsif/elsif?
>
>
> I had thought TryCatch's use of Moose would be a deal-breaker ( at least
> until Koha is officially plack-only ), but after inspecting the code, I
> don't believe it actually uses Moose. It does use packages in the Moose
> namespace, but it doesn't appear to use Moose itself, though it's possible I
> didn't go far enough down the rabbit hole. At this point I think I'm in
> favor of TryCatch instead of Try::Tiny do to it's ability to catch multiple
> types of exceptions and it's avoidance of messing with error handlers.
>
> Kyle
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Sessions terminated at random under Plack

[Magnus Enger]

On 30 August 2016 at 20:40, Tomas Cohen Arazi  wrote:
> My suggestion would be to set sessionStorage to 'mysql' and disable the
> RestricSessionByIP syspref.

Yup, this made the problem with timed out sessions go away. Does that
indicate it is related to caching/RestricSessionByIP and will be fixed
in the next stable release?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Sessions terminated at random under Plack

[Magnus Enger]

Dear Community,

I am seeing a strange problem, and I'm not sure where to start digging.

I have a (big) server with 30 odd Koha instances. One of these
instances has been running under Plack for quite some time now,
without any problems.

Two new instances have a problem where librarians get kicked out of
the intranet more or less frequently, with a message like "Your
session has expired, please log in again".

We had this problem on 3.22.x.
After upgrading to 16.05.02 it went away.
After upgrading to 16.05.03 last night it came back again.

It is not consistent. Earlier today it looked like you could log in,
click on a link, get thrown out, login again and then things would
work. Later users got kicked out every single time they clicked on a
link in the intranet.

All sites are running off the official Debian packages, on the same server.
Memcached is installed, enabled and used for storing sessions.
Switching SessionStorage to the DB does not stop the problem.
Stopping and disabling Plack for these two instances makes the problem go away.

I have not found anything interesting in Plack or Apache logs.

Anyone got a hunch what might be causing this? Or where to start digging?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Updating Koha manual documenation

[Magnus Enger]

Hiya!

The description of the koha-docs mailing list says "This list will be
used to send patches to the documentation manager. Please send all
documentation patches to this list for review." I know I have sent
documentation patches to this before, and Nicole has pushed them.
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs

The easiest thing might be to ask Nicole on IRC, I guess.

Best regards,
Magnus

On 20 April 2016 at 15:33, Barton Chittenden
 wrote:
> Agreed.
>
> There is a 'Documentation' category in bugzilla. The documentation is in
> docbook format; I'm sure that you could supply patches, or I'm sure that
> Nicole would be happy to make edits if you supply the text.
>
> --Barton
>
> On Wed, Apr 20, 2016 at 8:59 AM, Tomas Cohen Arazi 
> wrote:
>>
>> I think it should follow the regular BZ workflow.
>>
>> 2016-04-20 4:00 GMT-03:00 David Cook :
>>>
>>> Hey all,
>>>
>>>
>>>
>>> What’s the procedure for updating Koha manual documentation?
>>>
>>>
>>>
>>> I’d like to expand on
>>> http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see there is
>>> a kohadocs.git to which Nicole contributes
>>> (http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary), but do
>>> those changes still go through Bugzilla?
>>>
>>>
>>>
>>> Does one clone the repository and just post the patches to Bugzilla and
>>> mark it as documentation? And then Nicole/RM does the merging from there?
>>>
>>>
>>>
>>> I basically just want to add that searching “title” will use
>>> “index.dc.title” because the default set in pqf.properties is “dc”, and that
>>> you can use other sets by adding the prefix like “f bath.keyTitle=test” in
>>> yaz-client when using “querytype cql”.
>>>
>>>
>>>
>>> But there’s heaps of other search documentation that I’d like to edit, so
>>> I figure I may as well get up to speed on the procedure! I’ve been saying
>>> for years that I should contribute to the documentation, so maybe I should
>>> put my words where my... words are!
>>>
>>>
>>>
>>> David Cook
>>>
>>> Systems Librarian
>>>
>>>
>>>
>>> Prosentient Systems
>>>
>>> 72/330 Wattle St
>>>
>>> Ultimo, NSW 2007
>>>
>>>
>>>
>>> Office: 02 9212 0899
>>>
>>> Direct: 02 8005 0595
>>>
>>>
>>>
>>>
>>> ___
>>> Koha-devel mailing list
>>> Koha-devel@lists.koha-community.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/
>>
>>
>>
>>
>> --
>> Tomás Cohen Arazi
>> Theke Solutions (http://theke.io)
>> ✆ +54 9351 3513384
>> GPG: B2F3C15F
>>
>> ___
>> Koha-devel mailing list
>> Koha-devel@lists.koha-community.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-devel mailing list
> Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day 2015-04-13!

[Magnus Enger]

Dear Community!

Apologies for cross-posting... nah, not really. ;-)

In the last community meeting it was decided that we should do a
Global bug squashing day (GBSD) again, on Monday 2015-04-13:
http://wiki.koha-community.org/wiki/2015-04-13_Global_bug_squashing_day

- 3.20 is due in the not too distant future, and we should make sure
it has as few known bugs as possible
- The QA team will have a QA sprint on the 17th (if I remember
correctly), let's make sure they have a looong queue of signed off
patches to work from!

So grab your nearest dev install or sandbox and join the fun!

Best regards,
Magnus Enger

PS
And don't forget https://www.gofundme.com/TomasNeedsALaptop
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Browser-based tests

[Magnus Enger]

On 17 March 2015 at 11:06, Jonathan Druart jonathan.dru...@biblibre.com wrote:
 Hello devs,

 A (very) quick email to let you know I have submitted patches on
  bug 13691 - Add some selenium scripts
 and
  bug 13849 - Introduce acceptance tests with cucumber

 I would like to start a discussion on these subjects: selenium,
 cubumber, browser-based tests, acceptance tests, etc.
 What are you opinions? Should we stuck to Test::WWW::Mechanize or it's
 worth to have a look somewhere else?

 Useless ? Worth a try ? Very useful ?

I think integration/acceptance tests would be very, very useful. Unit
tests at the level of individual subroutines are awesome, of course,
but some automated way of telling if things are working on a higher
level would definitely be a good thing.

I have been a fan of Test::WWW::Mechanize, but with our increasing
reliance on JS and AJAX, I think something that can work with those
things too are a necessity. I don't have strong opinions on what tools
we should use, though.

Best regards,
Magnus
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] General IRC meeting 11 March 2015

[Magnus Enger]

Kia ora Community!

Just a small reminder that there is a general community IRC meeting in
just about 24 hours:

11th March 2015 at 10:00 UTC

Date and time conversion:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meetingiso=20150311T10

See ya there!

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Meeting pre-hackfest Marseille 2015

[Magnus Enger]

Bonjour!

Could it be an idea to add lightning talks/persentations to the
spreadsheet? I have an idea for one I could do myself (on kohadevbox:
https://github.com/digibib/kohadevbox) + a couple I would love to
listen to (how OPL and SUB plan to build things on top of Koha).

That said, I did love the first hackfest, where the focus was really
on signing off patches and getting stuff done. I'd love for the
hackfest to stay a true hackfest and not develop into a conference. So
maybe lightning talks limited to a few minutes is a good idea? Anyone
else got an opinion on that?

Au revoir!
Magnus

On 6 February 2015 at 15:39, Jonathan Druart
jonathan.dru...@biblibre.com wrote:
 Hello,
 I would like to organise a quick IRC meeting on #koha to launch
 discussions and to know what attendees want to do at the hackfest in
 Marseille.
 The workshops tab of the HackFest Europe march 2015 doc is still
 almost empty, it will be a good way to fill it.

 I propose next Wednesday at 15 UTC [1] if it fits everybody.

 It would be good to see all hackfest attendees present :)

 Regards,
 Jonathan

 [1] 
 http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meetingiso=20150211T15
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Improving Plack support on the staff client

[Magnus Enger]

On 1 May 2014 08:28, Robin Sheat ro...@catalyst.net.nz wrote:
 I've been doing a bit of work lately making patches for the staff client
 to improve its ability to use Plack without exploding in weird ways.

Hooray for that, Robin!

I have taken the liberty of creating an omnibus to make it easier to
get an overview of these bugs:

Bug 12173 - Improving Plack support on the staff client OMNIBUS
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12173

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Here's a little thing i wrote... kohaprofile

[Magnus Enger]

Dear Community,

I spent the last day of the hackfest in Marseille hacking together a
proof of concept script for checking changes in the performance of
Koha over time:

https://github.com/digibib/kohaprofile

The idea is to step x commits back in time, run a bunch of timed
tests/benchmarks on Koha, take one step forwards in time, run the
tests again etc. Hopefully this might be able to show us what the
general trends are, and if there are any changes that lead to
noticeable increases in response times.

If you run the same benchmark a few times in a row, the response times
vary quite a bit. Perhaps there is too much noise for this to be
really useful. (To mitigate this, the script can run the tests y
number of times and record the average time. Perhaps there are better
ways to deal with the statistics of this, like removing the fastest
and the slowest time etc.)

This is a proof of concept, so I would be really interested in
hearing your thoughts on it. If the concensus is that it does not
yield interesting data, I'll abandon the project. If people think it
has some merit I would be more than happy to accept pull requests for
improving it. :-)

See the README for some ideas for improvements.

Does anyone know if there are tools that can do what I'm trying to
accomplish here (specifically the idea of stepping through Git history
to check performance) already?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Development meeting - save the date

[Magnus Enger]

On 17 February 2014 09:54, Paul Poulain paul.poul...@biblibre.com wrote:
  * is there something we should prepare ? (for example, are you
 expecting some of us come with ideas/suggestions ? should we put them on
 the wiki before the meeting

Just in case people have not noticed, I have taken the liberty of
turning Galen's email into a wikipage for the meeting:
http://wiki.koha-community.org/wiki/Developers_IRC_Meeting,_February_25,_2014

See you there!
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Proposal of a new development for Marseille hackfest, feedback needed

[Magnus Enger]

Hiya Paul et al!

I think those are two very interesting ideas, well worth pursuing.

A wiki page describing something similar to the second idea was
created a while ago:
http://wiki.koha-community.org/wiki/Add_a_button_to_the_intranet_for_registering_with_the_Koha_community

Au revoir!
Magnus
libriotech.no

On 11 February 2014 18:30, Paul Poulain paul.poul...@biblibre.com wrote:
 Hi koha-devel,

 There are sometimes debates about how and who is using Koha, how it is
 setup, which decision is of general interest.
 I had 2 ideas that could be developed during the hackfest. 2 of BibLibre
 developers are very motivated by the idea, anyone else can join us ;-)

  1st idea : collecting -anonymous- data on staff interface usage
 We sometimes are wondering whether librarians are running an old version
 of IE, or if they have a large screen, or if the page X is often run or not.
 There's a tool that could let us know: piwik (BibLibre already has an
 offer on Piwik for the OPAC)
 The idea here would be to add piwik for staff interface, and collect all
 datas on a single piwik instance.
 We made something (quick) for one of our current supported library, just
 to see what kind result we could get. We're quite happy with the
 performances, datas are interesting (which browser is used, which screen
 size, which pages. [ For example, the library runs an average of 40
 times reports/catalogue-stats.pl every day (yes, that's crazy ;-) ).
 This page is worth being optimized !!! ]

 The only caveat we've seen for now is that it can be tricky to have many
 websites pointing to the same piwik database.
 We also are not completely peaceful with having 10 000 librarians
 calling the server. We could face a heavy load...

 But that's worth investigating imo.

 (for those who don't know what is piwik, it's like google analytics, but
 respect your privacy ;-) Ah, and it's a software developed by a frenchy,
 living in new zealand, that has office hosted by catalystNZ afaik)
 If the community likes the idea, we will ask him for any advice on the 2
 caveats we fear.
 [ PS: please avoid starting a troll about piwik collecting anonymous
 data or not because of the IP. Anyway, the feature will be trigger-able
 by the library. ]

  2nd idea : collecting nominative datas.
 We very often face the question how many libraries are using Koha
 So the idea is to have a form that let the library declare itself.
 Library name, type (academic, public,...), country,...
 We could also collect other data, like catalog size, systempreferences
 values to be able to make statistics.

 Example of answers we could get:
  * how many libraries are using Koha in Africa ?
  * What's the average catalog size ? Which library is the largest one ?
  * Is someone/how many libraries are using the insecure mode
 (syspref=insecure set to Yes) ? [ If no, we can drop it ! ]

 Each library could choose to share or not the data (and maybe which
 level of data. One could accept to declare itself  share sysprefs, but
 not appear on nominative listings for example)
 A specific website could be made to display informations, either
 nominative or not.

 Do you like those ideas ?

 PS: BibLibre is of course willing to host piwik and statistics servers.
 --
 Paul POULAIN - BibLibre
 http://www.biblibre.com
 Free  Open Source Softwares for libraries
 Koha, Drupal, Piwik, Jasper

 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.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-devel] Advice on syncing and DBIC

[Magnus Enger]

Hi!

I am working on Bug 11401 - Add support for Norwegian national library card:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11401

The goal is to sync patrons in Koha back and forth to the Norwegian
national patron database. In order to do this I need to keep track of
- which patrons should be synced (they can choose to opt out of the syncing)
- a sync status, to see which patrons are new, which have been changed
and which are already synced
- the date of the last sync

I am a bit undecided about whether I should use extended patron
attributes for this, or add columns to the borrowers table. Some
pros and cons:
- Attributes are less intrusive, they only need to be added to systems
that want to sync with the Norwegian national patron database.
- New columns could be re-used by others, to implement other syncing
schemes, and they are easier to work with, as far as I can see.
I am currently leaning towards adding columns.

Now the thing is that I want to change the syncstatus every time
AddMember or ModMember is called, so I want to add some logic to these
subroutines, perhaps like this (... indicates lines that have been
edited out for clarity):

use Koha::Database;
...
sub AddMember {
my (%data) = @_;
...
$data{'borrowernumber'}=InsertInTable(borrowers,\%data);

# If NorwegianPatronDBEnable is enabled, we set the nllastsync
attribute to something that a
# cronjob will use for syncing with NL
if ( C4::Context-preference('NorwegianPatronDBEnable') == 1 ) {
my $borrower =
Koha::Database-new-schema-resultset('Borrower')-find(
$data{'borrowernumber'} );
$borrower-update( { 'syncstatus' = 'new' } );
}
...
}

Would that be an OK way to do it? Or is mixing in DBIC in existing
subroutines like this frowned upon?

Would it be cleaner to add a module like Koha::Borrower::Sync (that
could be re-used by other syncing schemes), with methods like
SetBorrowerSyncstatus( $patronnumber, $value ) that would then look
something like this:

use Koha::Database;
sub SetBorrowerSyncstatus {
my ( $borrowernumber, $value ) = @_;
my $borrower =
Koha::Database-new-schema-resultset('Borrower')-find(
$borrowernumber );
$borrower-update( { 'syncstatus' = 'new' } );
}

Any advice on this would be much appreciated!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] RFC: make OPAC XSLT be shared by all themes

[Magnus Enger]

On 6 January 2014 18:13, Galen Charlton g...@esilibrary.com wrote:
 I would appreciate feedback on the proposal

+1

Re-use all the things!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Architectural goals for 3.16

[Magnus Enger]

Dear Community!

My devious little plan for 3.16 is to start getting some RDF/Linked
Data/Semantic Web stuff into Koha.

There are two sides to this, both of which should of course be
completely opt-in and without side-effects for the MARC-based
functionality in Koha:

* MARC2RDF conversion

MARC records should be converted to RDF and stored in a triplestore,
whenever they are added to Koha or edited in Koha.

Chris Cormack already made a start on this, but I think we agree now
that the actual conversion should be re-written to use Catmandu::RDF.
My plan is to either nag Chris into doing this or to fork what he
already did and re-write it myself. ;-)

* Browsing

RDF data in the triplestore should be browsable in the OPAC. I have
code for this that is almost ready to be submitted, but I will do some
more tweaking before I unleash it.

Even if I fail miserably at all of this, it sounds like 3.16 is going
to be pretty great! :-)

Best regards,
Magnus Enger
libriotech.no

On 10 December 2013 01:59, Galen Charlton g...@esilibrary.com wrote:
 Hi,

 For discussion, here is a list of some of some things I would like to see in
 3.16.  This is not meant to be complete; please feel free to use this thread
 both to comment on my goals and to suggest goals that you're personally
 willing to advocate for -- and by advocate for, I mean that you and/or the
 institutions who support your Koha activity are ready and willing to take
 concrete steps to help implement it.  I ask that if all you have is an idea
 -- no matter how good! -- but not any concrete code or plans to have it be
 ready in the next few months -- please start a different thread.

 [1] Deprecation of the GRS-1 mode for Zebra.

 Reason: the DOM index filter allows greater flexibility for setting up
 indexing definitions.  The DOM filter also offers a path (among other
 options) towards indexing non-MARC metadata.

 Obstacles: the default UNIMARC indexing rules for the DOM filter need more
 testing.  There is also an ongoing discussion about the desired semantics
 for the Any index, which at present behaves differently with the current DOM
 indexing rules as compared with GRS-1.

 Upgrade considerations: in order to truly deprecate the GRS-1 filter, at
 some point there will have to be a forced reindexing upon upgrade.

 [2] Use DBIx::Class to deploy the database schema for new installations.

 Reason: Maintaining multiple SQL schema scripts, one for each DBMS we want
 to support, would be error prone.  Making edits to classes under
 Koha/Schema, then using -deploy(), offers the possibility of initializing
 both MySQL and PostgreSQL databases.

 DBIx::Class::Schema::Versioned could be used at as way of managing schema
 updates

 Obstacles: DBIx::Class doesn't automatically know anything about indexes
 required for good performance; consequently, it will be necessary to write
 hooks for (at least) MySQL to create the necessary indexes.

 [3] Relaunch PostgreSQL support

 Reason: PostgreSQL is a compelling alternative to MySQL, and now that we
 have DBIx::Class in place, managing the schema for PostgreSQL is now a more
 reasonable proposition.

 For 3.16, I propose the following specific goals:

 - Koha will be installable on a Pg database
 - A staff user will be able to create or import and bib record and item
 - A public catalog user will be able to search for and retrieve that item
 - a reasonable number of the database-dependent tests will pass

 In other words, I'm not proposing that Pg support be ready for production by
 3.16, just that it be just good enough that a developer who wants to improve
 Pg support isn't starting from nothing.

 [4] Upgrade the version of Bootstrap we use to 3.x.

 A new major release of Bootstrap was made recently.  Unfortunately, it is
 not backwards compatible with previous versions (see
 http://bootply.com/bootstrap-3-migration-guide for a taste of the issues
 involved).

 As much as I'm personally not exactly a fan of the changes that were made to
 the CSS class names, we're much better off if we bite the bullet now and
 update both staff and OPAC to use the new version of Bootstrap rather than,
 two years down the road, finding out that we're completely stuck on Boostrap
 2.3.

 Regards,

 Galen
 --
 Galen Charlton
 Manager of Implementation
 Equinox Software, Inc. / The Open Source Experts
 email:  g...@esilibrary.com
 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@lists.koha-community.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-devel mailing list
Koha-devel@lists.koha-community.org
http

[Koha-devel] 2013-09-23 Global bug squashing day - come join the fun!

[Magnus Enger]

Dear Community!

Some of the dates in Galen's RM proposal* are drawing dangerously near:

25 September 2013: feature slush**
3 October 2013: feature freeze
31 October 2013: string freeze
21 November 2013: release of 3.14.0

That's right, feature slush is just a few days away. And we have
something of a queue of things that would be cool to have in 3.14:
http://dashboard.koha-community.org/

So let's join forces and knock those numbers way down, on Monday 23rd:
http://wiki.koha-community.org/wiki/2013-09-23_Global_bug_squashing_day
That page should give you some clues about things you can do, but if
you are unsure about how you can contribute, don't hesitate to jump on
the IRC and ask for help:
http://koha-community.org/get-involved/irc/

And rumour has it there will be a QA Sprint immediately the GBSD, but
Katrin will have to fil in the details of that.

Have fun!
Magnus

* See http://wiki.koha-community.org/wiki/Proposal_for_RM_3_14_gmcharlt

** Excerpt from the last general IRC meeting:

cait gmcharlt: can you define feature slush a little? want to
prevent any misunderstandings if possible :)
gmcharlt cait: feature slush -- any new features that have hit
passed QA by that date will be included in 3.14, assuming they don't
raise signfiicant QA concerns on my part
gmcharlt new features that have /not/ hit passed QA by feature slush
are more liable to be left for the next release; if you want something
that misses slush to make it in, you'll need to advocate for it
thd Why does slush have the name slush?
gmcharlt a partial freeze, of course
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day starts in less than 2 hours!

[Magnus Enger]

(...if you choose to go by Kiribati time).

http://wiki.koha-community.org/wiki/2013-08-23_Global_bug_squashing_day

Currently the dashboard reports these numbers:

Needs Signoff - 166 (56 bugs)
Signed Off - 99 (47 bugs)
Passed QA - 34 (12 bugs)
Failed QA - 142
Patch Doesn't apply - 21
In Discussion - 115

So there is plenty of fun to be had! Come join us!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] GBSD: 2013-08-09 is done, next is 2013-08-23!

[Magnus Enger]

Dear Community!

Global bug squashing day 2013-08-09 just ended. Here are the numbers before:

Needs Signoff...157 (54 bugs)
Signed Off...90 (46 bugs)
Passed QA28 (12 bugs)
Failed QA...150
Doesn't apply26
In Discussion...119

and after:

Needs Signoff...138 (44 bugs)
Signed Off..116 (62 bugs)
Passed QA29 (13 bugs)
Failed QA...145
Doesn't apply26
In Discussion...121

Needs signoff went from 157 to 138, which is not too shabby,
considering this is probably a time when a lot of people are on
holiday.

In fact, this was so much fun/use, the next GBSD will be in just 2
weeks time, on 2013-08-23:
http://wiki.koha-community.org/wiki/2013-08-23_Global_bug_squashing_day

So mark that date in your calendars, drop all your other appointments
and come join the fun!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day - come join the fun!

[Magnus Enger]

Dear community!

GBSD just ended in NZ, but wherever you are you can choose to abide by
any timezone, so if you choose Hawaii time there is still almost 22
hours to go!

When we started the numbers looked like this:

Needs Signoff...157 (54 bugs)
Signed Off...90 (46 bugs)
Passed QA28 (12 bugs)
Failed QA...150
Doesn't apply26
In Discussion...119

And a couple of hours ago they looked like this:

Needs Signoff...144 (43 bugs)
Signed Off..112 (62 bugs)
Passed QA28 (12 bugs)
Failed QA...147
Doesn't apply26
In Discussion...119

As you can see, some progress has been made, but there is still a lot
of fun to be had. So let go of everything else and come join the fun!
Get your name on the dashboard for the first time or see if you can
climb in the ranks! Maybe you can even beat Kyle as the #1 signoff
hero of August?
http://dashboard.koha-community.org/

Not sure how you can help? Jump on the IRC channel and we will help
you figure it out!
http://koha-community.org/get-involved/irc/

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day 2013-08-09

[Magnus Enger]

Dear community!

There will be a Global bug squashing day on 2013-08-09 (in the
timezone of your choice):
http://wiki.koha-community.org/wiki/2013-08-09_Global_bug_squashing_day

Come join the fun! Not sure what you can do? Jump on the IRC channel
and we will help you figure it out!

Current stats are:

Needs Signoff - 169 (57 bugs)
Signed Off - 77 (38 bugs)
Passed QA - 26 (12 bugs)
Failed QA - 144
Patch Doesn't apply - 21
In Discussion - 119

...so there is plenty of fun to be had!

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Koha + Blacklight

[Magnus Enger]

On 17 June 2013 11:57, Fitzpatrick, Christopher c...@wmu.se wrote:
 Hi everyone,

 We recently launched a beta version of a Blacklight (
 https://github.com/projectblacklight/blacklight)  instance that is backed by
 our Koha ILS. You can see it here = http://beacon.wmu.se/ .

 Currently, it takes indexes nightly MARC dumps from Koha into Solr, with
 live availability and location lookups performed asynchronously through the
 koha-restful  api.

Nice work! I'm just curious:

How are you transfering the records from Koha to Blacklight? OAI-PMH
or something else?

And when you say koha-restful api - is that the code from BibLibre (
http://git.biblibre.com/?p=koha-restful;a=summary ), or something
else? Like the GetAvailability call in ILS-DI, for example?

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] BibLibre hires a student to work during summer for the community

[Magnus Enger]

On 4 April 2013 20:53, Chris Cormack ch...@bigballofwax.co.nz wrote:
 So writing WWW::Mechanize tests to test things functions also.

 I'd like to build up a set of tests that can simulate an hour in an
 average(ish) library, and have them running after any successful
 jenkins build. I can help with the jenkins side and scripting the
 deploy, (i'll be doing it with packages) but having someone write the
 tests (Jared has a good start in his release manager scripts) would be
 awesome.

Hooray for this! And welcome Kenza!

There is also bug 8300, which could do with a second (or third?) opinion:

Bug 8300 - Koha should have mechanized testing suite
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8300

Best regards
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] XSLT and superfluous xmlns attributes

[Magnus Enger]

On 18 January 2013 09:20, Frédéric Demians frede...@tamil.fr wrote:
 and here is the stylesheet in /home/magnus/koha/biblioteksok.xslt:

 Try this:

 Suppress:

  xsl:template match=marc:controlfield[@tag=001]/
  xsl:template match=marc:datafield[@tag=850]/

That did not work, when I left these out the old elements were not removed.

 and replace:

 xsl:template match=marc:leader

 with:


 xsl:template match=marc:record

Ah, that helped!

What I ended up using was this:

https://gist.github.com/1918264#file-biblioteksok-xslt

The clue was including an xmlns-definition on the xsl:element:

 xsl:element name=datafield xmlns=http://www.loc.gov/MARC21/slim;

Thanks for your help Frédéric!

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Hackfest 2013 in Marseille

[Magnus Enger]

On 17 December 2012 10:39, Paul Poulain paul.poul...@biblibre.com wrote:
 Hello, koha-devel,
 After 2011 and 2012, i'm happy to announce the dates for the 2013
 hackfest in Marseille :
 http://www.biblibre.com/en/blog/entry/koha-hackfest-in-europe-in-2013

And look what goes on in Marseille from Friday 22 to Monday, March 25:
http://www.savim.eu/

Some kind of food festival with 250 food producers, as far as I can tell! :-)

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Can't search after loading a 3.8 sql dump into 3.10

[Magnus Enger]

On 10 December 2012 21:00, Jared Camins-Esakov
jcam...@cpbibliography.com wrote:
 We were troubleshooting the issue on IRC, and Fridolyn's theory was correct.
 Magnus reported a new bug for it: bug 9256
 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9256 ).

Thanks for your help on this, Fridolyn and Jared!

As far as I can tell, this bug breaks the 3.10 packages for
marcflavour != marc21...

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Koha hackfest in 2013 in Marseille, (proposing a date)

[Magnus Enger]

On 12 November 2012 18:38, Paul Poulain paul.poul...@free.fr wrote:
 EPIC FAIL: the proposed dates are in *march*, not feb !!!
 from march, 18th to march, 22th

That works for me! With a bit of luck I might even get the rest of the
family to tag along.

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Upgrading Koha's license?

[Magnus Enger]

On 14 November 2012 22:35, BWS Johnson abesottedphoe...@yahoo.com wrote:
 I'd say simple majority at an IRC meeting with this advertised on the 
 agenda so it doesn't sneak up and bite anyone.

I have added it to the agenda:
http://wiki.koha-community.org/wiki/General_IRC_meeting,_5_December_2012

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] update Koha download pages, with some info for beginners

[Magnus Enger]

 On Mon, Nov 12, 2012 at 1:13 PM, Mason James m...@kohaaloha.com wrote:
 so… is this a good idea, or not?

+1

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] docbook-xml triggers scary update-catalog message(s) under Ubuntu 12.10

[Magnus Enger]

On 5 November 2012 00:51, Mark Tompsett mtomp...@hotmail.com wrote:
 This said, docbook I think is just a build
 dependency, not needed at runtime. One of these days I need to separate
 these out.


 If it is just a build dependency, then the message is most definitely a
 warning and can be ignored. That was something I was wondering as well (is
 it a just a build dependency?).

I think docbook-xml is only used to convert the koha-common man pages
from docbook to um, man format, which happens when the packages are
built.

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Some thoughts from QA team

[Magnus Enger]

On 24 October 2012 12:49, Mason James m...@kohaaloha.com 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

Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Default search options in the OPAC

[Magnus Enger]

On 18 September 2012 15:58, Owen Leonard oleon...@myacpl.org wrote:
 We've now got two patches pending which seek to add more options to
 the default OPAC search, the masthead search bar which currently
 includes options for Library catalog, title, author, subject, ISBN,
 series, and call number:

 Add Phrase Searching to OPAC Search
 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8778

 Add accesssion [barcode] number to the drop down list in OPAC Search
 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8302

 I'll say right out that I'm opposed to these changes, but I want to
 bring it up here on the list so we can discuss.

I agree that the simple search should be simple. But we could probably
spend a lot of time arguing about how simple is simple enough.

Seems to me that it would be better to find a way to make this easily
configurable. I'd like to suggest a simple solution:

In the template, we could have

select id=masthead_search class=left name=idx
[% OPACSearchOptions %]
/select

Then we could have a syspref called OPACSearchOptions (or something),
with this initial content:

option value=Library catalog/option
option value=tiTitle/option
option value=auAuthor/option
option value=suSubject/option
option value=nbISBN/option
option value=seSeries/option
option value=callnumCall number/option

This would keep current behaviour, but make it easy to add or remove
or re-arrange the option elements. And we could explain in the docs
or on the wiki how the values here relate to indexes defined in more
or less obscure config files.

Yes, it would require fiddling with HTML and Zebra (or Solr) indexes
to change it. No, it would not be GUI and pretty. But it would be so
simple, even I could submit a patch for it.

Thoughts?

Best regards,
Magnus
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Default search options in the OPAC

[Magnus Enger]

On 8 October 2012 13:42, Fischer, Katrin katrin.fisc...@bsz-bw.de wrote:
 I am sorry, but there is a big problem with that solution as suggested. The 
 search options won't be translatable and only available in one language at a 
 time. I think what we really need is a way to have all the HTML system 
 preferences in an editor like we have for news that supports content for 
 multiple languages.

Gah, I agree of course. Too simple to be true...

Best regards,
Magnus
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Default search options in the OPAC

[Magnus Enger]

On 8 October 2012 15:07, Marc Véron ve...@veron.ch wrote:
 Hi all,

 I agree with Katrin that we should have the possibility to localize the HTML
 system preferences.

Okay, slightly more crazy proposal.

In the template (note the | eval):

select id=masthead_search class=left name=idx
[% OPACSearchOptions | eval %]
/select

And then in OPACSearchOptions (or something):

[% IF ( OPACLanguage == 'nb-NO' )  %] [%# Don't remember if there is a
variable for this, or if it would have to be added%]
option value=Katalogen/option
option value=tiTittel/option
option value=auForfatter/option
option value=suEmne/option
option value=nbISBN/option
option value=seSerie/option
option value=callnumHyllesignatur/option
[% ELSE %]
option value=Library catalog/option
option value=tiTitle/option
option value=auAuthor/option
option value=suSubject/option
option value=nbISBN/option
option value=seSeries/option
option value=callnumCall number/option
[% END %]

Please feel free to shoot this down - I have no idea how it would
affect performance etc. :-)

Best regards,
Magnus
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Signed off patches to the patches list?

[Magnus Enger]

Hi!

http://wiki.koha-community.org/wiki/Git_bz_configuration still says
It is still considered good practice to send the signed off patch to
the patches mailing list, but it seems that few folks do it and using
git bz seems to have made this practice obsolete. Any objections to
deleting this line and the command that accomplishes it?

Best regards,
Magnus
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Short notice: Global Bug Squashing Day 2012-08-10

[Magnus Enger]

Dear Community!

The bug wranglers are a bit rusty, but we would like to suggest a GBSD
for Friday 2012-08-10 (yup, that's *this* Friday)!

All the usual activities of signing off patches etc are encouraged:
http://wiki.koha-community.org/wiki/2012-08-10_Global_bug_squashing_day

Remember that even one signoff will now make your name show up on the
super cool dashboard Chris C has created:
http://dashboard.koha-community.org/
... as well as in future relase notes!

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Koha API for use in mobile app

[Magnus Enger]

Hi and sorry for the delay!

On 31 May 2012 22:02, Robert Nay rob...@naygames.com wrote:
 I am looking to create an iPhone/Android app for my local library, and am
 wondering about the best way to go about this. Does Koha have some API that
 can be accessed from a third-party client (in this case, a mobile
 application)? Koha pages seem to have an unapi link in them, is this
 something that could be used? I am relatively new to Koha, so any help or
 advice would be greatly appreciated.

I don't know unapi, but what I would recommend looking at is ILS-DI and SRU.

ILS-DI is activated with the ILS-DI syspref, and is self documenting, see e.g.:
http://head.bibkat.no/cgi-bin/koha/ilsdi.pl

To get SRU working you need to enable the Z39.50 server in your
koha-conf.xml file.

Hope that helps!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Signing-off a patch for a customer

[Magnus Enger]

On 30 May 2012 02:38, Chris Cormack ch...@bigballofwax.co.nz wrote:
 On 30 May 2012 12:30, Chris Nighswonger cnighswon...@foundations.edu wrote:
 On Tue, May 29, 2012 at 11:12 AM, Ian Walls koha.sek...@gmail.com wrote:

 To me, the role of QA is to be highly conservative.  The QA team needs to
 look at a piece of incoming code, and not only judge it on how well it does
 it's intended purpose, but how it affects all the other code and workflows
 that surround it.  The folks creating and signing off on code are often
 looking to answer the question does it work?.  I approach the QA process
 asking the question what does it break?.

 Often times, the answer is nothing, and we get a great new feature in
 our codebase. But sometimes the patch changes a core function or variable
 declaration in a way that isn't spotted, and only applicable on certain use
 cases.  Or a new dependency is added that conflicts with something
 existing.  Or a security hole is introduced under some conditions.  A person
 asking does this work? isn't necessarily going to spot these things in
 their testing; our code is very complex.  I'm sure we can all recall cases
 where piece of code was committed to do one thing, and then required a
 followup because it broke something else under specific circumstances.

 I strongly believe that having a 'neutral party' to do the QA work is
 essential to keeping our codebase strong and healthy.  We need the fresh set
 of eyes, the different perspective, the alternate use case.  We need someone
 asking what does it break?, and I don't think the folks who've been asking
 the question does it work? are the best suited to that task.


 +1

 +1 from me also

+1

Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Gerrit as a workflow aid [Was: Re: Signing-off a patch for a customer]

[Magnus Enger]

On 30 May 2012 02:21, Chris Nighswonger cnighswon...@foundations.edu wrote:
 I am very much in favor of us implementing gerrit to help tighten up our
 workflow.

 I would like to see us begin a discussion on this and put it up for a vote
 among developers during the June or July meeting.

 So let's talk!

And for those of us who don't already know it, maybe someone could
point out some recommended reading (
http://gerrit-documentation.googlecode.com/svn/Documentation/2.4/intro-quick.html
perhaps? ) and/or outline how they see it affecting our workflow?

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] missing pdf files for Koha 3.6 and 3.8 manuals

[Magnus Enger]

On 11 May 2012 15:23, Nicole Engard neng...@gmail.com wrote:
 On Fri, May 11, 2012 at 6:25 AM, MJ Ray m...@phonecoop.coop wrote:
 Are those issues recorded anywhere, so people can try fixing?

 MJ I can ask around - but like I said, I'm not the right person to be
 answering these questions :) I update the XML, push the patches, and
 they automagically post to the web in HTML :)

If someone is going to mess around with things in this area, could
they please consider setting up an automated conversion to ePub format
too?

With dbtoepub it's as simple as this:

$ dbtoepub -o /path/to/manual.epub /path/to/manual-in-git/en/manual.xml

I have an old demo here:
http://div.libriotech.no/kohaebook/
I have not found a good way to convert to .mobi yet, so please
disregard those parts.

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] How to view Zebra indexes..?

[Magnus Enger]

On 13 April 2012 12:51, Adam Dickmeiss a...@indexdata.dk wrote:
 You should be able to view indexing for any record by doing a 'present' of
 the record with element set zebra::index and syntax being XML or SUTRS.

 Most Z39.50 client should be able to do that.

 yaz-client example:

Excellent!

Adam: Would you mind if I posted this example verbatim in the Koha
wiki for future reference? I'll give you credit for it, of course!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Next week is Global Bug Squashing Week!

[Magnus Enger]

Dear Community,

The deadlines for getting stuff into version 3.8 are drawing near:
http://wiki.koha-community.org/wiki/Roadmap_to_3.8

As most of you are probably aware now, there will be a super cool
hackfest in Marseille next week:
http://drupal.biblibre.com/en/blog/entry/2012-hackfest-in-europe

For those of us who can't be there in person, it's still possible to
contribute to the fun, by joining the Global bug squashing week:
http://wiki.koha-community.org/wiki/2012-03-19_Global_bug_squashing_week

As far as I can tell, the beginning of this week will be the last
chance for having new features signed off with any hope of getting
them into 3.8. And there are bugfixes and minor improvements to look
after.

Not sure how you can help? Jump on the IRC channel (
http://koha-community.org/get-involved/irc/ ) and we will help you get
started! And with the sandboxes provided by BibLibre all you need in
order to join the fun is a web browser!

http://wiki.koha-community.org/wiki/2012-03-19_Global_bug_squashing_week

See you there!
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Proposal to change Bugzilla Status and Patch Status values

[Magnus Enger]

2012/1/6 Ian Walls ian.wa...@bywatersolutions.com:
 What do people think?  Does this sound like a reasonable change to make?

+1
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] adding fields in XSLT (bug 7332)

[Magnus Enger]

2011/12/15 Fischer, Katrin katrin.fisc...@bsz-bw.de:
 +1 from me too.

 The XSLT is done so that only information in your records shows up. I don't
 see why people would not want that.

+1

In an ideal world I think we would have some cool graphical tool where
each library could easily configure their own display by dragging tags
and subfields around, set conditions, formatting etc. Well, one can
dream...

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day #7 - It's on!

[Magnus Enger]

Dear Community!

Global bug squashing day #7 is almost an hour old - in Kiribati!
http://wiki.koha-community.org/wiki/2011-12-07_Global_bug_squashing_day

And remember: you don't have to be a hard-core developer to make a
difference! Take a look at the wiki page above to see all the fun
things you can do!

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] New dates for GBSD: 2011-12-07 and 2012-01-06

[Magnus Enger]

Yes, that's right, after some consultation on IRC I'm proposing two
dates, to avoid the short notices that have been creeping up on us
lately:

http://wiki.koha-community.org/wiki/2011-12-07_Global_bug_squashing_day
http://wiki.koha-community.org/wiki/2012-01-06_Global_bug_squashing_day

And yes, 2011-12-07 is a Wednesday (some of us have been talking about
trying another dey than Friday) and yes it does fall on the same date
as the next general IRC meeting. The devious plan of the bug wranglers
is to cajole people into squashing bugs after the meeting! ;-)

See you there!
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] RM monthly newsletter

[Magnus Enger]

On 26 November 2011 06:23, Chris Cormack ch...@bigballofwax.co.nz wrote:
 On 26 November 2011 07:02, Paul Poulain paul.poul...@biblibre.com wrote:
 PS: is this newsletter worth being published on koha-community.org
 website ? somewhere else (send me your ideas !)
 --

 I think on the website is a great place for it

+1

Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Proposal for Global Bug Squashing Day: 2011-11-04

[Magnus Enger]

On 25 October 2011 16:49, MJ Ray m...@phonecoop.coop wrote:
 Please please please could we use something more open than Google?
 Has the IRC been working well so far?  Are you after other features
 which the current tools don't have?

Sorry for being unclear about this. Google Hangout is a
video-conference-thingamajig, so what I had in mind was establishing
an audio-visual link to the lucky people in Thane, just for the fun of
it. I don't believe IRC works very well with audio and visuals, yet...
;-)

And yes, Google Hangout is a Google service, yes it does require
download and installation of a closed plugin-thingy. But on the
plus-side, I know several potential GBSD'ers use and it works quite
well (even with video from several participants, as opposed to Skype).
It was always meant as a fun add-on to the main event and
participating is in no way required to be part of the fun that is
GBSD.

More details here:
http://www.google.com/support/plus/bin/topic.py?hl=en-GBtopic=1257349parent=1698315

I'm very interested in learning about FLOSS alternatives for
videoconferencing, though!

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 2011-10-07 Global bug squashing day - 3.6 String Freeze Sprint

[Magnus Enger]

Dear Community!

String freeze for 3.6 has been set to 8 October 23:59 UTC.

I'd like to propose a Global bug squashing day for October 7th, as a
last, concerted effort to get as much as possible from the needs
signoff queue into 3.6. Details are here:

http://wiki.koha-community.org/wiki/2011-10-07_Global_bug_squashing_day

Happy squashing!
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 2011-09-02 Global bug squashing day #4 - It's on! Join the fun!

[Magnus Enger]

Dear Community!

Just a gentle reminder that GBSD#4 started about half an hour ago, in
Kiribati. If Friday September 2nd is inconvenient for you in your
timezone you might want to consider diving in now, to get a head
start! ;-)

For those watching at home, a lot of the changes on Bugzilla will be
tweeted here:
http://twitter.com/#!/KohaGBSD

Best regards,
Magnus Enger


-- Forwarded message --
From: Magnus Enger mag...@enger.priv.no
Date: 30 August 2011 08:35
Subject: 2011-09-02 Global bug squashing day #4
To: Koha list k...@lists.katipo.co.nz, koha-devel@lists.koha-community.org


Dear Community!

Just a gentle reminder that GBSD#4 is approaching fast:
http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day

Please bear in mind that the Release Manager has declared the following dates:
* Feature freeze – 22 September 23:59 UTC – From this point on, no new
features will be considered for inclusion into 3.6.0
* String freeze – 8 October 23:59 UTC – no bugs that change templates
accepted after this point. This allows the translators to translate
without things changing on them
http://koha-community.org/key-dates-3-6-0/

That means we have about 3 weeks for getting any new features in! And
there are (at the moment) 83 (!) bugs/patches waiting to be signed
off:
http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDfield0-0-0=cf_patch_statusquery_format=advancedtype0-0-0=equalsvalue0-0-0=needs%20signofforder=bug_idlist_id=10641

See one in there that you would like to make sure makes it into Koha
3.6? YOU can help it along by signing off on it!
http://wiki.koha-community.org/wiki/Sign_off_on_patches

Of course, we should take every opportunity to sign off patches in the
coming weeks, but why not make a concerted effort on Friday September
2nd 2011 (in your timezone) and see how far we can get, as a team?
Could we cut the queue in half?

Happy hunting!
Magnus Enger

PS
And you don't have to be a developer to help either!
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 2011-09-02 Global bug squashing day #4

[Magnus Enger]

Dear Community!

Just a gentle reminder that GBSD#4 is approaching fast:
http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day

Please bear in mind that the Release Manager has declared the following dates:
* Feature freeze – 22 September 23:59 UTC – From this point on, no new
features will be considered for inclusion into 3.6.0
* String freeze – 8 October 23:59 UTC – no bugs that change templates
accepted after this point. This allows the translators to translate
without things changing on them
http://koha-community.org/key-dates-3-6-0/

That means we have about 3 weeks for getting any new features in! And
there are (at the moment) 83 (!) bugs/patches waiting to be signed
off:
http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDfield0-0-0=cf_patch_statusquery_format=advancedtype0-0-0=equalsvalue0-0-0=needs%20signofforder=bug_idlist_id=10641

See one in there that you would like to make sure makes it into Koha
3.6? YOU can help it along by signing off on it!
http://wiki.koha-community.org/wiki/Sign_off_on_patches

Of course, we should take every opportunity to sign off patches in the
coming weeks, but why not make a concerted effort on Friday September
2nd 2011 (in your timezone) and see how far we can get, as a team?
Could we cut the queue in half?

Happy hunting!
Magnus Enger

PS
And you don't have to be a developer to help either!
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Importing checkout records into Koha

[Magnus Enger]

2011/8/9 Chris Cormack chr...@catalyst.net.nz:
 * Hartman, David W. - GBTS Library (david.w.hart...@disney.com) wrote:
 Yes, due date is provided and name - names are unique! :)

 Right, then a script like Robin's is probably the way to go.

Here is my script for doing something similar:
https://github.com/MagnusEnger/LibrioTools/blob/master/tidem/loans.pl
Again, this is tailored to one specific system/situation (where the
data about current checkouts was in HTML format!), but it might give
some hints...

What I did was create a .koc-file with my script, which I could then
import using Home › Circulation › Offline Circulation File Upload. I
figured that would reduce the risk of putting data in the wrong place
or missing some field in some table that should have data in it...

The format of the .koc file is documented here:
http://wiki.koha-community.org/wiki/Koha_offline_circulation_file_format

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Bugzilla default assignee

[Magnus Enger]

On 2 August 2011 17:09, Paul Poulain paul.poul...@biblibre.com wrote:
 Le 02/08/2011 16:56, Mahesh T Pai a écrit :
 Paul Poulain paul.poul...@biblibre.com
 writes:

   My question : what should I do to discard this entry from my list ? I
   tried to remove me as assignee, but bz don't want no assignee. Should
   we have a virtual assignee for this kind of entry ? Should I close the
   bug entry as it's an enhancement, no-one plan to take care of it ? Other
   idea ?

 How about the devel list as default assignee?

 Several projects have it that way, afaict.

 Maybe not as the default assignee, but as a possible assignee, it's a
 good idea.
 It would mean ok guys, I won't deal with this one, anyone
 voluntering/concerned can take it !)
 We could then add a public filter bugs to assign on bugzilla saved
 queries.

+1 from me!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Patch format

[Magnus Enger]

On 1 August 2011 02:49, Mason James m...@kohaaloha.com wrote:
 i think an little improvement to our current patch workflow, would be to just 
 attach the patch to a bug, in bugzilla
 an automated bugzilla script could then send that new patch to the patches 
 list

+1 yay!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 2011-08-05 Global bug squashing day #3

[Magnus Enger]

Dear Community,

As far as I can tell, proposing 2011-08-05 as the next Global bug
squashing day should not be totally out of order:
http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day

Join the fun!
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Koha - WAI / WCAG

[Magnus Enger]

On 8 July 2011 21:04, Owen Leonard oleon...@myacpl.org wrote:
 Is there any experience / plan for working around Koha and WAI (Web
 Accessibility Initiative) / WCAG (Web Content Accessibility Guidelines) for

 As far as I know no one has done any formal evaluations of Koha with
 regard to WAI or WCAG. Suggestions, data, bug reports, etc. are
 welcome!

That sure sounds like something vendors might have to answer in an RFP
process. I have yet to answer an RFP that mentions it, but hopefully
some of the other vendors has something to share...

If not, maybe we could use the wiki to collaborate on an answer? Or
if someone has something to share, maybe we could still stick it on
the wiki, so we can collaborate on keeping it up to date?

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global bug squashing day #2 - 1 short summary and 2 questions

[Magnus Enger]

Dear Community!

GBSD#2 should now be finnished in all timezones (I think), and here
are some of the results:

Does not apply  63  - 38
Failed QA   53  - 57
Needs Signoff   50  - 53
Passed QA   1   - 8
Signed Off  90  - 94

http://wiki.koha-community.org/wiki/2011-07-08_Global_bug_squashing_day#Numbers

Now that actually looks less impressive than it is. A lot of bugs were
moved from Does not apply to Needs signoff (hence the increase in
Needs signoff), and some were moved from Signed off to Passed QA
etc. See the link above for some snapshots taken during the day.

This page:
http://bugs.koha-community.org/cgi-bin/progress.pl
shows 44 bugs changing status on 2011-07-07 and 2011-07-08.

And as Paul has already said somewhere else, a lot of work was also
put into organizing RFCs on the wiki:
http://wiki.koha-community.org/wiki/Category:RFC_Status

All in all, a productive day for Koha, I think!

A couple of questions:

* BibLibre are having community days every other Friday (as far as I
have heard). Should there be GBSDs to coincide with every one of
these, or is every other enough (= GBSD every 4 weeks)?
(I think for me personally dedicating 1 day every 4 weeks to this
stuff is probably the best I can do at the moment, but others might
see it differently.)

* Is Friday the best day for GBSDs?
(I know I personally want to make pizza and be around the wife and the
dogs when Friday afternoon comes around, whereas on another weekday it
might be easier to get some work done after dinner. Whaddaya think?)

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Preparing GBSD (friday)

[Magnus Enger]

On 6 July 2011 18:56, Paul Poulain paul.poul...@biblibre.com wrote:
 Hello world,

 I’m preparing Friday Global Bug Squashing Day, and want to share a
 bugzilla query with you.

 I've added a Patches for GBSD query that display, Koha module by Koha
 module, all patches needing a sign-off, failed QA or does not apply.
 To see it : bugs.koha-community.org  Preferences  saved searches 
 click patches for GBSD

Thanks, Paul! I have added it to the wiki page:
http://wiki.koha-community.org/wiki/2011-07-08_Global_bug_squashing_day
(Or actually, I have added it to a template, so we can easily re-use it ;-)

 I think it's useful to organise the GBSD = it's better to work module by
 module.
 At least, at BibLibre, developers will be 2 for a module, working on all
 kind of patches. Of course, everybody will be on IRC, so the group of 2
 can become a group of 3 ;-)

Yay!

Best regards,
Magnus Enger

PS
GBSD has already started in some timezones:
http://www.timeanddate.com/worldclock/custom.html?sort=2 ;-)
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Preparing GBSD (friday)

[Magnus Enger]

On 6 July 2011 18:56, Paul Poulain paul.poul...@biblibre.com wrote:
...
 I think it's useful to organise the GBSD = it's better to work module by
 module.
 At least, at BibLibre, developers will be 2 for a module, working on all
 kind of patches. Of course, everybody will be on IRC, so the group of 2
 can become a group of 3 ;-)

I have added a table of bugs that needs signoff to the wiki, sortable
by module/component:
http://wiki.koha-community.org/wiki/2011-07-08_Global_bug_squashing_day#Claim_a_bug_for_signoff.21
(Sorry for the truncated names of the categories, that's how I got 'em
from Bugzilla...)

It might not be necessary to claim bugs before signing off, but at
least it's there if people want to use it...

Have fun!
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] 2011-07-08 Global bug squashing day

[Magnus Enger]

Dear Community!

Since there were no severe complaints after the first Global sign off
day, I'll risk proposing another one, with a new name:

http://wiki.koha-community.org/wiki/2011-07-08_Global_bug_squashing_day
(globsquad for short)

The name has been chosen to highlight that this day is meant not only
to encourage signing off on bugs, but to encourage all kinds of
activities that can help bugs and patches move along in the right
direction.

BibLibre has pledged to participate this time (and hopefully more
times in the future too), so we should be able to get even more stuff
done than the last time. Yay!

See you there!
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Trouble with CSS files after creating package with translations

[Magnus Enger]

2011/6/22 Robin Sheat ro...@catalyst.net.nz:
 All going to plan, this should work :) Once someone has worked out the tricks
 the first time, any other translations should just be a copy-paste of that
 with appropriate language codes changed.

Thanks for that run-down Robin! This definitely goes on my summer
holiday cool projects list! ;-)

 It's been on my radar for a while (I really want to get -en-nz into there for
 example), but I've lacked the time, and things aren't going to get quieter in
 the next month or three it looks like (too many libraries want Koha now
 apparently :)

A mixed blessing? Nah, not really... ;-)

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Summary of Global Signoff Day 2011-06-15 - more to come?

[Magnus Enger]

Dear Community!

* GSOD #1

Our very first Global Signoff Day (GSOD) was held on 2011-06-15.

During the 48 hours that make up a day in all available time zones, we
reduced the number of bugs that had status Needs signoff from about
76 to about 45. (There were some bugs that got the Needs Signoff
status during the day, which complicates counting somewhat...)

You can see a more or less complete list of what bugs were changed here:
http://wiki.koha-community.org/wiki/Global_sign_off_day,_2011-06-15

See the bottom of this page for some more numbers, and keep in mind
that the dates there are relative to UTC:
http://bugs.koha-community.org/cgi-bin/progress.pl

As far as I can tell we were about 6 people signing off on things
during GSOD #1, which is not an astronomical figure, but i still think
we made some good inroads into the queue. (A number of the remaining
bugs are actually ones that depend on other bugs that have failed QA,
so they are not really available for signing off.) Imagine what we
could have done if there were more of us... ;-)

* GSOD #2

BibLibre have said all their staff will dedicate half a day every two
weeks to signing off on bugs and similar tasks (woohoo!). I would like
to propose another GSOD to coincide with their first such day, which
is scheduled for 2011-07-08. Motto: The more, the merrier!

Some questions spring to mind:

- How can we get more people involved?
- Should the name of the event reflect that other activities (such
as closing bugs) are encouraged too?
- How can we make it even more fun?
-- Better/other lists and visualisations?
-- Could we have the huginn bot on IRC annonunce new signoffs, the
same way it does needs signoffs?
-- Could we use some kind of VoIP/videoconferencing tools to make the
social interactions seem more um... real?

Or is GSOD a really bad idea, would it be better to channel our energy
into making signoffs (and similar activities) look more like an
ongoing task, and less something you only have to think about once a
month?

Best regards,
Magnus Enger
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Trouble with CSS files after creating package with translations

[Magnus Enger]

2011/5/30 Robin Sheat ro...@catalyst.net.nz:
 Magnus Enger schreef op vr 27-05-2011 om 14:46 [+0200]:
 Looks to me like the packaging/packages is doing some rearranging of
 the CSS files that only works for the English templates and not for
 templates translated into other languages? Are there any package gurus
 out there who are able to see what is going on?

 From the debian/rules file:

 rm -r $(TMP)/usr/share/koha/opac/htdocs/opac-tmpl/prog/en/lib/yui
 ln -s /usr/share/javascript/yui 
 $(TMP)/usr/share/koha/opac/htdocs/opac-tmpl/prog/en/lib/yui

 and then a bunch of installs of css and png files
 into ...-tmp/prog/en/css. Perhaps this is what you're seeing that causes
 things to lay out differently.

Finally some time to look at this again...

Yup, that is definitely the heart of the matter! Installing another
language replicates lots of JS/CSS/image stuff from opac-tmpl/prog/en/
to e.g. opac-tmpl/prog/nb-NO/ and then the packaging process comes in
and does it's magic, but only on the stuff in opac-tmpl/prog/en/ and
not on the stuff that has been installed for any other languages.

The weird thing is that it seems to work just fine for the Intranet,
but not for the OPAC... I am not sure why yet.

So far, these are the possibilities I can see:

- Move the JS/CSS stuff out of the language specific directories and
have all languages use this stuff from one and the same location.

- Make debian/rules do it's stuff for all installed languages with
some kind of foreach-loop, if that is possible

- Find another way to handle translations than the process I am trying
now (install the languages, commit the resulting files with git, build
packages with build-git-snapshot)

- Make custom versions of debian/rules to accommodate translations,
I'm currently testing this: http://div.libriotech.no/kohadeb/rules -
the packages are being built as we speak

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Trouble with CSS files after creating package with translations

[Magnus Enger]

On 17 June 2011 12:24, Magnus Enger mag...@enger.priv.no wrote:
 - Make custom versions of debian/rules to accommodate translations,
 I'm currently testing this: http://div.libriotech.no/kohadeb/rules -
 the packages are being built as we speak

PS
Looks like that actually worked! ;-)

Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Reminder: Global sign off day 2011-06-15 (in your time zone of choice)

[Magnus Enger]

Dear Koha friends!

Just a gentle reminder that Global sign off day is just 2,5 hours away
in Kiribati, and fast approaching for other time zones too... Se the
message below for details.

Best regards,
Magnus Enger


-- Forwarded message --
From: Magnus Enger mag...@enger.priv.no
Date: 7 June 2011 16:16
Subject: Global sign off day, 2011-06-15
To: Koha list k...@lists.katipo.co.nz, koha-devel@lists.koha-community.org


Dear all!

(And sorry for cross posting... At least a little bit ;-)

We had such great fun in Marseilles earlier this year, signing off
patches, that I have been wondering if it would be possible to
re-create some of that experience without incurring the costs of
travel. I broached the subject on IRC earlier today and after the
briefest and least democratic of processes, we decided to declare
15th June 2011 as a Global Sign Off Day:
http://wiki.koha-community.org/wiki/Global_sign_off_day,_2011-06-15

The hope is that as many people as possible will be able to set aside
as much other work as possible on this day, and concentrate on signing
off patches, to reduce the queue of bugs that are currently waiting
for sign-off (66 at this moment:
http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDfield0-0-0=cf_patch_statusquery_format=advancedtype0-0-0=equalsvalue0-0-0=needs%20signofforder=bug_idlist_id=7042)

We will try to visualise and document the progress that is made, to
make it more fun and maybe even tickle the competitive instincts a
little bit... ;-)

And who knows, if this day is a success, maybe we could turn it into a
regular tradition? *

If you have not signed off on a patch before, now is the perfect time
to do it! The more the merrier! The process is outlined here:
http://wiki.koha-community.org/wiki/Sign_off_on_patches And there will
be people on IRC that you can ask for help and guidance!

Best regards,
Magnus Enger

* On the other hand, let's hope we can keep the queue as short as possible...
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Global sign off day, 2011-06-15

[Magnus Enger]

Dear all!

(And sorry for cross posting... At least a little bit ;-)

We had such great fun in Marseilles earlier this year, signing off
patches, that I have been wondering if it would be possible to
re-create some of that experience without incurring the costs of
travel. I broached the subject on IRC earlier today and after the
briefest and least democratic of processes, we decided to declare
15th June 2011 as a Global Sign Off Day:
http://wiki.koha-community.org/wiki/Global_sign_off_day,_2011-06-15

The hope is that as many people as possible will be able to set aside
as much other work as possible on this day, and concentrate on signing
off patches, to reduce the queue of bugs that are currently waiting
for sign-off (66 at this moment:
http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDfield0-0-0=cf_patch_statusquery_format=advancedtype0-0-0=equalsvalue0-0-0=needs%20signofforder=bug_idlist_id=7042)

We will try to visualise and document the progress that is made, to
make it more fun and maybe even tickle the competitive instincts a
little bit... ;-)

And who knows, if this day is a success, maybe we could turn it into a
regular tradition? *

If you have not signed off on a patch before, now is the perfect time
to do it! The more the merrier! The process is outlined here:
http://wiki.koha-community.org/wiki/Sign_off_on_patches And there will
be people on IRC that you can ask for help and guidance!

Best regards,
Magnus Enger

* On the other hand, let's hope we can keep the queue as short as possible...
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Trouble with CSS files after creating package with translations

[Magnus Enger]

Hi!

I recently built my first debian package, based on the 3.4.x branch
from git, and with the addition of having installed translations for
the Nordic languages. (I'll write up the process of doing that on the
wiki, once I'm sure I have the correct steps.)

I used the Perl version of build-git-snapshot provided by attachment
4007 from bug 5602 to build the packages:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5602
(I'll sign off on the patch once I see the resulting package working,
I promise! ;-)

After installing the package and creating a library I noticed that a
couple of CSS files are missing from the OPAC when it is viewed in any
language other then English, making it look weird:
http://esme.priv.bibkat.no/

Firebug tells me these two files can not be found, when the language
is not English:
http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/reset-fonts-grids.css
- 404 Not Found
http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/skin.css - 404 Not Found

But when I view the front page in English, those two files *are*
found, but from a different path:
http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/reset-fonts-grids.css - 200 OK
http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/skin.css - 200 OK

The contents of the css-folders for the two languages are quite different:

http://esme.priv.bibkat.no/opac-tmpl/prog/en/css/
[TXT]   colors.css  05-May-2011 20:59   0   
[TXT]   hierarchy.css   05-May-2011 20:59   1.5K
[IMG]   menu-button-arrow-disabled.png  22-May-2011 14:59   173 
[IMG]   menu-button-arrow.png   22-May-2011 14:59   173 
[TXT]   opac.css22-May-2011 14:59   34K 
[TXT]   print.css   05-May-2011 20:59   3.1K
[TXT]   reset-fonts-grids.css   22-May-2011 14:59   5.0K
[TXT]   sanop.css   05-May-2011 20:59   28K 
[TXT]   sco.css 22-May-2011 14:59   4.0K
[TXT]   skin.css22-May-2011 14:59   84K 
[IMG]   split-button-arrow-active.png   22-May-2011 14:59   280 
[IMG]   split-button-arrow-disabled.png 22-May-2011 14:59   185 
[IMG]   split-button-arrow-focus.png22-May-2011 14:59   185 
[IMG]   split-button-arrow-hover.png22-May-2011 14:59   185 
[IMG]   split-button-arrow.png  22-May-2011 14:59   185 
[IMG]   sprite.png  22-May-2011 14:59   3.0K

(The en folder in the demo on mykoha.co.nz is identical to the folder above:
http://demo.mykoha.co.nz/opac-tmpl/prog/en/css/ )

http://esme.priv.bibkat.no/opac-tmpl/prog/nb-NO/css/
[TXT]   colors.css  22-May-2011 08:34   0   
[TXT]   hierarchy.css   22-May-2011 08:34   1.5K
[TXT]   opac.css22-May-2011 08:34   34K 
[TXT]   print.css   22-May-2011 08:34   3.1K
[TXT]   sanop.css   22-May-2011 08:34   28K 
[TXT]   sco.css 22-May-2011 08:34   4.0K

The contents of the lib/yui directory are also different on a regular
dev install:
http://sksk.bibkat.no/opac-tmpl/prog/en/lib/yui/ (5 CSS files, 3
directories, 1 PNG)
and a packaged install:
http://esme.priv.bibkat.no/opac-tmpl/prog/en/lib/yui/ (lots of
directories, no CSS, no PNG)
http://demo.mykoha.co.nz/opac-tmpl/prog/en/lib/yui/

On a non-package (dev) install the contents of the corresponding
folders are the same for en and nb-NO - and they are the same as the 6
files listed for nb-NO above.
http://sksk.bibkat.no/opac-tmpl/prog/en/css/
http://sksk.bibkat.no/opac-tmpl/prog/nb-NO/css/

On a working non-package (dev) installation the files are taken from
the en folder, where they are indeed to be found:
http://sksk.bibkat.no/opac-tmpl/prog/en/lib/yui/
http://sksk.bibkat.no/opac-tmpl/prog/nb-NO/lib/yui/

On the virtual machine where I built the package, the contents of the
two css-directories are also the same, and they are the 6 files listed
for nb-NO above.

Looks to me like the packaging/packages is doing some rearranging of
the CSS files that only works for the English templates and not for
templates translated into other languages? Are there any package gurus
out there who are able to see what is going on?

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Why is Dewey in the su index?

[Magnus Enger]

On 29 April 2011 16:48, Galen Charlton gmcha...@gmail.com wrote:
 What's in one of the records that are being retrieved?  Do any of the
 subject field (e.g., the 690) contain a copy of the Dewey number?

That's exactly it! The records that were returned when searching for
the Dewey-number had them in the 600 fields. Thanks for changing my
perspective and saving me from a sleepless night!

And of course uncommenting
#Dewey-classification 1=13
in etc/zebradb/ccl.properties made it possible to use that as an index.

 Or
 alternatively, do any of the authorized subject headings contain a $9
 with 355 in the link to the authority record?

No authorities involved!

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Generating transactions

[Magnus Enger]

On 9 April 2011 09:55, Magnus Enger mag...@enger.priv.no wrote:
 On 7 April 2011 22:56, Chris Cormack ch...@bigballofwax.co.nz wrote:
 As far as I know such a
 script does not exist. I would offer to write one, as it sounds like
 fun, but I am in the middle of release management work. I am sure
 however that one of the other developers could do this.

 I thought it sounded like fun too, so I have started to work on one
 during the trip to and from Marseille. It's not finished yet, but I
 hope to get a long, good wait for the last plane home to Bodø, and I
 will let you know when it can be tested.

Here is a basic version of the script for generating patrons:
https://github.com/MagnusEnger/LibrioTools/blob/master/sim/patrons.pl
See here for some context:
https://github.com/MagnusEnger/LibrioTools/tree/master/sim

I'm sort of stuck on the script for the actual transactions, though:
https://github.com/MagnusEnger/LibrioTools/blob/master/sim/circ.pl
The call to C4::Circulation::AddIssue() results in this error:

Can't use an undefined value as a HASH reference at
/home/magnus/scripts/kohanor32/C4/Circulation.pm line 1048.

Line 1048 and it's surroundings in Circulation.pm looks like this:
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Circulation.pm;h=b977524b3f871477d2d18f5a8ba4150853ae68f0;hb=HEAD#l1048

1042 unless ($datedue) {
1043 my $itype = (
C4::Context-preference('item-level_itypes') ) ? $biblio-{'itype'} :
$biblio-{'itemtype'};
1044 $datedue = CalcDateDue( C4::Dates-new( $issuedate,
'iso' ), $itype, $branch, $borrower );
1045
1046 }
1047 $sth-execute(
1048 $borrower-{'borrowernumber'},  # borrowernumber
1049 $item-{'itemnumber'},  # itemnumber
1050 $issuedate, # issuedate
1051 $datedue-output('iso'),# date_due
1052 C4::Context-userenv-{'branch'}# branchcode
1053 );

When i introduce a die Dumper $borrower; after line 1046 i get what
looks like a perfectly accpetable representation of a borrower, and I
can't for the life of me understand why it should be undefined two
lines further down.

If anyone with a keener eye than mine should find this to be an
interesting challenge I'm all ears... ;-)

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Hacker's corner, wk14 / Hackfest Europe

[Magnus Enger]

On 8 April 2011 18:22, Paul Poulain paul.poul...@biblibre.com wrote:
 Just a special thanks to Magnus, that came from Norway, and to Katrin,
 that came from Germany. We should send some picture we've taken very soon !

Just a special thanks to BibLibre for organizing and hosting the
hackfest in the best way possible! Being the only Koha hacker in
Scandinavia, getting to spend some time with people with similar
interests every now and then is just great! Maybe we could make a
European hackfest a yearly tradition?

Best regards,
Magnus Enger
libriotech.no
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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-devel] Hacker's corner, wk14 / Hackfest Europe

[Magnus Enger]

On 11 April 2011 13:14, Chris Cormack ch...@bigballofwax.co.nz wrote:
 On 11 April 2011 23:12, Magnus Enger mag...@enger.priv.no wrote:
 On 8 April 2011 18:22, Paul Poulain paul.poul...@biblibre.com wrote:
 Just a special thanks to Magnus, that came from Norway, and to Katrin,
 that came from Germany. We should send some picture we've taken very soon !

 Just a special thanks to BibLibre for organizing and hosting the
 hackfest in the best way possible! Being the only Koha hacker in
 Scandinavia, getting to spend some time with people with similar
 interests every now and then is just great! Maybe we could make a
 European hackfest a yearly tradition?

 How about 6 monthly  ... a month ahead of each release :)

That would be absolutely fine by me, it's just that I'm afraid I would
not be able to travel to 2 hackfests and 1 KohaCon every year... ;-)

Best regards,
Magnus
___
Koha-devel mailing list
Koha-devel@lists.koha-community.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/