[Koha] REMINDER: General IRC meeting 2 May 2024

[Paul Derscheid]

Hi all,
 
We have a General IRC/Jitsi meeting scheduled for Thursday:
https://wiki.koha-community.org/wiki/General_IRC_meeting_2_May_2024
 
Time converter:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+General+IRC+Meeting=20240502T1300
 
<https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting=20240403T1200>

Please feel free to add any topics you’d like to discuss to the agenda or let 
me know and I am happy to add them for you.
 
See you there!
 
Paul
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hackfest registrations open !

[Paul Poulain]

Hello koha developers !

I'm very happy to open the registrations for the Marseille Koha hackfest.
Some information:

 * *date* : April 8th > April 12th
 * *location*: BibLibre office, 23 rue Fauchier, 13002 Marseille *[NEW
   ADDRESS]*
 * *what is the cost* ? 0€ (I let you calculate in your own currency ;) )
 * who can come: anyone with a laptop
 o librarian who want to contribute to Koha: test new version, test
   new features, document, translate, ...
 o developers who want to contribute to Koha: test technical
   patches, write unit tests, work on package, unit test,
   Elasticsearch, ERM module, LRMisation of Koha, or anything else ;)
 * can I come just for a part of the week ? Yes, but coming at least 3
   days seems needed
 * coffee, tea, and break : provided by BibLibre. Feel free to come
   with candies from your country
 * what about lunch ? BibLibre organize, and ask for 21€ per lunch per
   person (veggie & gluten-free option available).
 * what about the cheese lunch ? On Tuesday :D
 * *How to register* ? Drop me an email

About our new office: it's smaller than the previous one. However, I've 
found an additional location, just on the other side of the street, that 
can welcome 20 more ppl. 25+ ppl fit in BibLibre office, so we'll have 
enough space for everybody wanting to come.


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Internal Server Errors

[Paul]

I recently reported that we'd started to get internal server errors when
looking at ISBD detail and making a hold when in the OPAC.

Jonathan Druart asked if I'd run misc/maintenance/
search_for_data_inconsistencies.pl  to catch potential problems with our
data.

There were numerous errors with respect to home branch and/or holding
branch which I corrected. We've run search_for_data_inconsistencies.pl
again and no problems are reported.

We're still getting internal servers errors when looking at ISBD detail and
making a hold when in the OPAC.

Is there anything  else I can check?

We've also seen that the plack-error.log has a continuously generated error:

DBD::mysql::db selectrow_array failed: Unknown column 'LOST' in 'field
list' [for Statement "SELECT LOST from items where itemnumber = ?"] at
/usr/share/koha/lib/C4/Items.pm line 1229.










-- 
Paul Leman
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Internal server error with ISBD detail and making a hold on OPAC

[Paul]

I’m recently started to get internal server errors when looking at ISBD
detail and making a hold when in the OPAC.

We’re using Koha 19.11.22.000 on Debian 9.

I’ve seen a similar problem reported as bug 22735: Resolve internal server
error on missing item type but that was on 18.05 and presumably fixed back
then.

Can anyone offer any fixes please?

Paul Leman

-- 
Paul Leman
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hackfest in Marseille

[Paul Poulain]

The hackfest will take place in March, 27th - 31th, drop me an 
email if you want to join


Hello ladies and gentlemen,
After 3 years of pandemic where everything was messy, the hackfest in 
Marseille is back ! Join us for 
coding/testing/translating/documenting/dreaming about the future of your 
preferred ILS, in Marseille, 108 rue Breteuil, 13006 Marseille. We'll 
start on monday, March, 27th, and end on Friday, March, 31th.


 * *How to register ?* Just drop me an email !
 * *How much does it cost ?* Nothing. We just ask some fees for the
   lunch [special information: cheese lunch on Tuesday]
 * *What is the agenda ?* there's none, come with your ideas, your
   wish, your goodwill, and we'll do a lot of things in smaller or
   larger groups.
 * *5 days, wow, that's a lot !* yes, but as it's an "un-conference",
   you can come just for a part of the week. I suggest not less than 3
   days, but no obligation here.
 * *I'm not a developer !* That's not a problem. MANY librarians come
   to the hackfest, they meet other librarians, they talk about Koha,
   they help testing, documenting, translating... There's always a lot
   of things to do

Also note: it will be the very last hackfest in our current office, 
we'll move to another office in May (but don't worry, I plan to continue 
hackfesting in your new office)


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Some very sad news.

[Paul Poulain]

Hi Chris,

Sad news, let us know when the funerals are.

@community : May I suggest that we name the next release "Koha 22.11 
Rosalie" ?


Le 17/11/2022 à 08:09, Chris Cormack a écrit :

Tēnā koutou

It is with great sadness that I pass on to you all the news that 
Rosalie Blake has passed away.
Rosalie was the Head Librarian at Horowhenua Library Trust when Koha 
was started and without her Koha would not exist.
But more than this Rosalie was an amazing person, a librarian who 
always thought outside the box, a gifted potter, a friend to many and 
a beloved mother and grandmother.


Details around the funeral and memorial note should be available 
tomorrow. But I am sure you will all join me holding Rosalie's family 
and friends in your thoughts.


Tiwhatiwha te pō, tiwhatiwha te ao.

Chris

___
Koha-devel mailing list
koha-de...@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/


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] NUMBER OF KOHA RECORDS

[Paul Zulu]

Thank you for the information.

On Mon, Jul 18, 2022 at 5:58 PM Alvaro Cornejo 
wrote:

> Hi Paul
>
> Koha does not have a record limit. Limit is determined by your drive space
> and memory size.
>
> Of course, the bigger the DB and the bigger the patrons, the more powerful
> the hardware required.
>
> Regards,
>
> Alvaro
>
> ||
>  Stay safe / Cuídate/  Reste sécurisé
> *7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
> mesure.
>  *q *Recycle always / Recicla siempre / Recyclez toujours
>  P Print only if absolutely necessary / Imprime solo si es necesario /
> Imprimez seulement si nécessaire
>
>
> Le lun. 18 juil. 2022 à 01:11, Paul Zulu  a écrit :
>
>> Dear Koha Community
>>
>> Can anyone assist me by giving the maximum number of records Koha can
>> accommodate? Thank you.
>>
>> --
>> Paul Zulu
>> Sub-Librarian II
>> Mulungushi University Library
>> P.O Box 80415
>> KABWE, ZAMBIA
>> Cell: 0977875006
>> E-mail: plzul...@gmail.com
>> ___
>>
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>

-- 
Paul Zulu
Sub-Librarian II
Mulungushi University Library
P.O Box 80415
KABWE, ZAMBIA
Cell: 0977875006
E-mail: plzul...@gmail.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] NUMBER OF KOHA RECORDS

[Paul Zulu]

Dear Koha Community

Can anyone assist me by giving the maximum number of records Koha can
accommodate? Thank you.

-- 
Paul Zulu
Sub-Librarian II
Mulungushi University Library
P.O Box 80415
KABWE, ZAMBIA
Cell: 0977875006
E-mail: plzul...@gmail.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] hackfest registration

[Paul Poulain]

Hello koha fans,

A quick reminder: drop me an email if you plan to come to the hackfest, 
that will be in March, 23-27, in France, Marseille.


Currently, we've people from : Argentina, Canada, Finland, France, 
Germany, Ireland, Spain, UK, USA.


Your country and your contribution is missing !!!

As usual, it will be a week of useful work, with a lot of documenting, 
testing, coding, talking, thinking. And a little bit of eating (cheese) 
and drinking ( -not only- beer, after work of course)


Welcome

--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] hackfest 2020 in Marseille, registrations are open !

[Paul Poulain]

Hello everyone,

almost everything is in the title : you can register for the hackfest by 
sending me an email.


As announced previously, it will take place in BibLibre office, 
Marseille, France, March 23-27


Some explanations for those who need them:

 * the hackfest is NOT a developer week. it's a week for anyone willing
   to contribute to Koha, whatever the kind of contribution (testing,
   documenting, ...)
 * the hackfest is free of charge (but you'll have to deal with your
   traveling costs, of course)
 * you can come for 5 days, or less. Don't come for 1 day, it's
   useless. coming for 2 days is very frustrating. Coming for 3 to 5
   days is perfect !
 * 40-45 ppl fit in our office. If we're more than this, we'll have to
   book an additional room [thanks to the company just next door] So
   register as soon as possible
 * there's no schedule, everyone comes with it's own
   ideas/goals/expectations
 * that's not a training session
 * if you need an official invitation, just ask by email

Hoping to see you next month !!!

--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] From docs list: Deprecated script used (koha-start-sip)

[Paul Hoffman]

On Wed, Sep 11, 2019 at 05:47:20AM +1200, David Nind wrote:
> (This is a bounced messaged sent the docs list - posting to the general
> list)
> 
> Hi team,
> 
> Installed 19.05 version of koha and got the subjected error when try
> starting sip. Koha is got started by using koha-sip  but not able
> to stop or restart sip services. Please help
> 
> root@koha:/home/koha# koha-start-sip library
> Deprecated script used (koha-start-sip)

Are you sure that your SIP server isn't running?  You should be able to 
tell by running these commands:

source /usr/share/koha/bin/koha-functions.sh
if is_sip_running $instance; then
echo SIP is running
else
    echo SIP is not running
fi

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha/Zebra record lengths

[Paul A]

We've lost a record (opac and staff) biblio + 422 items. It's there in 
all its glory in MySQL, but Zebra won't show it. The Koha wiki mentions:


"Record length of 101459 is larger than the MARC spec allows (9 
bytes) -- This will show up if you are trying to index a record that has 
a large number of items (common with serials, for example), or just has 
a lot of text in the record itself. /.../ Koha can do the indexing by 
using the MARCXML format rather than ISO 2709, and this gets around the 
problem. If you add '-x' to the reindex_zebra.pl command when indexing 
biblios, it will do this"


We always have used '-x' for biblios (did it again a couple of minutes 
ago.) No joy


I can (I hope!) just delete the last item (or two or three) from MySQL 
and reindex, but before I go there, does anyone have previous experience 
with this problem?


Many thanks --Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Koha-devel] Hackfest 2019, registration open !!!

[Paul Poulain]

A reminder of the hackfest dates & registration open. Drop me an email 
if you plan to join us !


Le 09/07/2019 à 10:27, Paul Poulain a écrit :


Hello,

Once again, BibLibre is happy to invite Koha users and developers for 
a week of fun, working on Koha for improving it's quality !


*Dates* : September 30th - October 4th. Anyone is welcomed any day: 
it's not required to come the whole week. But a minimum of 2 
consecutive day is needed to be able to do something useful


*Location*: 108 rue Breteuil, F-13006 Marseille

*Who is invited* : anyone willing to contribute to Koha, you don't 
need to be a developer to join us ! There is a lot of useful things a 
librarian can do much better than a developer, like testing, documenting.


*How to register* : drop me an email

*How much does it cost* : nothing (you'll have to deal with your 
traveling fees though, and we organize the lunch, with a fee of 15-17€ 
per day)


*Last but not least* => come with your swimsuit, the sea is usually 
welcoming in September/early October :D


--
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-de...@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/


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Update jquery

[Paul A]

On 2019-07-27 9:04 p.m., Owen Leonard wrote:

install jquery v1.7. How can I upgrade to the latest stable version of
jquery?


I would like to hear more details about why you want to upgrade
jQuery. I'm not aware of a reason to do so just for the sake of having
the latest version.


[probably off-topic for many readers]

Jumping in from a philosophically technical (or technically 
philosophical) perspective: maybe there are other organizations that run 
more than one website | database | application?  We do -- in house, not 
"in a cloud", and a couple of years ago we invested in additional 
servers for this type of problem.


Note that I do not remember jquery as being necessarily problematic, but 
various flavours of o/s, kernel, perl, apache (and its setup and 
dependencies), html, mysql, python, letsencrypt, maybe more... made it 
more straightforward and saved my sanity from an IT perspective


We invested in a front-end server running nginx to distribute to two 
"main" servers (Koha, all the rest) and two backups (Koha, all the 
rest.)  It works totally reliably, but we went from two servers ("all" 
plus "backup") to five. Plus the sandboxes.


Every springtime we "sandbox" the latest version of Koha, and while we 
always get it to function, we have never (yet!) found an easy solution 
to exactly this type of production capability | service and dependency 
version compatibility.


Quite frankly, I haven't touched our production Koha in years -- it's 
fast and rock-solid; we love it. But at 3.8.24 probably way out of date 
for a "lending" library (which we are not) but brilliant for cataloguing.


Bottom line: it's a bit of an IT challenge to maintain and/or upgrade a 
server environment plus Koha plus other usages, from a soft- and 
hardware perspective. I run a charity and from a budgetary p.o.v. found 
it easier to dedicate additional hardware, at a static software level, 
to the production Koha that we rely upon.


Please note: this is *not* a recommendation, only one organization's 
perspective...


Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hackfest 2019, registration open !!!

[Paul Poulain]

Hello,

Once again, BibLibre is happy to invite Koha users and developers for a 
week of fun, working on Koha for improving it's quality !


*Dates* : September 30th - October 4th. Anyone is welcomed any day: it's 
not required to come the whole week. But a minimum of 2 consecutive day 
is needed to be able to do something useful


*Location*: 108 rue Breteuil, F-13006 Marseille

*Who is invited* : anyone willing to contribute to Koha, you don't need 
to be a developer to join us ! There is a lot of useful things a 
librarian can do much better than a developer, like testing, documenting.


*How to register* : drop me an email

*How much does it cost* : nothing (you'll have to deal with your 
traveling fees though, and we organize the lunch, with a fee of 15-17€ 
per day)


*Last but not least* => come with your swimsuit, the sea is usually 
welcoming in September/early October :D


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Koha-devel] Extracting Frequency of a Serial From metadata

[Paul Hoffman]

Each string produced by Pasi's query -- and, if I'm interpreting it 
correctly, by your original query -- is the complete contents of 
subfield $a in a 310 field.  According to the MARC21 standard, this is a 
free-text subfield -- it does not (commonly) contain coded (or even 
readily parseable) information.

Here is the Library of Congress's brief description of that subfield:

$a - Current publication frequency
Complete statement, exclusive of dates, of the current publication frequency.

And here are some examples of its contents:

310 ##$aMonthly
310 ##$aMonthly, including annual cumulation
310 ##$aBimonthly (monthly June-July)
310 ##$aContinuously updated 

See http://www.loc.gov/marc/bibliographic/bd310.html for further 
details.

I hope this helps.

Paul.

On Tue, Jul 02, 2019 at 02:35:40PM +0530, RAGHAV ARORA wrote:
> Sir,
> 
> Even this query gives certain ambiguous values like 'SM', 'BM', 'Q', etc.
> What do these values mean?
> 
> Thanks in advance
> Regards
> *Raghav Arora*
> Sophomore, M.Sc (Hons) Chemistry BE Electrical and Electronics Engineering
> Contact : (+91) 9897597761, 8474975691
> Personal Email  | University Email
> 
> LinkedIn <https://www.linkedin.com/in/raghav-arora-9820a648/> |  GitHub
> <https://github.com/RAraghavarora/>
> 
> ▄
> *Birla Institute of Technology and Science, Pilani*
> Pilani campus,
> Rajasthan-333031
> 
> 
> On Tue, Jul 2, 2019 at 9:28 AM RAGHAV ARORA <
> f20171...@pilani.bits-pilani.ac.in> wrote:
> 
> > Thank you sir,
> > I will try this out and let you know.
> >
> > Regards
> > *Raghav Arora*
> > Sophomore, M.Sc (Hons) Chemistry BE Electrical and Electronics Engineering
> > Contact : (+91) 9897597761
> > Personal Email  | University Email
> > 
> > LinkedIn <https://www.linkedin.com/in/raghav-arora-9820a648/> |  GitHub
> > <https://github.com/RAraghavarora/>
> >
> > ▄
> > *Birla Institute of Technology and Science, Pilani*
> > Pilani campus,
> > Rajasthan-333031
> >
> >
> > On Mon, Jul 1, 2019 at 4:53 PM Pasi Kallinen 
> > wrote:
> >
> >>
> >> Those locates really made it look too complex. I'd rather use
> >> ExtractValue to get the MARC field values, perhaps something along these
> >> lines:
> >>
> >> select ExtractValue(metadata,
> >> '//datafield[@tag="310"]/subfield[@code="a"]') as frequency from
> >> biblio_metadata where ExtractValue(metadata,
> >> 'count(//datafield[@tag="310"]/subfield[@code="a"])') > 0;
> >>
> >>
> >> --
> >> Pasi Kallinen
> >> Koha-Suomi oy
> >> +358 400 174 235
> >>
> >>
> >>
> >> Jul 1, 2019, 1:26 PM by f20171...@pilani.bits-pilani.ac.in:
> >>
> >> > Hello everyone,
> >> > The SQL query to get the frequency for different serials was given on
> >> the KOHA SQL Library as :
> >> >SELECT
> >> > IF
> >> > (   LOCATE(' >> biblio_metadata.metadata) = 0
> >> > OR
> >> > LOCATE('',
> >> biblio_metadata.metadata, LOCATE(' >> biblio_metadata.metadata)) = 0
> >> > OR
> >> > LOCATE('',
> >> biblio_metadata.metadata, LOCATE(' >> biblio_metadata.metadata))
> >> > > LOCATE('',
> >> biblio_metadata.metadata, LOCATE(' >> biblio_metadata.metadata)),
> >> > '',
> >> > SUBSTRING( biblio_metadata.metadata,
> >> > LOCATE('',
> >> biblio_metadata.metadata, LOCATE(' >> biblio_metadata.metadata)) + 19,
> >> > LOCATE('',
> >> biblio_metadata.metadata, LOCATE('',
> >> biblio_metadata.metadata,
> >> > LOCATE(' >> biblio_metadata.metadata)) + 19)
> >> > -
> >> > (LOCATE(' >> code="a">',biblio_metadata.metadata, LOCATE(' >> biblio_metadata.metadata)) + 19)
> >> > )
> >> > )
> >> > AS FREQUENCY
> >> >
> >> > When I run this query, it gives 

Re: [Koha] Circulation rule by location

[Paul A]

On 2019-06-26 4:33 p.m., Coehoorn, Joel wrote:

This seems like a major weakness.


Maybe more a "special case" rather than "major weakness" ... so ...


For just one example that is likely common, let's a book, or older issues
of a periodical move from the normal part of the library to an "Archives"
location that is more dense, and maybe climate controlled for preservation.


Maybe it's "common" -- we certainly deal with exactly this type of 
situation, and use MARC21 952$7 (somewhat successfully for us, maybe not 
exactly your challenge?)


However, if that doesn't meet your needs, and as Katrin said: "library 
... item types only. Locations cannot be used" So there are a couple of 
potential solutions:


- You could have a "library" -- you might want to call 
"climate_controlled_holdings" (we call it "rare book room") where the 
rules can be a tad different


- "item types" could be an option. When you transfer a periodical 
to your new holding area, just call it a "protected periodical" instead 
of "periodical" at the same time as giving it a new location code/name.


Best -- Paul


The circulation rules for those items might be different, but the type of
the item hasn't changed, only the location.

Is there a feature request I can vote for or bugzilla # I can track to
watch for this?

Joel Coehoorn
Director of Information Technology
402.363.5603
*jcoeho...@york.edu *

*Please contact helpd...@york.edu  for technical
assistance.*


The mission of York College is to transform lives through
Christ-centered education and to equip students for lifelong service to
God, family, and society


On Wed, Jun 26, 2019 at 3:22 PM Katrin Fischer 
wrote:


Hi Joel,

at the moment circulation conditions can be tied to combinations of
library, patron category and item types only. Locations cannot be used.

Katrin

On 26.06.19 21:39, Coehoorn, Joel wrote:

Is it possible to have a circulation rule that targets location? In the
past, we've had a diarrhea of item types to encode both a location and

the

kind of item, and this really isn't ideal. We'd like to revise our
circulation rules to target locations, and therefore simplify our item
types.

Joel Coehoorn

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Need advice regarding removal of deleted biblio records

[Paul A]

On 2019-06-25 4:43 p.m., Andy Boze wrote:

Dear all,

I'm hoping someone can give me a bit of direction. We have a large 
number of deleted biblio records (due to a failed MARC records import). 
We'd like to remove the deleted records from the database as there are 
somewhat more deleted records (401,000) than active records.


Why not go back to your previous backup? Quick, simple, painless.

Best -- Paul


Is there a script than can clean up deleted records? I've seen this 
"Clean up database" script < 
https://koha-community.org/manual/18.11/en/html/cron_jobs.html#clean-up-database 
 >, but it's not what we're looking for.


If there's no script, can we safely use the MySQL TRUNCATE command on 
the deletedbiblio, deletedbiblio_metadata, deletedbiblioitems and 
deleteditems tables? This is a non-circulating library, so I don't think 
the biblionumber would be tied to any other tables.


I'll appreciate any guidance. We're using Koha 18.11 and MariaDB 5.5.60.



___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha backup vs -SQL backup

[Paul A]

On 2019-06-20 11:34 a.m., Indranil Das Gupta wrote:

On Thu 20 Jun, 2019, 8:13 PM Yatheesh lis,  wrote:

Hi
1) what is deferencece B/w Koha backup vs -SQL backup.

None. It's the same MySQL database if you are talking about the database
backup generated by koha-run-backups script. 


Respectfully, this could be misinterpreted. "-SQL" pure backup is done via:
	mysqldump --user=your_kohadb_username --password=whatever your 
koha_db_name > /wherever/backup/koha_dump_whatever


Note that this is best done using the "Koha" owner (not root) and is 
agnostic as to whether you use Innodb or Isam as storage engine. I 
haven't kept perfect track of all shell commands as 'koha-run-backups 
script', but they were designed to do more or less exactly that, but 
with a (default 2 day) over-write as a cron job.



However, the defaults used may
be different, for example whether syntaxes like "CREATE IF NOT EXIST" are
incorporated OR not in the backup etc.


This has nothing whatsoever to do with "backup" but with "restore" -- it 
is a function of the opposite mysqldump < (rather than >) and is only 
[potentially] relevant to *overwrite* a previous, differently 
constructed and protected, database.


2) I have taken backup through koha and imported other system but it shows

only biblio records with out any item details why?


Does your "backup through [k]Koha" show your items? In other words, did 
you have an existing library, with biblios and items, that you can 
restore?  Or, is it only your "imported other system" that fails (or 
even breaks your old, possibly inexistent library)?


Regards -- Paul




Most likely case, that somehow the branchcode (s) defined are different
from the backup.

In case you are talking about *MARC* backup rather than a full db backup,
then either (a) your branchcodes are not same between the instances OR (b)
you have only exported the bibs and *not* the items.


3) to import -SQL backup should I know database name?




Yes.

Cheers

Indranil Das Gupta
L2C2 Technologies
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Error message shown during web installation

[Paul A]

On 2019-06-14 10:07 a.m., Indranil Baruah wrote:

Following error is shown during web installation of Koha 19.05 on Lubuntu
19.04. The installation however completes but the speed of the application
is slow even with Memcached running.


Happy to see you have Koha running. As to speed, here are a few thoughts 
based on many years of Koha (but not specifically 19.05) experience:


	- you mention Lubuntu, which might be a desktop (GUI) implementation. A 
_server_ implementation would probably be more suitable -- ubuntu, 
debian are good choices. Desktops have overheads that use resources 
unnecessary for Koha.


	- you mention memcached. How much memory have you allocated? look in 
your /etc/memcached.conf and increase "-m" from the default 64 to 4096 
(or at least 2048.)


	- you do not mention the hardware that you are using. We have found 
that, as long as you have at least 16 Mbs RAM, the CPU's L2 and L3 cache 
across a large number of cores is the most determining factor. To give 
you an example, on an old box with (inxi reporting) "Quad core Intel 
Core i7-2600 (-HT-MCP-) cache: 8192 KB" needs approx 1.21 secs for a 
Zebra search, whereas a dual motherboard "6 core Intel Core i7-8700K 
(-MT-MCP-) cache: 12288 KB" (i.e. 12 core, with overlapping 2 x 12288 KB 
CPU cache) does exactly the same job in 0.048 seconds. (This for a 
240,000 item db.)


The bottom line is that Koha is a very "big" application, that does an 
awful lot of things for an awful lot of varying libraries and end users. 
The sheer size and complexity of all the improvements that have been 
integrated over the years has inevitably led to to either "hardware 
upgrades" or as you write "the application is slow."


There might well be other reasons that you have found your installation 
to be "slow." Perhaps you would be kind enough to let us know how you 
did your installation (package? tarball?) and the size of your database 
(number of biblios and items?), any log entries that could assist, and 
some idea of your hardware. There are many helpful and knowledgeable 
people on this list who, in my experience, would be most enthusiastic to 
try and help you.


Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [EXTERNAL] batching imported records viaz39.50

[Dr Paul Adamthwaite]

On 2019-05-31 12:02 p.m., Hernandez, Heather wrote:
[snip]

You need to pay for a full cataloging subscription to OCLC to use it even
via Z39.50, 

[snip]

A couple of weeks ago, Library and Archives Canada turned off their 
Z39-50 service AMICUS which we have been using via Koha for many years. 
They have written to us -- CaOPIACS, which they issued -- that, as 
Heather says above, we have to pay for "a full cataloging subscription 
to OCLC". The quote from OCLC is several thousands of dollars. As a 
Canadian charity we are adversely impacted [1].


Might I prevail upon all Koha users (and potential users) on this list 
to let me know:

- if they used to use AMICUS Z39-50 for Canadian titles
- if they are commercial subscribers to OCLC
	- if they have feelings/comments about a national library outsourcing 
to a foreign commercial corporation


List replies would be appreciated, as Z39-50 is one of Koha's strengths. 
Off-list replies to paul.a at navalmarinearchive.com would, gratefully, 
be held in confidence.


With my sincerest thanks,
Paul
---
Paul Adamthwaite, Ph.D.
Executive Director
Naval Marine Archive : The Canadian Collection
Canadian Charitable Organization 88721 9921 RR0001

[1] This affects the speed and accuracy of our [mostly volunteer] biblio 
cataloguing of Canadian titles (although LoC, via their "copycat" 
service are sometimes of great help.) It also puts our Koha catalog 
potentially "out of sync" with our national authority; ~20% of our 
holdings are of Canadian publishing origins.



___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Plugin Error

[Paul A]

On 2019-05-22 7:54 a.m., Jon Knight wrote:

Have you checked if you have SELinux enabled?  That sometimes causes issues 
with being able to write to temporary directories from Apache derived 
processes, write to network sockets from CGI scripts, etc.


A little off topic, but Satish mentions an Ubuntu variant. Please note 
that SELinux is not necessarily recommended in Ubuntu (apparmor is the 
default security, which should be removed and purged before installing 
SELinux as they conflict.)  SELinux was developed for Centos and RHEL, 
and while it is more "fine-grained" that makes it more challenging to 
configure (we played with it on a dev 18.04 server a little while ago.)


If you have apparmor installed try:

sudo aa-status

which will show in broad-brush terms what is being enforced (if it is 
running, which it should be.)


Paul> 

From: Koha  on behalf of SATISH 

Sent: 21 May 2019 08:29:27
To: Koha
Subject: Re: [Koha] Plugin Error

Hi,

With Lubuntu 16.04 LTS + Koha 18.11.05 + MySQL + Installation by Package
Method

Still I am not able to upload plugins to Koha

Throws the same error:
*--*

*Cannot unpack file to the plugins directory.Please verify that the Apache
user can write to the plugins directory.*
--
I tried permission with all possible names suggested in the reply ( like,
www-data, koha-instance, root) , but no success.

Can you please help me get this fixed?

With thanks.
Satish MV
Librarian
Govt. Engineering College, Hassan
Karnataka
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] New added items and biblio records not searchable on two-tier setup

[Paul A]

On 2019-05-02 12:37 p.m., Admire Mutsikiwa wrote:

Hi
On the database server, I did not have zebra. My database server is a 
bare metal installation on operating system and  MySQL and has no zebra 
instance running on it. Thought the zebra should be running on the Koha 
application server.


You do say that you modded "koha-conf.xml to the IP address of the 
database server and granting the relevant privileges" and it sounds as 
though new db entries are being written.


Perhaps it doesn't matter where Zebra is running (your setup, your 
choice), but it still sounds as though Zebra, through the 
"rebuild-zebra" script with the -z option (cron job, incremental / 
process_zebraqueue) is not fully functional. Have you changed the env 
vars to tell it where the db is located? Have you got any logged error 
entries? Can you do a full re-index? What happens, any errors?, when you 
run ./rebuild_zebra.pl -a -b -z -v &> /dev/null




P.


Regards,

Admire

On Thu, May 2, 2019 at 6:27 PM Paul A <mailto:pau...@navalmarinearchive.com>> wrote:


On 2019-05-02 12:15 p.m., Admire Mutsikiwa wrote:
 > Hi  All
 >
 > I am running an instance of Koha  18.11.03.000 on Debian 8.11
where both
 > the application server and the Koha database where running on one
server.
 > My server was becoming overwhelmed so I decided to have a
two-tier setup
 > with the database running on another separate server  by changing the
 > localhost/etc/koha/sites/library/koha-conf.xml to

 > the IP address of the database server and granting the relevant
privileges.
 > Everything seems to be going on well.  However, newly added items and
 > biblio records are not searchable on the catalogue pointing to a
browse
 > index-related issue. What should I do on a two-tier setup to
ensure that
 > newly added items are added to the browse index and  are
searchable? Any
 > pointers are most welcome.

Have you set up the cron job on the db server to update Zebra?

Best -- Paul
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha



___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] New added items and biblio records not searchable on two-tier setup

[Paul A]

On 2019-05-02 12:15 p.m., Admire Mutsikiwa wrote:

Hi  All

I am running an instance of Koha  18.11.03.000 on Debian 8.11 where both
the application server and the Koha database where running on one server.
My server was becoming overwhelmed so I decided to have a two-tier setup
with the database running on another separate server  by changing the
localhost

Have you set up the cron job on the db server to update Zebra?

Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Creating a Report to List Books published with a Date Range

[Paul A]

On 2019-04-29 6:44 a.m., Njideaka Tobechukwu wrote:

Hi All,

Please, I am trying to create a report of my KOHA database to list books
published within 2016-2019, in a tabular form having just the book title,
author, and date of publication.  However, I do not know how to go about
creating this report.


SELECT b.title, b.author, b.copyrightdate
FROM biblio b
WHERE b.copyrightdate BETWEEN '2016' AND '2019';

Note: this simplistically relies on "copyrightdate" 260$c, which Koha 
defines as "publication or copyright date from the MARC record".


Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] ELAG 2019

[Paul Poulain]

Hello,

This year, ELAG is in Berlin, Germany, and BibLibre is sponsoring, so 
I'll be here, and happy to see at BibLibre booth anyone attending ELAG ! 
See https://www.elag2019.de/


I also have been selected for a bootcamp about Urungi to build 
statistics & dashboards : https://www.elag2019.de/bootcamps.html#urungi


Regards

--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Problem uploading patrons

[Paul Hoffman]

On Tue, Apr 02, 2019 at 11:36:36AM -0700, Elaine Bradtke wrote:
> It has taken a while to figure out what caused the patron import to fail.
> The CSV file that failed has returns between each patron instead of new
> line.   Koha doesn't parse returns as new lines and so the file kept
> failing.
> Unfortunately, the software that we get the data from exports it with
> returns instead of new lines, and there's not a way to fix it on their end.
> I'd like to find a way to convert the returns to new lines so that the
> assistant librarian can do the uploads without my intervention. Excel
> doesn't seem to do the trick, unless there's a secret setting somewhere (if
> you know, do tell!).  Does Open Office work better?

In Linux or UNIX, this command will do the trick:

perl -i -p -e 'tr/\x0d/\x0a/' FILE

(Option -i means "change the file in place"; _perldoc perlrun_ can help 
you understand the other options.)

To do the same but keeping a backup with extension .bak:

perl -i.bak -p -e 'tr/\x0d/\x0a/' FILE

To copy from FILE1 to FILE2, changing CR to LF:

perl -p -e 'tr/\x0d/\x0a/' < FILE1 > FILE2

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Koha-devel] New OPAC design

[Paul Poulain]

You can thank Fridolin for this great work, my skills in terms of design 
are far lower than what he's able to do !


Le 01/04/2019 à 14:08, Pedro Amorim a écrit :

Looks great, Paul!

I would've gone for a Pokémon theme myself but My Sweet Pony also 
works! xD



On Mon, 1 Apr 2019 at 11:56, Paul Poulain <mailto:paul.poul...@biblibre.com>> wrote:


Kia ora, hoping you're all enjoying the new month starting,

We (BibLibre) think that the default OPAC layout is not adapted to
the
youngest audience. That's why we've decided to create a new design
for
the OPAC, that will be soon submitted for inclusion in Koha 19.05. We
really hope you'll enjoy this new design.

We have set it on our demo instance, you can have a look here :
https://demo.biblibre.com/

PS: our customers will have this design automatically set during the
next update.


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] New OPAC design

[Paul Poulain]

Kia ora, hoping you're all enjoying the new month starting,

We (BibLibre) think that the default OPAC layout is not adapted to the 
youngest audience. That's why we've decided to create a new design for 
the OPAC, that will be soon submitted for inclusion in Koha 19.05. We 
really hope you'll enjoy this new design.


We have set it on our demo instance, you can have a look here : 
https://demo.biblibre.com/


PS: our customers will have this design automatically set during the 
next update.


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] bug sip2 koha 18.05

[Paul Hoffman]

On Mon, Mar 25, 2019 at 02:05:02PM +, Ahmed Samir wrote:
> i configure sip2 by
> https://wiki.koha-community.org/wiki/Koha_SIP2_server_setup
> when test sip2 server
> ./bin/sip_cli_emulator.pl -a localhost -su user -sp pass -l LIB -patron 111 
> -m patron_information
> error message
> Attempting socket connection to localhost:6001...connected!
> SEND: 9300CNuser|COpass|CPLIB|
> READ: HTTP/1.1 400 Bad Request
> 
> Login Failed!

It looks as though you sent the user name "user" and the password 
"pass".  If so, that would explain why the SIP login attempt failed.  
What happens if you use real user credentials?  (Don't show them to us, 
just tell us if they work!)

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to receive reports to email

[Paul Hoffman]

On Thu, Feb 14, 2019 at 12:30:59PM +0530, SATISH wrote:
> I need to keep print copy of daily transactions (cumulative) report for
> check-out & check-in transactions that is from library
> opening hours to closing hours every day. Currently I am running sql for
> date range for check-in & check-out.
> 
> [...]
> 
> But, I am looking for using same sql report automatically through an email
> on every day basis.

Here's one way to do it.  Start with a file that contains the SQL for 
the report, preceded by a suitable e-mail header:

- /path/to/your/reports/foobar -
From: some.email.addr...@example.com
To: some.other.email.addr...@example.com, etc.etc@example.com
Subject: The report you asked for
Content-Type: text/plain

SELECT ...
FROM   ...
WHERE  ...


Then write a Perl script that runs the report and sends the results in
tab-delimited format:

--- /path/to/run-reports.pl 
#!/usr/bin/perl

use strict;
use warnings;

use C4::Context;

my $dbh = connect_to_database();

# Expand file globs
if (@ARGV == 1 && $ARGV[0] =~ /[*]/) {
@ARGV = glob(@ARGV);
}
die "No reports to run" if !@ARGV;

# Run report(s)
foreach my $file (@ARGV) {
open STDIN, '<', $file
or die "Can't open $file: $!";
my $header = read_header();
my $sql= read_sql();
my $sender = find_sender($header);
my $sth= prepare_sql($sql);
my $fh = start_sendmail($sender);
print $fh $header;
print $fh columns_header($sth);
while (my @row = $sth->fetchrow_array) {
print $fh tab_delimited(@row);
}
close $fh or die "Close sendmail handle: $!";
close STDIN;
}

# Functions

sub connect_to_database {
my $dbh = C4::Context->dbh;
$dbh->{RaiseError} = 1;
return $dbh;
}

sub find_sendmail {
foreach (qw(/sbin/sendmail /usr/sbin/sendmail /bin/sendmail 
/usr/bin/sendmail)) {
return $_ if -x $_;
}
die "Can't find sendmail";
}

sub read_header {
my $header = '';
while (<>) {
$header .= $_;
last if /^\r?$/;
}
return $header;
}

sub find_sender {
my ($header) = @_;
foreach (split /\n/, $header) {
return email($1) if /^From:\s+(.+)/;
}
die "No sender found in e-mail header";
}

sub email {
local $_ = shift;
return $1 if /^([^@\s]+\@[^@\s]+)\b/;
return $1 if /^.+ <([^<>\s]+)>/;
die "Can't find sender e-mail address";
}

sub read_sql {
# Read the SQL
local $/;
my $sql = <>;
return $sql;
}

sub prepare_sql {
my $sql = shift;
my $sth = $dbh->prepare($sql);
$sth->execute(@_);
return $sth;
}

sub start_sendmail {
my ($sender) = @_;
my $sendmail = find_sendmail();
open my $fh, '|-', $sendmail, qw(-oi -oem -t -f), $sender
or die "Can't exec $sendmail: $!";
return $fh;
}

sub columns_header {
my ($sth) = @_;
return join("\t", @{ $sth->{'NAME'} }) . "\n";
}

sub tab_delimited {
return join("\t", map { defined $_ ? $_ : '' } @_) . "\n";
}
--------

Then use koha-shell to run them:

[as root]
# koha-shell YOURINSTANCE -c '/path/to/run-reports.pl /path/to/your/reports/*'

I'll leave the rest to you -- cron, etc.

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] unable to enable e-mail services

[Paul Hoffman]

On Thu, Feb 14, 2019 at 08:28:20AM -0500, Alvaro Cornejo wrote:
> looks like a write permission..
> 
> try sudo touch ...

It's probably a good idea to figure out what the problem is, rather than 
just use sudo to "solve" it.  Can you send us the output of the 
following commands?

id
ls -ld /var /var/lib /var/lib/koha /var/lib/koha/library

That will (hopefully) tell us if you're trying to do this as the wrong 
user, if your permissions are messed up (which would likely cause more 
problems later), etc.

Paul.

> Le jeu. 14 févr. 2019 à 04:39, takan bhatt  a écrit :
> 
> > while enabling email in command line I am getting following errot
> >
> > touch: cannot touch '/var/lib/koha/library/email.enabled': Permission
> > denied
> >
> > pls help me
> >
> > Rajesh

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 2 different circulation rules against a patron

[Paul Hoffman]

On Mon, Jan 07, 2019 at 06:34:54PM -0500, Chee Hong wrote:
> Thanks for your reply and explanation. I agree with you that it will be a
> maintenance nightmare for the upgrade. Personally, I think this is a nice
> to have feature. In order to realize my use case, I need to create 2 patron
> accounts for users who need to have this special privilege.

Unless I'm misunderstanding or have forgotten what you wrote in your 
original post, what you're looking for is a way to enable an interaction 
such as this...


Maria (a graduate student who also works as an adjunct faculty member) 
brings a book to the circulation desk and asks to check it out.

Bob (a circ staff member) scans Maria's barcode, or searches using her 
name.

Koha indicates that there are two options to choose from when performing 
the checkout:

(1) Check it out to Maria as a graduate student.
(2) Check it out to Maria as an adjunct faculty member.

Bob selects the desired option.

(Alternatively, Koha sees that #2 would result in a longer loan period 
and selects that option automatically.)


Furthermore, you would prefer to do this without the added burden of 
having two separate patron records (i.e., two different rows in the 
"borrowers" table) in Koha.

Am I understanding correctly?

If so, it might be useful to think of this at a higher level of 
abstraction.  Here are my ideas...

We keep the two separate records -- each must continue to have a unique 
cardnumber, which may make this idea unusable -- but link them in some 
way.  

Maria is a person with two roles at your institution.  We create a new 
"object" -- a Person -- and reference Maria (the Person) from each 
patron record.

In concrete terms, this might mean:


CREATE TABLE persons (
personnumber INTEGER PRIMARY KEY,
preferred_borrowernumber INTEGER REFERENCES borrowers(borrowernumber);
);
ALTER TABLE borrowers
ADD COLUMN personnumber INTEGER REFERENCES persons(personnumber);


Then (*handwave*) we add an interface for linking borrowers, another for 
selecting the desired borrower from a list of linked borrowers, etc.

It's just a thought...

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
617-989-5032
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Staff and opac doesn't load after starting k

[Paul Hoffman]

On Fri, Dec 21, 2018 at 04:17:04PM +, Indranil Baruah wrote:
> Plack is running. Still no staff of opac. 

(I'm replying to the list, so people can see the full conversation.)

I wonder if Apache is running, is listening on port 80, etc.

I've attached a Perl script you can run to detect which Koha instances 
are running; it runs netstat to see which ports Apache is listening on, 
then looks at all your Koha config files to find the corresponding Koha 
instance(s).

If you're comfortable running the script -- preferably as root -- send 
us the output.  Otherwise, the output of the following commands might 
prove helpful:

koha-list --enabled

netstat -nlpt | fgrep :80

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Staff and opac doesn't load after starting koha-plack

[Paul Hoffman]

On Fri, Dec 21, 2018 at 12:49:31PM +0100, Katrin Fischer wrote:
> maybe Plack is no longer running after your restart - have you tried
> starting it again?

Depending on your OS, one of these two commands should tell you whether 
plack is running:

# systemctl status koha-common

# ps -ef | fgrep plack

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Branches limitations for locations

[Paul Poulain]

IMHO, that's a bug (or a mistake in behavior)

When you create an item, if you create it for homebranch X, you must be 
able to see location defined for branch X. It does not depends on the 
branch you're connected to, it depends on the branch of the item you're 
cataloging. So we should change the behavior.


Additional cases:

 * libraries having a cataloger in every branch ("I catalogate for my
   branch") will see no difference,
 * I can't see a use case where the librarian want to enter "homebranch
   = X" and "location = a location that is not supposed to exist in
   branch X" !

Le 18/12/2018 à 18:35, BOUIS Sonia a écrit :

Hello,
It is possible in Koha to limit the locations to specific branches. This 
limitation is active when adding items and in item search.
Currently, this limitation is linked to the branch where you are logged. But 
this behavior doesn't fit with our organization because with have a centralized 
service to add items for all branches.
I wonder if we could change this behavior to limit the location to the branch 
selected in the home branch or the holding branch (I presume the holding branch 
is more logical?)
Actually, I don't think it would be a big change for people that already use 
this functionality because, if I am not mistaken, when you add a new item, 
you're by default on the branch where you are logged.
For item search, it could be disturbing to be able to choose any branches for 
home branch or holding branch, but only the location from the branch where you 
are logged. We could perhaps change to limit the location the branch that are 
selected in the search form?

Any opinion?

Cheers,


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] OPAC header

[Paul T. Manauis]

What changes do i have to make, so that the opac header is visible in other
opac pages like search.  Based on some tutorials, i just have to edit
opacheader, but i works only on the opac home page but not in search
results.


-- 

*Paul ManauisMIS Executive Officer*
*Universidad de Sta. Isabel*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Subject Headings Display in OPAC

[Paul Hoffman]

On Fri, Dec 07, 2018 at 04:21:52PM +, Tami Wilkerson wrote:
> Koha newbie here, so please pardon my ignorance!
> Is there a way to choose which 650 fields display in the OPAC? I would 
> like ours to only show Library of Congress subjects (650 0_0) and 
> suppress all others.

You can customize this by editing some XSLT.

Check the system preference OPACXSLTDetailsDisplay; if it's set to 
"default" then your Koha is probably using this file to build the 
detailed record display:

/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2intranetDetail.xsl

You can customize this to display a 650 field only if indicator 2 is 0.  
I haven't done this, so take this with a grain of salt, but I believe 
the way to proceed is to copy this file, edit the copy -- check it with 
_xsltproc_, or with _xmllint --noout_ if you just want to make sure it's 
at least well-formed XML -- and then change the system preference to use 
the edited copy and see if it's working the way you want.  (Be prepared 
to change it back quickly!)

The file we have (Koha 18.05) deals with subject fields in a block that 
begins like this:

 683 
 684 Subject(s): 
 685 

It shouldn't be hard to find in your version, even if the line 
numbers are different.  Try changing the XPath criteria from this:

marc:datafield[substring(@tag, 1, 1) = '6' and not(@tag=655)]

To something like this:

marc:datafield[substring(@tag, 1, 1) = '6' and not(@tag=655) and @ind2=0]

But be careful, and check the LC docs for 6xx fields, since indicator 
2 doesn't have the same meaning in all of them.  I'm not a cataloger, so 
I'll leave that to you (or others) to figure out.  :-)

HTH,

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Subject Headings Display in OPAC

[Paul A]

On 2018-12-07 2:51 p.m., King, Fred wrote:

Welcome! There's probably an easier way to do it, but I take out the 650 fields 
I don't want when I'm editing the MARC records. I figure our users probably 
don't need the subject headings in French, Spanish, German, etc. We're a very 
small library--the number of records our cataloging department* adds annually 
is in the low three figures--so that might not be the best solution for you. It 
does work, though.


If some/many/most of your records come via Z39.50 and contain 650 
authorities, the "IT cost" of retaining a 650 (that another 
bibliographer/cataloguer thought was useful) is trivial -- and the 650 
could be useful one day to someone else further down the line -- so I 
would suggest not deleting.


_However_, fine tuning this to LoC 650s only is perhaps more 
challenging. Have you looked at using e.g. 690 for your local 
authorities and not displaying them in OPAC?


You can eliminate them in your OPAC display by putting a suitable code# 
in your MARC frameworks › BKS framework structure › Tag 690 subfield 
structure › Edit subfields constraints > Advanced constraints:  e.g. 6 
which takes it out of OPAC but leaves it editable by staff.


Best season's greetings -- Paul


-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Tami Wilkerson
Sent: Friday, December 07, 2018 11:22 AM
To: koha@lists.katipo.co.nz
Subject: [Koha] Subject Headings Display in OPAC
Hello,

Koha newbie here, so please pardon my ignorance!
Is there a way to choose which 650 fields display in the OPAC? I would like 
ours to only show Library of Congress subjects (650 0_0) and suppress all 
others.

Thank you,
Tami

Tami Wilkerson
Library Program Lead/Librarian
Columbia River Inter-Tribal Fish Commission
StreamNet Regional Library
700 NE Multnomah St. Suite 515
Portland, OR 97232
twilker...@critfc.org<mailto:twilker...@critfc.org> / 503.736.3581

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Load Balancing with Koha

[Paul Poulain]

hello,

wow, did you need load balancing for performance reasons, or was it just 
by choice ?


We're supporting a library that has 1M biblios, 1.7M items, 300+ issues 
and 70k+ patrons, and they don't need load balancing at all. It's hosted 
on their platform, virtualised with VMWare. They had to tweak some 
things to get good performances, and that's it, it works !


Le 07/12/2018 à 14:50, Dave Sherohman a écrit :

On Tue, Dec 04, 2018 at 04:46:59PM +0100, Paul Poulain wrote:

Can you share the metrics of the Koha DB ? (# of biblios, # of yearly
issues, # of patrons, # of librarians, ...)

Yearly issues 260k (not counting renewals)
Patronrecords: 68k
200 libray staff
2.4M biblios
2.4M items


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] XSLT question

[Paul Hoffman]

On Wed, Dec 05, 2018 at 09:18:35PM +0100, Michael Kuhn wrote:
> I've got the following content in MARC 245:
> 
> 245 00 _aTitle
>_pPart
>_nVolume
> 
> I'm using the following XSL code in file "MARC21slim2OPACDetail.xsl":
> 
>  
>  
>  
>  a
>  
>  
>  
>  
>  
>  
>  
>  
>  
>   :  class="title_medium">
>  
>  
>  
>  
>  
> 
> I'm expecting the following two lines:
> 
> Title
> Volume : Part
> 
> But in fact I'm getting these lines:
> 
> Title : Part
> Volume
> 
> It seems like I can't get 245$n to precede 245$p ... What am I doing wrong,
> can please someone explain?

You're doing this:

if there's a 245 field:
for each 245 field:
print subfield $a
for each subfield $n or $p:
if it's $n:
print "" followed by the subfield contents
else if it's $p:
print " : " followed by the subfield contents
end
end
end
end

But that doesn't process 245$n before 245$p.  So use the following 
logic, or something like it: 

for each 245 field:
print subfield $a
for each subfield $n:
print "" followed by the subfield contents
end
for each subfield $p:
print " : " followed by the subfield contents
end
end

(The outer conditional seems unnecessary to me, but I could be wrong).

Does that help?

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Load Balancing with Koha

[Paul Poulain]

Hi Dave,

Can you share the metrics of the Koha DB ? (# of biblios, # of yearly 
issues, # of patrons, # of librarians, ...)


Le 04/12/2018 à 14:06, Dave Sherohman a écrit :

On Tue, Dec 04, 2018 at 02:35:39PM +0200, Mutsikiwa Admire wrote:

Just wondering if it is possible to have a Koha implementation in which we
have a front-end Load Balancer such as NGINX or HAProxy, several Koha  web
server instances powered by one database server running on a separate server
with balancing from source with stick-table in the case of HAProxy.

Yep!  I'm currently handling the sysadmin side of an installation which
runs the koha web interface on two mirrored web servers behind an F5
BIG-IP load balancer, with a third non-web server to handle cron jobs,
outgoing mail, etc.  All three servers talk to a three-node
mariadb/galera cluster (although they only actually talk to a single
node because koha doesn't play well with multi-master database
configurations) for data storage and a five-node elasticsearch cluster
for indexing.

On each individual web server (after passing through the load balancer),
the request path is nginx => apache => starman/plack.  nginx serves
static files, apache handles shibboleth authentication, and starman runs
the koha scripts.

I opted to go with the F5 device instead of nginx for the front-end load
balancing because it was already available through the campus data
center and I didn't want to deal with setting up failover on an IP
address myself, but I can't see any reason that it wouldn't work just as
well (from koha's perspective) with nginx or haproxy as the load
balancer instead of a dedicated device.


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] subfields

[Paul Hoffman]

On Fri, Nov 02, 2018 at 02:29:04PM +, anabela semedo wrote:
> I need to create field 952 of a record in the editmarc before importing it 
> into koha.
>  this record is from the winisis and the fields 040, 060, 970(Literatura 
> cabo-verdiana), 970(Diario)
> must be subfields 040 = 952 $a, 060 = 952 $e and 970(Literatura 
> cabo-verdiana) = 952 $8.
> field 970(Diario) will be field 650 $a.
> 
> field 245 ($aDiario of the islands / $dManuel Veiga.), subfield $d will 
> become 245 $c
> Someone tell me how to do it?

Do you need to change just this one record?  Or do you have a file of 
records and each one needs to be changed in the same way?

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Batch checkin in 18.05 koha

[Paul Hoffman]

On Wed, Oct 31, 2018 at 08:27:08PM +0500, Arshad Iqbal wrote:
> This feature can be added in koha coming version..
> On Oct 31, 2018 4:58 PM, "Owen Leonard"  wrote:
> >
> > > Without offline plugin not possible
> >
> > Koha has no built-in tool for batch checkins like there is for batch
> checkouts.
> >
> > There is an open bug report for this feature, but as far as I know no
> > one is working on it:
> >
> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19814

If you're feeling adventurous, you might try doing this from the command line
using a simple script; something like this (totally untested!):

# ---
#!/usr/bin/perl

use strict;
use warnings;

use C4::Context;
use C4::Circulation;

while () {
chomp;
s/\r$//;
my $result = ProcessOfflineReturn({ 'barcode' => $_ });
if ($result =~ /success/i) {
print STDERR "OK $_\n";
}
else {
print STDERR "ERR $_ $result\n";
}
}
# ---

Save it as /foo/bar/checkin.pl (just for the sake of example), make it
executable (chmod a+x /foo/bar/checkin.pl) and invoke it like this:

koha-shell -c /foo/bar/checkin.pl < /foo/my/file.txt

Where /foo/my/file.txt is just a bunch of item barcodes, one per line.

The ProcessOfflineReturn() function takes care of everything for you -- look up
the item given its barcode, find the patron who checked it out, mark it
returned, etc.  It's defined in the file /usr/share/koha/lib/C4/Circulation.pm
around line 3726 if you want to see exactly what it does.  (I find the Koha
source code remarkably easy to read and generally have no trouble figuring out
how to use it from a Perl script, though it helps that I've been programming in
Perl for a long, long time.)

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] FW: Re: convert ISO to marc file with MarcEdit

[Paul Hoffman]

Ana Bela,

On Tue, Oct 30, 2018 at 05:01:59PM +, anabela semedo wrote:
> thank you OWEN, yes I tried converting with MarcEdit, but it does not convert.
> reading many tutorials, I think my problem is even in the data.

Is there a mailing list for ABCD?  If so, I would ask them how to export 
records in MARC21 format.  Or perhaps in UNIMARC, since Koha seems to 
support that as well.

> I export and convert with marcedit, I open with the marc editor, I get 
> the message that my file is not a valid marc.

What this means is that the file is not valid MARC21 (or any other 
variety of ISO-2709 that MarcEdit is able to parse).

> this is an example of the exported record of ABCD base
> 
> 0078904090004500068012181319311000107910
> 00118110001282100013831000149020005000159040003000209080003000239090
> 002000269540002801500032002000300037004000200040006000200042009000600044
> 0160016000500180108000660430011001740380047001850260023207600130023807600280
> 02510760031002790760018003100370013003280370010003419810018003519820005003690100
> 00500374#Doação.1986#PT#en#m#MON#true#21#M#m#Livro#Schasse^bUlrich#"Male
> -female wage differences in west germany: empirical evidence, causes and 
> implica
> tions"/ Ulrich Schasse#016 SCH ma#Lisboa: Centro de Estudos da Dependencia, 
> 1986
> #44 p.#Bibliografia#Politica de desenvolvimento#Mulheres-Equidade de géneros#M
> ulheres-Alemanha#2 exemplares#Inv. 2016#20140601 08:49:45#abcd#true##

Hmm, that does look like ISO-2709 data, but not MARC21 or UNIMARC.  Do 
you know which variety of ISO-2709 it is?  Here are the various parts of 
the leader (a.k.a. record label) that convince me that it's not MARC21 
or UNIMARC:

Offset  Contents  Description
--    --
00-04   00789 Record length = 789 bytes
05-09   0 ???
10  0 Indicator count (MARC21 and UNIMARC have 2 here)
11  0 Subfield code count (MARC21 and UNIMARC have 2 here)
12-16   00409 Base address of data
17-19   000   ???
20  4 Length of the length-of-field
21  5 Length of the starting-character-position
22  0 Length of the implementation-defined
23  0 Undefined in MARC21

> I try with exported winisis data and I can edit with marcedit.
> but I have 30,000 ABCD registration to convert.
> thanks for listening.

You'll have to find a way to convert the exported records to MARC21 or 
UNIMARC, or to some other ISO-2709 format that Koha supports.  Either 
that, or convince ABCD to export in one of those formats.  Good luck!

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] FW: Re: convert ISO to marc file with MarcEdit

[Paul Hoffman]

Anabela,

Your attachments haven't come through -- either the mailing list, or 
some overeager mail server, is stripping them.

Paul.

On Mon, Oct 29, 2018 at 03:43:12PM +, anabela semedo wrote:
> I'm sorry, this is it.
> 
> 
> De: Koha  em nome de anabela semedo 
> 
> Enviado: 29 de outubro de 2018 14:40
> Para: Koha list
> Assunto: [Koha] FW: Re: convert ISO to marc file with MarcEdit
> 
> Hi Paul, it's in anexo.
> 
> De: Microsoft Outlook 
> Enviado: 29 de outubro de 2018 14:36
> Para: Paul Hoffman
> Assunto: Não entregue: Re: [Koha] convert ISO to marc file with MarcEdit
> 
> 
> mx.google.com rejeitou a sua mensagem destinada aos seguintes endereços de 
> correio eletrónico:
> 
> Paul Hoffman (p...@flo.org)<mailto:p...@flo.org>
> A mensagem não foi entregue porque o fornecedor de correio eletrónico do 
> destinatário a rejeitou.
> 
> 
> mx.google.com devolveu este erro:
> This message was blocked because its content presents a potential security 
> issue. Please visit https://support.google.com/mail/?p=BlockedMessage to 
> review our message content and attachment content guidelines. 
> p1-v6si6690955wrp.52 - gsmtp
> 
> 
> 
> 
> 
> 
> 
> Informações de diagnóstico para administradores:
> 
> Servidor de origem: AM5EUR03HT202.mail.protection.outlook.com
> 
> p...@flo.org
> mx.google.com
> Remote Server returned '552-5.7.0 This message was blocked because its 
> content presents a potential 552-5.7.0 security issue. Please visit 552-5.7.0 
> https://support.google.com/mail/?p=BlockedMessage to review our 552 5.7.0 
> message content and attachment content guidelines. p1-v6si6690955wrp.52 - 
> gsmtp'
> 
> Cabeçalhos originais da mensagem:
> 
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
>  s=selector1;
>  
> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
>  bh=cIYxQ6QR5wHzkrcd7VWqZFqMKskLQPjUGPVd0BDLoN0=;
>  
> b=PFqI2VIj+XtHqPhkos5DMamYOqKMufYhuW6pUw/qC/AeVQd9/1n/NsiUw/euiZqwpmI+BCRz2gZ9wiH3Flr2LPle5q1ylXX/+L3Dfu00wEQH7iGg7ifTQRKLGYIpPdipDQnLmmui/EdWQvWjipGYfcfIzUTwPo3jzptigwhinTUg0DIsng97Q3wm61tnvcrIsEU8llWHKaHkwqryHGmTnaOCCCLobGMcGwx1QDREdHokLxvfUBpSq+Fta9qQFOsGMEKVEU70kQTCzLDg7vFAX5HcMPnFEXtzqDEHD3s4e7wqKvBzh9wQ5+JRPQgJmrfDzoOT0j+6J1KmewODUWRMiQ==
> Received: from AM5EUR03FT037.eop-EUR03.prod.protection.outlook.com
>  (10.152.16.60) by AM5EUR03HT202.eop-EUR03.prod.protection.outlook.com
>  (10.152.17.17) with Microsoft SMTP Server (version=TLS1_2,
>  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1294.14; Mon, 29 Oct
>  2018 15:36:37 +
> Received: from VI1PR05MB4317.eurprd05.prod.outlook.com (10.152.16.53) by
>  AM5EUR03FT037.mail.protection.outlook.com (10.152.17.241) with Microsoft SMTP
>  Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
>  15.20.1294.14 via Frontend Transport; Mon, 29 Oct 2018 15:36:37 +
> Received: from VI1PR05MB4317.eurprd05.prod.outlook.com
>  ([fe80::55e3:b22c:8bd1:4f3b]) by VI1PR05MB4317.eurprd05.prod.outlook.com
>  ([fe80::55e3:b22c:8bd1:4f3b%2]) with mapi id 15.20.1273.027; Mon, 29 Oct 2018
>  15:36:37 +
> From: anabela semedo 
> To: Paul Hoffman , "koha@lists.katipo.co.nz"
> 
> Subject: Re: [Koha] convert ISO to marc file with MarcEdit
> Thread-Topic: [Koha] convert ISO to marc file with MarcEdit
> Thread-Index: AQHUbvX4EWltluCXgkCM+fIhVKYwZ6U2QcqAgAAahiE=
> Date: Mon, 29 Oct 2018 15:36:37 +
> Message-ID: 
> 
> References: 
> ,<20181029140114.GA4986@trot>
> In-Reply-To: <20181029140114.GA4986@trot>
> Accept-Language: pt-PT, en-US
> Content-Language: pt-PT
> X-MS-Has-Attach: yes
> X-MS-TNEF-Correlator:
> x-incomingtopheadermarker: 
> OriginalChecksum:3D730D87DF4E929CF9F1C78CEBC1ADEB118FEE01AF5A67F2D47B8BE47FCAC3A0;UpperCasedChecksum:7589DA788BA469F16972147D2EAD47866BEC61F258D5A004EF191F538BB836A2;SizeAsReceived:7129;Count:46
> x-ms-exchange-messagesentrepresentingtype: 1
> x-tmn: [rhHYELAjgS4i/zVQg9N58HxHjWM3f4Lf]
> x-ms-publictraffictype: Email
> x-microsoft-exchange-diagnostics: 
> 1;AM5EUR03HT202;6:+EQHmd8e69IENLGwgq2tLV/rwLeRrJ+snvOoYWW/eGmtMomH3ACI/kbSq9zwA2VvUXv2Hh8WrLy+bjEooOQwlsw3XfmW5E4RjvJIiqSAXBAtwWlAd75sLw3jWMAoRF9y0fIbFeusEFARP3HxrKDvuQCX/puiavnBcOMLw1/RT5/Y5HREkONrukPx9sAEBmjMW605ECFWrQM4k2HYxq0O73ffsTcfZLSe077gqySnkcxqXKNKlAol+kbACeYkdPdilOHK2ZfeiestaUonbMdRHDp+SSJgvEdIx8hdT5lFSV3LvSODeyrPuJa9gpYoZnzn1zNTy8nCVPIeTkeV4UBiwX/u/a0LI/GVXa8BpP9SC5kXBs1SarapwyPGw/FPYyh0fqH7Gkq1oiCnq6ery1A+GK2IfcbmNs3LdcFelJt7V4QpbzL35EVG535QehE0aAJl/0TO18UYwHOFqkt7eW2zEw==;5:UdeucfjkmcpdVXuJu3cXNJZZoBDbptYx1btg5Pj8hN9oqN/pYxXf9tC8lkVTqcVCkWteNSH7BaH0tp0zwk3t0hAEFgW0joN89kwcTskX7pE0slzNHB06yCR

Re: [Koha] convert ISO to marc file with MarcEdit

[Paul Hoffman]

Ana,

On Sun, Oct 28, 2018 at 07:39:41PM +, anabela semedo wrote:
> Olá amigos, tenho que converter uma quantidade enorme de dados da base de 
> dados ABCD, da bireme, para o koha.
> 
> já instalei o MarcEdit e já fiz alguns testes com dados importados da 
> Porbase, catálogos da BNPT, e correu tudo bem, mas com os dados da ABCD não 
> funciona.
> 
> Ambas as bases exportam formato ISO mas com aspetos diferentes.
> o ficheiro registso1.iso em anexo é da base de dados de Portugal e o ficheiro 
> um.iso é da ABCD. podiam dar uma vista de olhos?
> 
> como podem ver consegui converter o registo1.iso em registo1.mrc
> 
> Por favor me ajudem.
> 
> Ana Bela

[en] Welcome to the mailing list!  :-)  You forgot to attach the files.  

[pt] Bem vindo à lista de discussão!  :-)  Você esqueceu de anexar os 
ficheiros.

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Barcode

[Paul Hoffman]

On Mon, Oct 08, 2018 at 08:40:46AM +0800, Ma. Victoria H. Silva-Manuel wrote:
> Is there a way for Koha to disregard extra zeros at the beginning of the
> barcode?

I doubt that this is possible.  In any case, a better solution would be 
to fix the barcodes in Koha.

> Example, the barcode is 00112495d. Can Koha just read it as 112495d?
> When we encode our barcodes in Koha we did not place extra zeros but
> because we acquire another library system and it cannot accept barcodes
> with different lengths we need to add extra zeros at the beginning of the
> barcode numbers.

Let me make sure I understand correctly: are you saying that the barcode 
in Koha is "112495d" but the barcode that you scan is "00112495d"?

Also, are you talking about item barcodes, patron barcodes, or both?

If you have access to your Koha server, you might be able to fix 
barcodes using SQL something like this (assuming you're talking about 
items):

UPDATE items
SETbarcode = concat("00", barcode)  -- prepend "00"
WHERE  barcode LIKE "11_"   -- five "_" characters
;

Please don't run this query as is!  Instead, use this is inspiration for 
a SQL query that fits your particular needs.  And check first -- for 
example, if you think most of your item barcodes are seven characters 
long, and begin with "11" or "12", see what numbers you get from a query 
like this:

SELECT count(*), '11X'
FROM   items
WHERE  barcode LIKE "11_"
UNION ALL
SELECT count(*), '12X'
FROM   items
WHERE  barcode LIKE "12_"
UNION ALL
SELECT count(*), 'other'
    FROM   items
WHERE  barcode NOT LIKE "11_"
ANDbarcode NOT LIKE "12_"
;

Good luck!

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] REPORT 100 AND 700 MARC TAG

[Paul Hoffman]

Or like this, which might (or might not!) be more efficient since it 
only resorts to ExtractValue if the author is NULL:

SELECT IF(b.author IS NULL,
  ExtractValue(m.metadata, 
'//datafield[@tag="700"]/subfield[@code="a"]'),
  b.author
 )
FROM biblio b INNER JOIN biblio_metadata m USING (biblionumber);

Paul.

On Thu, Oct 04, 2018 at 09:36:08AM -0400, Caroline Cyr-La-Rose wrote:
> Hi Hans,
> 
> I'm no SQL expert either, but I usually use CONCAT_WS to have the 100 and
> 700 authors appear in the same column.
> 
> Also, check your mappings in Administration > Koha to MARC mapping. You may
> be able to use biblio.author instead of ExtractValue for the 100 field.
> 
> So something like
> 
> SELECT CONCAT_WS(biblio.author, ExtractValue(metadata,
> '//datafield[@tag="700"]/subfield[@code="a"]')) FROM biblio_metadata JOIN
> biblio USING (biblionumber)
> 
> (metadata is used instead of marcxml in more recent versions of Koha)
> 
> Good luck!
> 
> Caroline
> 
> Caroline Cyr La Rose, M.S.I.
> Bibl. prof. / Chargée de la formation et du soutien
> 
> Tél.  : 1 (833) 465-4276
> caroline.cyr-la-r...@inlibro.com <mailto:caroline.cyr-la-r...@inlibro.com>
> 
> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
> Le 2018-10-04 à 04:53, Hans Manrique a écrit :
> >Hello everyone,
> >
> >I would like to have a report of only fields 100 and 700 in a single
> >column. I'm a student and I do not understand much about sql, but I've
> >managed to get a 100 report through ExtractValue syntax queries (marcxml,
> >xpath). But I do not know how to get one of the fields 100, 700 in a single
> >report and in a column. Is that possible?
> >
> >Hans Manrique
> >___
> >Koha mailing list  http://koha-community.org
> >Koha@lists.katipo.co.nz
> >https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Check out restriction to category / branch for School Libraries

[Paul Hoffman]

On Wed, Oct 03, 2018 at 02:13:18AM -0700, anjoze wrote:
> Yes Cron is running:
> # Hourly holds queue updated
> 52   * * * *  __KOHA_USER__  $KOHA_CRON_PATH/holds/build_holds_queue.pl 
> >/dev/null 2>&1
> 
> Nothing happens :(

You might try changing the cron job command so that it doesn't throw 
away all output:

52   * * * *  __KOHA_USER__  $KOHA_CRON_PATH/holds/build_holds_queue.pl >> 
/tmp/build_holds_queue.log 2>&1

Then look at /tmp/build_holds_queue.log -- maybe something there will 
explain what's going wrong.

(I hate cron jobs that blithely discard all output!)

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Exclude users from search (check out)

[Paul Hoffman]

On Tue, Sep 25, 2018 at 06:48:41PM +0700, zefanja wrote:
> we use Koha in our school and therefor many students get enrolled each
> year, but also many students leave the school every year. Every year we
> have more and more users, that are not at school anymore, but they still
> exist in Koha. If we want to checkout books and search for the right
> user we have many similar names over the years, sometimes the same
> firstname and lastname.
> 
> Is it possible to deactivate users so they are excluded from the search
> result (checkout)? I don't want to delete them because we will loose the
> circulation data.

I think you'd have to modify the source code, but if you want to go down 
that path then look for the call to 
C4::Utils::DataTables::Members::search in the file 
intranet/cgi-bin/circ/circulation.pl (lines 242-248 in our install).  
Immediately after the following line, which sets the variable 
$borrowers, add some code that discards elements in @$borrowers (i.e., 
that discards patrons) with an expiration date (too far) in the past.  
Something like this (totally untested!):

my $borrowers = $results->{patrons};
#  Add these lines 
use POSIX qw(strftime);
# Omit if expired more than 30 days ago (not taking possible
# daylight saving time transitions into account!)
my $cutoff = strftime('%Y-%m-%d', localtime(time - 30*86400));
# ^^ Or maybe '%Y%m%d'?
@$borrowers = grep { $_->{dateexpiry} gt $cutoff } @$borrowers;
# -

However, what circulation data exactly do you want to preserve -- data 
on fines that you're still hoping will be paid?  I assume when purging 
patron you can skip anyone with outstanding fees, so you'd get rid of 
the vast majority(?) of old, crufty patrons but leave the ones you care 
about.

Paul.

-- 
Paul Hoffman 
Software Services Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Koha-translate] Your Mailman server is misconfigured

[Paul Poulain]

Hello all,

The problem on mailman configuration is fixed.

Thanks for those who reported it !


Le 26/08/2018 à 10:21, Rubén Fernández Asensio a écrit :

Hello all, is anybody there?

I tried to join this list through the web interface but the web server 
seems misconfigured: 
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate

It throws a "502 Bad Gateway" error.

Can anybody fix this please?


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Send all notices to all available eMail addresses

[Paul Hoffman]

Have you tried a comma?  That's the standard, not a semicolon.  The
people who developed Outlook, etc. don't particularly seem to care about
standards (pet peeve #9,037).

Paul.

On Fri, Aug 24, 2018 at 01:49:00PM +, Boettcher, Uwe wrote:
> Hi Alvaro,
> 
> thanks a lot for your feedback.
> 
> Indeed, we already have tried to enter more than just one email address into 
> the address field. Unfortunately, as you already assumed, Koha comes up with 
> an error message, claiming the email address not to be correct. We have tried 
> several combinations of blank and semicolon, but none was accepted.
> 
> Best
> 
> Uwe
> 
> Von: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
> Gesendet: Freitag, 24. August 2018 15:24
> An: Boettcher, Uwe 
> Cc: zefanja ; koha@lists.katipo.co.nz
> Betreff: Re: [Koha] Send all notices to all available eMail addresses
> 
> Hi,
> 
> Haven't tested on Koha but in other applications, the workaround I use is to 
> enter both email addresses on the same field separated by a semi-colon (;) 
> something like "ema...@domain.com<mailto:ema...@domain.com>; 
> ema...@domain2.com<mailto:ema...@domain2.com>"
> 
> Koha might not allow the ; and space as valid characters on the email address 
> and the email process might also fail. You can also try with a semicolon only 
> (no space).
> 
> Regards,
> 
> Alvaro
> 
> |-|
> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier 
> celular y Nextel
> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y 
> GPRS online
>   Visitenos en www.perusms.com<http://www.perusms.com>
> 
> 2018-08-24 5:52 GMT-05:00 Boettcher, Uwe 
> mailto:uwe.boettc...@whu.edu>>:
> Dear all,
> 
> we have the same problem, just with professors and personal assistants, and 
> would be happy to learn about a way to send notices to more than just one 
> e-mail address derived from a patrons' account.
> 
> Many thanks in advance, and kind regards
> 
> Uwe
> --
> (Mr.) Uwe Boettcher
> WHU - Otto Beisheim School of Management
> Vallendar, Germany
> 
> -Ursprüngliche Nachricht-
> Von: Koha 
> [mailto:koha-boun...@lists.katipo.co.nz<mailto:koha-boun...@lists.katipo.co.nz>]
>  Im Auftrag von zefanja
> Gesendet: Freitag, 24. August 2018 12:10
> An: koha@lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>
> Betreff: [Koha] Send all notices to all available eMail addresses
> 
> Hi all,
> 
> we are using Koha in our school library and we have the following
> "problem". We checkout books to all of our students starting from
> preschool. Especially the younger once don't have a personal eMail
> address. So we like to send notices (checkouts, checkins, overdues...)
> to both parents. As far as I understand Koha it send the notices only to
> one address. We could put in one of the parent's email, but we like to
> inform both.
> 
> I've read that overdue_notices.pl<http://overdue_notices.pl> has an 
> repeatable --email parameter.
> Where can I change it to send the notice to both parents?
> 
> Are there other ways to solve this problem or is it just not possible?
> 
> I'm thankful for any hints.
> 
> Regards,
> Stephan
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz>
> https://lists.katipo.co.nz/mailman/listinfo/koha
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz>
> https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Field 003 of Marc21

[Paul Hoffman]

Just for future reference, the Library of Congress maintains the
documentation of the MARC21 standard; for bib record documentation,
start here:

http://www.loc.gov/marc/bibliographic/

It's not always easy reading, but as a systems librarian (and not a
cataloger!) I find it indispensable.

Paul.

On Mon, Aug 06, 2018 at 04:22:02PM +0500, Hira Akram wrote:
> Hi All,
> Can you please tell me what is filled in field 003 of MARC21 format?
> 
> I have searched this on internet and this is what I found : MARC code for the 
> organization whose control number is contained in field 001. 
> 
> I am unable to understand this. Can anyone help.
> 
> Thanks
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Field 003 of Marc21

[Paul A]

On 2018-08-06 09:26 AM, King, Fred wrote:

Real catalogers are going to turn pale and have to sit down when they read this


IT technicians (and lawyers) might also turn pale. The combination of 
001 and 003 should be unique, and show the origin (certainly as a 
courtesy, if not as the responsibility and the possible copyright of a 
z39-50 download) of what you are using in your library db. "Your 
library" might be big, small, at home, whatever; but if you make your 
records available to the public, surely some level of accountability is 
desirable.


MARC21 (and other flavours used by Koha) have been developed over many 
years from tradition, some common sense, some technicalities, probably 
many more considerations by tens of thousands of quite smart librarians, 
archivists and end-users. Koha makes this available at a fairly painless 
level.



*And yes, someday I'm going to move the catalog from the MS Access 97 database 
to Koha.
Then please use Koha as a recognizable library catalogue rather than a 
glorified spreadsheet. But YMMV.


Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Emails

[Paul A]

On 2018-07-31 08:22 AM, vinod mishra wrote:

There is chances of attack/spam through your Koha server, however gmail
always block such automated emails after some time as per my observation.

[snip]

On Tue, Jul 31, 2018 at 5:45 PM, Hira Akram  wrote:

I Checked and it is showing too many login attempts in log that’s why
google server has blocked emails from this account. In Gmail account, it is
showing too many random emails on invalid accounts. But I haven’t sent
these through Koha or anything. Is it possible that koha sent these emails
automatically??


This is not a Koha problem. Do you use DKIM and SPF? If so you can 
*perhaps* contact gmail for a solution. See 
<https://support.google.com/mail/answer/6227174>, specifically 
"authentication domain".


In a nutshell, email deliverability to gmail is getting very complicated 
-- they handle billions of pieces of email/day, and (since at least 
2015) have radical protection/rejection practices after even the most 
minor "sniff" of UBE -- and this could well not be *you* but some other 
user in a bigger block of IP space that has a bad reputation.


Your logs show "(delivery temporarily suspended: connect to 
smtp.gmail.com[74.125.24.109]:587: Connection timed out)" which looks 
like tar-pitting. Unless you have an experienced email technician on 
staff, you could have problems. Once your (or whoever owns your block of 
IP space) "reputation" is hurt, it's not easy to get delisted.


Good luck -- Paul





[snip]


example is shown here.
-
# tail -f /var/log/mail.log
Apr 28 11:20:03 gechlibrary postfix/smtpd[4449]: disconnect from
localhost[127.0.0.1]
Apr 28 11:20:32 gechlibrary postfix/smtp[4451]: connect to smtp.gmail.com
[74.125.24.108]:587: Connection timed out
Apr 28 11:20:32 gechlibrary postfix/smtp[4452]: connect to smtp.gmail.com
[74.125.24.109]:587: Connection timed out
Apr 28 11:21:02 gechlibrary postfix/smtp[4451]: 9BE0E7805B6: to=<
x...@gmail.com>, relay=none, delay=60, delays=0.12/0/60/0, dsn=4.4.1,
status=deferred (connect to smtp.gmail.com[74.125.24.109]:587: Connection
timed out)
Apr 28 11:21:03 gechlibrary postfix/smtp[4452]: connect to smtp.gmail.com
[74.125.24.108]:587: Connection timed out
Apr 28 11:21:03 gechlibrary postfix/smtp[4452]: C7A8F7805E6: to=<
x...@gmail.com>, relay=none, delay=60, delays=0.07/0.01/60/0, dsn=4.4.1,
status=deferred (connect to smtp.gmail.com[74.125.24.108]:587: Connection
timed out)
Apr 28 11:21:03 gechlibrary postfix/smtp[4453]: connect to smtp.gmail.com
[74.125.24.108]:587: Connection timed out
Apr 28 11:21:03 gechlibrary postfix/smtp[4453]: E4358780614: to=<
p...@gmail.com>, relay=none, delay=60, delays=0.07/0.01/60/0, dsn=4.4.1,
status=deferred (connect to smtp.gmail.com[74.125.24.108]:587: Connection
timed out)

firewall was blocked, and because of this reason, status = deferred was
appeared in mail log.

#mialq

18308780A2A  918 Sat Apr 28 10:40:03  root@localhost
(delivery temporarily suspended: connect to smtp.gmail.com[74.125.24.109]:587:
Connection timed out)

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [EXTERNAL] NCIP User Question - biblionum in 001 vs 999c

[Paul A]

On 2018-07-26 05:34 PM, Kelly Drake wrote:
[snip]

Heather and Paul A - Does an ex-maritime librarian count? I used to work in
the library at Mystic Seaport!


Yup... Paul O'P is an old friend of mine.

Best -- Paul (another one.)


Kelly



On Thu, Jul 26, 2018 at 1:17 PM, Joy Nelson 
wrote:


Hi Kelly and Heather!
In many other ILS systems the 001 was/is indeed a field that contained a
unique value (control number).  I still work with data from time to time
that has a unique id in the 001.  Heather is right that in Koha the unique
id is stored in the 999$c, so you can use the 001 field for whatever you
like.  Some sites put the oclc number in the 001, others just leave it
blank, or just take what comes when cataloging via z3950 (clutch your
pearls on that. :D )

Kelly, I have set up some sites to automatically copy the biblionumber to
the 001 tag.  Yes, it duplicates the data from the 999c to the 001, but it
is done programmatically at night so no upkeep would be needed by
cataloging staff.  As long as all your libraries are okay with this
configuration and don't plan to use the 001 for anything else, let us know
at ByWater and we can set this up for you.

joy



On Thu, Jul 26, 2018 at 10:01 AM, Heather Hernandez <
heather_hernan...@nps.gov> wrote:


Hi, Kelly--

Our records in Koha actually have different values in the 001 field based
on the age of the record.  When I first thought about this, I pretty much
clutched my pearls and took to my fainting couch, thinking things like,
"But the 001 should be our consistent, primary database key!  Oh my stars
and garters!!!"

Then after applying a cool cloth to my forehead I got to thinking about
how
we used the 001 and what data was there:  based on the age of the record,
it's either an old catalog record number (which I want to keep in the
record) or the OCLC number (which I definitely want to keep in the
record).  How do I use it?  Well, to just store those numbers, and if I
want to overlay the existing Koha record with a record that I'm exporting
from the OCLC Connexion Client, I include a 999 $c with the Koha record
number in that field in the OCLC record.  I'm currently having some
trouble
with links into our catalog from our holdings in WorldCat.org, but that
doesn't seem related--we're trying to use ISBNs or title data for that.

So perhaps it might be helpful to ask how you would be using the 001 field
and the 999 $c field, and how it's used among the other libraries.  I
don't
have a lot of experience with using MarcEdit and such since ByWater
supports our Koha catalog & I happily rely on them for things like this,
but I think it would be entirely possible to export your records to
MarcEdit, copy record numbers that you're not using to another field
(e.g.,
035) and copy the Koha biblionumbers to the 001, then reimport/replace the
records.  But that sounds kind of drastic to me.  I also clutch my pearls
at the thought of data being duplicated in a record, e.g., in the 999 $c
as
well as the 001, but I can't think of any harm that it would do in *my*
setting--perhaps others could?  Your system would also need some sort of
configuring for ongoing cataloging, to see that the biblionumber gets
copied into the 001.

But if it were me, I'd think long and hard about if this is really
necessary.  For us, it's been absolutely fine to have the Koha
biblionumbers in the 999 $c and an assortment of types of numbers in the
001--I've gotten up off my fainting couch, adjusted my pearls, and
realized
that it works!:)  I hope that others will chime in, because I would be
very
interested to know about other options and possible consequences that
might
face us in the future since we do have such a variety of numbers in our
001
fields.

I hope this helps!  Best,
h2
~~
Heather Hernandez
Technical Services Librarian
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor
<https://maps.google.com/?q=2+Marina+Blvd.,+Bldg.+E,+3rd+floor=gmail=g>,
San Francisco, CA  94123-1284
415-561-7032, heather_hernan...@nps.gov
Library catalog: http://keys.bywatersolutions.com/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha





--
Joy Nelson
Vice President of Implementations

ByWater Solutions <http://bywatersolutions.com>
Support and Consulting for Open Source Software
Phone/Fax (888)900-8944
What is Koha?  <http://bywatersolutions.com/what-is-koha/>







___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [EXTERNAL] NCIP User Question - biblionum in 001 vs 999c

[Paul Hoffman]

Actually, that's the leader.  The 001 field is documented here:

http://www.loc.gov/marc/bibliographic/bd001.html

Paul.

On Thu, Jul 26, 2018 at 04:06:50PM -0400, Paul A wrote:
> I'm not sure where this thread is going, but from one "maritime" library to
> another, the 001 is defined at
> <http://www.loc.gov/marc/bibliographic/bdleader.html> and shouldn't have
> anything to do with biblio numbers (which are stored in 999$c as far as Koha
> is concerned and are used relationally with numerous other data entries.)
> 
> As to OCLC, our cataloguers see entries at 035$a in the format
> "(OCoLC)34125755" (again, see
> <http://www.loc.gov/marc/bibliographic/bd035.html> which specifically
> mentions OCLC.) Our budget does not cover the cost of OCLC services, so I am
> blissfully ignorant of how to use their numbers -- maybe they, rather than
> Koha, are better equipped to answer your query?
> 
> Best -- Paul
> 
> 
> 
> On 2018-07-26 12:01 PM, Heather Hernandez wrote:
> >Hi, Kelly--
> >
> >Our records in Koha actually have different values in the 001 field based
> >on the age of the record.  When I first thought about this, I pretty much
> >clutched my pearls and took to my fainting couch, thinking things like,
> >"But the 001 should be our consistent, primary database key!  Oh my stars
> >and garters!!!"
> >
> >Then after applying a cool cloth to my forehead I got to thinking about how
> >we used the 001 and what data was there:  based on the age of the record,
> >it's either an old catalog record number (which I want to keep in the
> >record) or the OCLC number (which I definitely want to keep in the
> >record).  How do I use it?  Well, to just store those numbers, and if I
> >want to overlay the existing Koha record with a record that I'm exporting
> >from the OCLC Connexion Client, I include a 999 $c with the Koha record
> >number in that field in the OCLC record.  I'm currently having some trouble
> >with links into our catalog from our holdings in WorldCat.org, but that
> >doesn't seem related--we're trying to use ISBNs or title data for that.
> >
> >So perhaps it might be helpful to ask how you would be using the 001 field
> >and the 999 $c field, and how it's used among the other libraries.  I don't
> >have a lot of experience with using MarcEdit and such since ByWater
> >supports our Koha catalog & I happily rely on them for things like this,
> >but I think it would be entirely possible to export your records to
> >MarcEdit, copy record numbers that you're not using to another field (e.g.,
> >035) and copy the Koha biblionumbers to the 001, then reimport/replace the
> >records.  But that sounds kind of drastic to me.  I also clutch my pearls
> >at the thought of data being duplicated in a record, e.g., in the 999 $c as
> >well as the 001, but I can't think of any harm that it would do in *my*
> >setting--perhaps others could?  Your system would also need some sort of
> >configuring for ongoing cataloging, to see that the biblionumber gets
> >copied into the 001.
> >
> >But if it were me, I'd think long and hard about if this is really
> >necessary.  For us, it's been absolutely fine to have the Koha
> >biblionumbers in the 999 $c and an assortment of types of numbers in the
> >001--I've gotten up off my fainting couch, adjusted my pearls, and realized
> >that it works!:)  I hope that others will chime in, because I would be very
> >interested to know about other options and possible consequences that might
> >face us in the future since we do have such a variety of numbers in our 001
> >fields.
> >
> >I hope this helps!  Best,
> >h2
> >~~
> >Heather Hernandez
> >Technical Services Librarian
> >San Francisco Maritime National Historical Park Research Center
> >2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
> >415-561-7032, heather_hernan...@nps.gov
> >Library catalog: http://keys.bywatersolutions.com/
> >___
> >Koha mailing list  http://koha-community.org
> >Koha@lists.katipo.co.nz
> >https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> >
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman 
Software Manager
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [EXTERNAL] NCIP User Question - biblionum in 001 vs 999c

[Paul A]

I'm not sure where this thread is going, but from one "maritime" library 
to another, the 001 is defined at 
<http://www.loc.gov/marc/bibliographic/bdleader.html> and shouldn't have 
anything to do with biblio numbers (which are stored in 999$c as far as 
Koha is concerned and are used relationally with numerous other data 
entries.)


As to OCLC, our cataloguers see entries at 035$a in the format 
"(OCoLC)34125755" (again, see 
<http://www.loc.gov/marc/bibliographic/bd035.html> which specifically 
mentions OCLC.) Our budget does not cover the cost of OCLC services, so 
I am blissfully ignorant of how to use their numbers -- maybe they, 
rather than Koha, are better equipped to answer your query?


Best -- Paul



On 2018-07-26 12:01 PM, Heather Hernandez wrote:

Hi, Kelly--

Our records in Koha actually have different values in the 001 field based
on the age of the record.  When I first thought about this, I pretty much
clutched my pearls and took to my fainting couch, thinking things like,
"But the 001 should be our consistent, primary database key!  Oh my stars
and garters!!!"

Then after applying a cool cloth to my forehead I got to thinking about how
we used the 001 and what data was there:  based on the age of the record,
it's either an old catalog record number (which I want to keep in the
record) or the OCLC number (which I definitely want to keep in the
record).  How do I use it?  Well, to just store those numbers, and if I
want to overlay the existing Koha record with a record that I'm exporting
from the OCLC Connexion Client, I include a 999 $c with the Koha record
number in that field in the OCLC record.  I'm currently having some trouble
with links into our catalog from our holdings in WorldCat.org, but that
doesn't seem related--we're trying to use ISBNs or title data for that.

So perhaps it might be helpful to ask how you would be using the 001 field
and the 999 $c field, and how it's used among the other libraries.  I don't
have a lot of experience with using MarcEdit and such since ByWater
supports our Koha catalog & I happily rely on them for things like this,
but I think it would be entirely possible to export your records to
MarcEdit, copy record numbers that you're not using to another field (e.g.,
035) and copy the Koha biblionumbers to the 001, then reimport/replace the
records.  But that sounds kind of drastic to me.  I also clutch my pearls
at the thought of data being duplicated in a record, e.g., in the 999 $c as
well as the 001, but I can't think of any harm that it would do in *my*
setting--perhaps others could?  Your system would also need some sort of
configuring for ongoing cataloging, to see that the biblionumber gets
copied into the 001.

But if it were me, I'd think long and hard about if this is really
necessary.  For us, it's been absolutely fine to have the Koha
biblionumbers in the 999 $c and an assortment of types of numbers in the
001--I've gotten up off my fainting couch, adjusted my pearls, and realized
that it works!:)  I hope that others will chime in, because I would be very
interested to know about other options and possible consequences that might
face us in the future since we do have such a variety of numbers in our 001
fields.

I hope this helps!  Best,
h2
~~
Heather Hernandez
Technical Services Librarian
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
415-561-7032, heather_hernan...@nps.gov
Library catalog: http://keys.bywatersolutions.com/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cataloging Error

[Paul A]

On 2018-07-24 09:24 AM, Michael Kuhn wrote:

 > If you want to see which fields are mandatory, go to Administration >
 > MARC bibliographic framework. Be sure to check the right framework you
 > were using while cataloging (to check that, click on the Settings
 > button in the cataloging form https://snag.gy/cNuFsB.jpg)

Additionally every framework shows a very tiny red asterisk (*) if a 
field is mandatory. So since all the fields 000, 001, 003, 005, 008, 
040$c, 245$a and 942$c in the standard framework are mandatory they show 
this small red asterisk at the left side.


I believe that this query started with cataloguing an *item*.  Our 
cataloguers occasionally run into this, and have always had difficulty 
when on the "items-edit" page understanding that they have to return to 
the "biblio-edit" page to put things right. Maybe it's a bug, but a 
little bit of experience with Koha goes a long way...


Best -- Paul

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Report help needed

[Paul Hoffman]

On Fri, Jul 13, 2018 at 10:06:56AM -0700, Elaine Bradtke wrote:
> This report finds Authors not linked to authorities.  But it only lists
> their names (some of them are quite prolific, and sometimes it's only one
> biblio that needs checking).
> How can I make the following give the biblio number as well as the name?
> 
> SELECT DISTINCT heading FROM (
>  SELECT ExtractValue(metadata,
> '//datafield[@tag="100"]/subfield[@code="a"]') AS heading
>  FROM biblio_metadata
>  WHERE
>   length(ExtractValue(metadata,
> '//datafield[@tag="100"]/subfield[@code="a"]')) != 0 AND
>   length(ExtractValue(metadata,
> '//datafield[@tag="100"]/subfield[@code="9"]')) = 0
> UNION
> [...]

I assume that you can just add biblionumber to the output everywhere 
that a heading appears, something like this (untested!):

SELECT DISTINCT biblionumber, heading FROM (
SELECT biblionumber, ExtractValue(metadata, 
'//datafield[@tag="100"]/subfield[@code="a"]') AS heading
FROM   biblio_metadata
WHERE  length(ExtractValue(metadata, 
'//datafield[@tag="100"]/subfield[@code="a"]')) != 0
ANDlength(ExtractValue(metadata, 
'//datafield[@tag="100"]/subfield[@code="9"]')) = 0
UNION
[...]

Paul.

-- 
Paul Hoffman 
Software Manager
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Item batch modifications using custom SQL or Perl?

[Paul Hoffman]

I've been asked to modify a batch of item call numbers, substituting 
"PYA" for "PZ100" whenever the latter occurs at the beginning of the 
call number.  This doesn't seem possible using the existing Batch Item 
Modification tool (batchMod.pl).

I would love to do this using SQL only, like so:

UPDATE items
SETitemcallnumber = concat("PYA", substr(itemcallnumber, 6))
WHERE  itemcallnumber LIKE 'PZ100%';

However, I suspect that this will mess up indexing or call number browse 
or *something*.  Reading the relevant parts of C4::Items, I believe I 
can more safely accomplish this in Perl, something along these lines...

use C4::Items;
use C4::Context;

use strict;
use warnings;

my $dbh = C4::Context->dbh;
$dbh->{RaiseError} = 1;
my $sql = q{
SELECT  biblionumber, itemnumber, itemcallnumber
FROMitems
WHERE   itemcallnumber LIKE 'PZ100%'
};
my $sth = $dbh->prepare($sql);
$sth->execute;
while (my ($bibnum, $itemnum, $callnum) = $sth->fetchrow_array) {
$callnum =~ s/^PZ100/PYA/;
ModItem(
{'itemcallnumber' => $callnum},
$bibnum,
$itemnum
) or print STDERR "Could not update item $itemnum\n";
}

Is this pretty much the simplest way to safely make unusual batch 
modifications like this?

Thanks in advance,

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Installation problem

[Paul A]

On 2018-07-02 08:54 AM, Bedanta Borah wrote:

I am trying to install koha on ubuntu 18.04. While I enter this command
"sudo koha-create --create-db library"
the outcome is
'Koha requires mpm_itk to be enabled within Apache in order to run.

How to solve this issue.?


From my notes when we tested about a year ago (Ubuntu 16.04LTS), 
mpm-itk was problematic with apache 2.4 (fine on 2.2). It also did not 
load with mpm_event or mpm_worker enabled, you have to use mpm-prefork. 
We finally got it working with:


sudo apt-get install apache2-dev

but I hope there is now a "production" version of apache 2.4 (rather 
than "dev") that might be suitable.


If you find a good solution, please post it back here. We're just 
beginning to test 18.04, but haven't got to Koha yet ;={


Best -- Paul


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra shutting down - no search

[Paul Hoffman]

On Tue, Jun 26, 2018 at 09:14:43AM -0400, Scott Owen wrote:
> Is there any drawback to this ?? (other than the small slice of time where
> the logs may not be written to ) ??

No, not in my opinion -- just do it in the wee hours of the morning to 
avoid a loss of log entries.

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] zebra shutting down - no search

[Paul Hoffman]

On Thu, Jun 21, 2018 at 09:16:56AM -0400, Scott Owen wrote:
> I still seem to be having some issues with logrotate and the zebra service
> starting up
> 
> I have tried both of the options discussed in bug #
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885
> 
> Has there been a good / reliable fix to this issue ? I was hoping that an
> upgrade to  17.11 might be the solution...but sadly, I still seem to have
> this issue on 2 of my 3 Kha installs

Another possible solution, which avoids shutting down Koha altogether, 
is to tweak the logrotate config to use the "copytruncate" setting.  So 
instead of all the prerotate/postrotate stuff, just do this:

/var/log/koha/*/*.log {
rotate 5
weekly
missingok
compress
delaycompress
notifempty
copytruncate
}

Here's what the logrotate man page says about copytruncate:

  copytruncate
 Truncate  the  original log file in place after creating a copy,
 instead of moving the old log file and optionally creating a new
 one.   It  can be used when some program cannot be told to close
 its logfile and thus might continue writing (appending)  to  the
 previous log file forever.  Note that there is a very small time
 slice between copying the file and truncating it, so  some  log-
 ging  data  might be lost.  When this option is used, the create
 option will have no effect, as the old log file stays in place.

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Partnership between BibLibre and Orex

[Paul Poulain]

Hello Koha,

Hugo & I are happy and proud to announce our partnership to increase 
Koha deployment in Spain and other Spanish speaking countries : 
https://www.biblibre.com/en/blog/orex-and-biblibre-join-their-strength-to-propose-open-source-solutions-to-spanish-libraries/


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Search error

[Paul Hoffman]

On Tue, Jun 05, 2018 at 03:15:37PM +0530, Thirunagalingam S.S. wrote:
> We are from India. We are using 3.20.08.000 on Ubuntu server. We encounter
> the below mentioned error when we search the catalogue.
> 
> Software error:
> 
> Illegal division by zero at
> /usr/share/koha/intranet/cgi-bin/catalogue/search.pl line 631.
> 
> For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
> 
> 
> Need help urgently.

Can you please post the output of this command?

cat -n /usr/share/koha/intranet/cgi-bin/catalogue/search.pl | sed -n 620,642p

Thank you,

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Hindi books

[Paul Hoffman]

On Fri, Jun 01, 2018 at 01:28:29PM +0530, takan bhatt wrote:
> We have huge collection of Hindi, Gujarati and Sanskrit Books. i want to
> catalog it in Roman Script only. But along with that we would like to
> provide them facilities to search in Hindi or Gujarati script so what are
> the solution in koha

I'm not an expert, but this seems difficult.  I believe the only 
feasible way to do this is to transliterate the search terms the user 
provides from Nagari to Roman script before building the query that 
Zebra performs.  (I presume you're using Zebra rather than 
Elasticsearch.)

I would put the custom code in C4::Search::buildQuery, which (in our 
Koha instance) would be around line 1545 of the file /usr/share/lib/

1531  # Form-based queries are non-nested and fixed depth, so we can easily 
modify the incoming
1532  # query operands and indexes and add stemming, truncation, field 
weighting, etc.
1533  # Once we do so, we'll end up with a value in $query, just like if we 
had an
1534  # incoming $query from the user
1535  else {
1536  $query = ""
1537; # clear it out so we can populate properly with 
field-weighted, stemmed, etc. query
1538  my $previous_operand
1539;# a flag used to keep track if there was a previous 
query
1540 # if there was, we can apply the current operator
1541 # for every operand
1542  for ( my $i = 0 ; $i <= @operands ; $i++ ) {
1543
1544  # COMBINE OPERANDS, INDEXES AND OPERATORS
1545  if ( $operands[$i] ) {
1546  $operands[$i]=~s/^\s+//;
1547
1548# A flag to determine whether or not to add the index 
to the query
1549  my $indexes_set;


I would start by adding a line like this between lines 1545 and 1546:

$operands[$i] = _transliterate_nagari($operands[$i]);

Write the function _transliterate_nagari and put it somewhere convenient 
-- perhaps at the end of /usr/share/koha/lib/C4/Search.pm:

sub _transliterate_nagari {
local $_ = shift;
s/(\p{Script:Gujarati}+)/_transliterate_gujarati($1)/xg;
s/(\p{Script:Devanagari}+)/_transliterate_devanagari($1)/xg;
return $_;
}

(I don't think that's quite right -- I've never used \p{Script:foo} before.)

Then figure out how to do the actual transliteration and write these 
functions:

sub _transliterate_gujarati {
...
}
sub _transliterate_devanagari {
...
}

Perl modules you might use for transliteration include Lingua::Translit 
and Lingua::Deva:

https://metacpan.org/pod/Lingua::Translit
https://metacpan.org/pod/Lingua::Deva

You'll need to use the same transliteration scheme when cataloging, of 
course, or the transliterated search terms won't match the terms in the 
Zebra index.  Are you planning to use IAST?

https://en.wikipedia.org/wiki/International_Alphabet_of_Sanskrit_Transliteration

Good luck!!

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Introduction / Problem with bulk import

[Paul Hoffman]

Willkommen, Markus!

On Fri, May 25, 2018 at 09:04:56AM +0200, Markus Becker wrote:
> - Third, i have a problem with the bulk-import of MARC21XML-Records to
> Koha and i hope, someone can give me a little hint (technical details
> of the Koha-installation below):
> 
> When i try to import the MARC21XML-File with the bulkmarcimport.pl via
> console (following
> http://kohageek.blogspot.de/2016/05/bulk-marc-import-using-command-line.html),
> i get the following error:
> 
> > ..Use of uninitialized value in concatenation (.) or string at
> > /usr/share/perl5/MARC/File/XML.pm line 397,  chunk 5.
> >
> > 2 MARC records done in 0.16786003112793 seconds
> 
> The 2 MARC records were *not* imported.
> 
> The error is occurring with MARC21XML-files created with my own
> conversion-script and with files exported from Koha itself.
> 
> Any hints for me?

It sounds as though the file you are trying to import is not a 
well-formed XML document; it may be truncated in the middle of a record.  
Can you post it for us to look at?  What XML library does your 
conversion script use?

Alternatively, if you have installed libexpat you can use the xmlwf 
command to check that the file is well-formed.  Or try xmllint if you 
have installed libxml.  For example:

    xmlwf FILE
xmlwf -n FILE
xmllint --noout FILE

Paul.

-- 
Paul Hoffman <p...@flo.org>
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha 18.05.00 released

[Paul Poulain]

Thanks for your (hard) work.

Fun fact: Jonathan is a Belgium guy, living in Argentina and funded by a 
French, an USA and a UK company for his community work.



Le 24/05/2018 à 20:04, Jonathan Druart a écrit :

Hello everybody,

It is with great pleasure that the Koha community announces the release of
Koha 18.05, a major release of the Koha open source integrated library
system.

Read the full release notes here:
https://koha-community.org/koha-18-05-released/

If you do not usually read the release notes, you should at least read the
new "Important notes" section at the top.

The Debian packages for this new version will be available soon. Stay tuned!

They are supposed to work out-of-the-box on:
* Debian Jessie (8)
* Debian Stretch (9)
* Ubuntu Xenial (16.04 LTS)
And should work without too much trouble under Ubuntu Bionic (18.04 LTC),
check the install wiki page for more information.

Cheers,
Jonathan
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Help Installing Plack on Koha 17.11

[Paul A]

On 2018-05-01 05:37 PM, Mason James wrote:

On 2/05/18 9:11 am, Mason James wrote:

[snip]

aah, false alarm... :)

# aptitude why  libcgi-emulate-psgi-perl
i   koha-common   Depends    starman


Yup -- we're running (testing Ubuntu 18.04) into the same sort of 
problem. Apparently (could be wrong) Starman is a plack specific web 
server. We have been running Apache for 25 years, know it, and are happy 
with it. Not sure why Koha might (big question mark) be bi-forking to 
something different.


Perhaps this thread should be moved to devel?

Best -- Paul


i A starman   Depends    libplack-perl
i A libplack-perl Recommends libcgi-emulate-psgi-perl

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Anonymous Search History

[Paul A]

On 2018-04-30 11:05 AM, Caroline Cyr-La-Rose wrote:

Hi All,

I'm trying to figure out the search_history table in Koha. Are anonymous 
OPAC searches ever added to that table? 


A word of caution about "anonymous searches" and whether (or not) you 
use a robots.txt file on your server (we limit to just a few search 
engines, and have found ourselves obliged to "deny" at firewall level 
Baidu and a couple of other abusive spiders.)


We still get +/- 300,000 "searches" per day and have written, totally 
separately from Koha, an analytical tool at apache log level. It is 
somewhat useful, but only after massaging the results to eliminate 
google, other "permitted", and "rogue" (do not respect robots.txt but 
are not yet in 'deny') search engines.


I would however strongly encourage your IT team to do something similar. 
The number of abusive WordPress (wp) and .php crack attempts is an 
eye-opener. Won't help your librarians, but is educational for today's 
web. We do *not* record these results in the Koha db, which might well 
get swamped, or worse, DDoS'd.


YMMV.

Best -- Paul



My EnableOpacSearchHistory
syspref is set to "Keep" and my AnonymousPatron syspref is set to 21. I 
see in the C4::Search::History that if a user is not logged in, the 
search history is saved in a cookie. But is it ever saved in the database?


I'd like to know what words patrons use when they are searching, 
regardless of if they are logged in or not.


Thanks!

Caroline Cyr La Rose, MLIS
Head of training and support, inLibro

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha





---
Naval Marine Archive : The Canadian Collection
205, Main Street, Picton, Ontario, K0K 2T0, Canada
Telephone: 1 613 476 1177
http://navalmarinearchive.com
Canadian Charitable Organization 88721 9921 RR0001
Dedicated to maritime conservation and education.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] OAI Harvesing - 952 c - Shelving location | filed

[Paul A]

On 2018-04-26 03:50 PM, Mohamed Fekry Negm wrote:
We are trying to view 952 c - Shelving location in harvesting data, but we can't harvest any data from  952 filed, any suggestions 


What is the result of the MySQL query:

SELECT location, COUNT(location) AS location_count FROM items GROUP BY 
location;


Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Items held by more than one branch

[Paul Hoffman]

On Mon, Apr 23, 2018 at 09:19:10AM -0400, Cab Vinton wrote:
> Trying to write a report that will provide details for items held by
> more than one branch, with separate output for each library's item.

Put the HAVING clause inside a subquery that determines which bibs' 
items should be included -- something like this (untested):

SELECT b.biblionumber, i.homebranch, t.isbn, b.title, b.author, i.ccode, i.itype
FROM items i
LEFT JOIN biblio b USING (biblionumber)
LEFT JOIN biblioitems t USING (biblionumber)
WHERE i.itemlost=0 AND i.withdrawn=0
AND b.biblionumber IN (
SELECT b.biblionumber
FROM items i
LEFT JOIN biblio b USING (biblionumber)
WHERE i.itemlost=0 AND i.withdrawn=0
HAVING COUNT(i.itemnumber) > 1
)
ORDER BY b.title

That's a bunch of data for all items (not lost or withdrawn) on bibs 
that have more than one item (not lost or withdrawn).

HTH,

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] bulkmarcimport.pl AND -match= fails when trying to import (bibliographic) records

[Paul Hoffman]

On Wed, Mar 28, 2018 at 04:35:30PM -0400, Paul Hoffman wrote:
> On Wed, Mar 28, 2018 at 04:58:30PM -0300, Nicolas Rucks wrote:
> > Hello again! Maybe this too easy, or too difficult, maybe I am missing a 
> > point.
> > As I could manage to understand, bulkmarcimport.pl requieres "-match="  
> > with a comma (,)
> > 
> > (From bulkmarcimport.pl DESCRIPTION:)
> > -match=
> > FIELD matchindex,fieldtomatch 
> > 
> > Could anybody show me a concrete example of "matchindex" value? how should 
> > the command be? 
> 
> The part before the comma has to be a field name, not a Z39.50 BIB-1 USE 
> attribute number.  So, for example, using ISBNs would be like this:
> 
> -match=isbn,020a
> 
> I figured out the field name for 035 $a once but have forgotten.  
> control-number, maybe:
> 
> -match=control-number,035a
> 
> No, that doesn't seem to be it.  Argh.  I'll dig around in the Z39.50 
> config files.

It's Other-control-number:

-match Other-control-number,035a

Or at least I can search using that field name to find things by OCLC 
number.  On the other hand, that appears to index 035 $z as well as 035 
$a -- that could be a problem, since $z contains cancelled or invalid 
numbers.

Here's how I found it:

# fgrep 035 /etc/koha/zebradb/*/*/biblios/record.abs
/etc/koha/zebradb/marc_defs/marc21/biblios/record.abs:melm 035$a  
Other-control-number
/etc/koha/zebradb/marc_defs/marc21/biblios/record.abs:melm 035$z  
Other-control-number
/etc/koha/zebradb/marc_defs/marc21/biblios/record.abs:melm 035
Other-control-number
/etc/koha/zebradb/marc_defs/normarc/biblios/record.abs:#melm 035   
Local-number,Identifier-standard

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] bulkmarcimport.pl AND -match= fails when trying to import (bibliographic) records

[Paul Hoffman]

On Wed, Mar 28, 2018 at 04:58:30PM -0300, Nicolas Rucks wrote:
> Hello again! Maybe this too easy, or too difficult, maybe I am missing a 
> point.
> As I could manage to understand, bulkmarcimport.pl requieres "-match="  with 
> a comma (,)
> 
> (From bulkmarcimport.pl DESCRIPTION:)
> -match=
> FIELD matchindex,fieldtomatch 
> 
> Could anybody show me a concrete example of "matchindex" value? how should 
> the command be? 

The part before the comma has to be a field name, not a Z39.50 BIB-1 USE 
attribute number.  So, for example, using ISBNs would be like this:

-match=isbn,020a

I figured out the field name for 035 $a once but have forgotten.  
control-number, maybe:

-match=control-number,035a

No, that doesn't seem to be it.  Argh.  I'll dig around in the Z39.50 
config files.

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Numeric subfield in framework

[Paul A]

On 2018-03-16 10:59 AM, Narcis Garcia wrote:

Thanks; I didn't see tag 300.a


It's a standard bibliographic entry for cataloguing, used by all major 
libraries.



Applying replacement.
About JavaScript, let's see how can it be implemented consistently in Koha.

I'm really surprised Koha seems not having implemented data types
(numeric, boolean, string, binary, date/time...).


Koha *does* implement data types, where required by cataloguing rules 
and conventions (and by internal db constraints.) Tag 300$a is *not* an 
integer by any stretch of anybody's imagination.


This list is here to help you. You might like to explain which version 
of Koha you are implementing, and which library you are working for. 
That would assist the Koha community in giving you the best possible advice.


You give the impression (y disculpame si estoy en error) that you have 
done very little MARC cataloguing. I might suggest that you look at 
records from Library of Congress, the British Library, Library Archives 
Canada, etc. particularly via Z39.50, or through the web interface to 
WorldCat (OCLC).  Koha is very good at "compliance" -- but does allow 
flexibility for you to go off on a tangent and "reinvent the wheel" if 
you have "non-industry / non-professional / specialized / amateur" 
requirements.


Amicalmente -- Paul






El 16/03/18 a les 15:31, Paul A ha escrit:

On 2018-03-16 06:00 AM, Narcis Garcia wrote:

I'm editing subtags in a MARC21 framework, and trying to use 302.a for
book's pages number.
At Tag subfield structure -> Edit -> Other options; how can I set
authorized value to be only a positive integer number?


Javascript *might* allow you to limit to 'a positive integer', but why?

First, tag 302 is obsolete (so LoC, if you accept them as properly
reflecting MARC21 status, do not supply suggestions.)

Secondly, the number of pages in a bibliographic record are normally
recorded in 300$a - "Extent", described as "Number of physical pages,
volumes, cassettes, total playing time, etc., of of each type of unit."

We often have entries such as:
300 ##$axii, 352, [8 advert.] p.

LoC <http://www.loc.gov/marc/bibliographic/bd300.html> give additional
examples such as:
300 ##$a1 videocassette of 1 (Beta) (30 min.)

which might answer your follow-up email.

Best -- Paul

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Numeric subfield in framework

[Paul A]

On 2018-03-16 06:00 AM, Narcis Garcia wrote:

I'm editing subtags in a MARC21 framework, and trying to use 302.a for
book's pages number.
At Tag subfield structure -> Edit -> Other options; how can I set
authorized value to be only a positive integer number?


Javascript *might* allow you to limit to 'a positive integer', but why?

First, tag 302 is obsolete (so LoC, if you accept them as properly 
reflecting MARC21 status, do not supply suggestions.)


Secondly, the number of pages in a bibliographic record are normally 
recorded in 300$a - "Extent", described as "Number of physical pages, 
volumes, cassettes, total playing time, etc., of of each type of unit."


We often have entries such as:
300 ##$axii, 352, [8 advert.] p.

LoC <http://www.loc.gov/marc/bibliographic/bd300.html> give additional 
examples such as:

300 ##$a1 videocassette of 1 (Beta) (30 min.)

which might answer your follow-up email.

Best -- Paul

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] DNS for OPAC

[Paul A]

On 2018-03-09 02:15 AM, Ma. Victoria H. Silva-Manuel wrote:

Hi.

Our library has a website which feature our OPAC, but it shows the IP
address.
Is it possible to set up a domain name for OPAC using our website's domain
name?
For example, our website is "library.org", can we make our OPAC domain name
"library.org/opac"?
We host Koha and our website is being host by web host provider.


It would probably be easier to ask your web host provider to redirect 
the DNS (your IP addresss) as "opac.library.org" -- technically it's 
trivial, but they might have policy constraints particularly for email.


Best -- Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] DDoS attack on memcached

[Paul A]

On 2018-02-28 01:47 PM, Chris Cormack wrote:

That will work, however unless you have configured your memcached server to 
listen on an external IP it will only be listening on localhost. It's worth 
checking both though.


and/or block at border -- there's an up-tick in attempts. In the last 
few minutes:


Feb 28 14:05:20 Wed Feb 28 14:05:11 2018 router2 System Log: Blocked 
incoming UDP packet from 185.94.111.1:52499 to 70.52.***.***:11211
Feb 28 14:07:06 Wed Feb 28 14:06:59 2018 router2 System Log: Blocked 
incoming UDP packet from 46.243.189.105:37750 to 70.52.***.***:11211


Best -- P.


Chris

On 1 March 2018 2:55:56 AM NZDT, Mark Alexander  wrote:

Apparently, a bug in memcached (which we use in Koha) causes it to be
used an intermediary in a DDoS attack:

https://arstechnica.com/information-technology/2018/02/in-the-wild-ddoses-use-new-way-to-achieve-unthinkable-sizes/

I'm not an expert on this kind of thing by any means, but judging
from this:

  https://github.com/memcached/memcached/wiki/ReleaseNotes156

It seems that we can disable the attack by preventing memcached from
listening on a UDP port.  I was able to do this by adding the
following lines to /etc/memcached.conf:

  # Disable UDP
  -U 0

Then restarted memcached and apache2.

My questions for the experts: Is this the correct approach?  Is it even
necessary?
Is there more we should do?
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Removing of syspref checkdigit

[Paul Poulain]

You probably already have checked, but hea says that no-one hea-ing is 
using it : https://hea.koha-community.org/systempreferences



Le 28/02/2018 à 14:22, Jonathan Druart a écrit :

Hi all,

I proposed on bug 20264 to remove the syspref "checkdigit".
If you are using it please tell us that it is still in used.
Without answer it will be removed from 18.05

Regards,
Jonathan
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Regarding SMS Setting in KOHA

[Paul Hoffman]

Do you have any specific questions?  Have you encountered any problems?  
Please tell us more so we can help you.

Paul.

On Mon, Feb 26, 2018 at 03:27:20PM +0530, Lalit Thakur wrote:
> Sir
> Pls. guide me Regarding SMS Setting in KOHA.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cronjob Settings Help ?

[Paul Hoffman]

I certainly didn't mean to be objectionable.  Satish, if my message 
seemed harsh I am truly sorry.

Indranil, I agree completely with your point that Indian English is no 
better or worse than other forms of English, e.g., my own American 
English, or any other language.

Paul.

On Fri, Feb 09, 2018 at 08:25:01PM +0530, Indranil Das Gupta wrote:
> Hi Paul,
> 
> On 09-Feb-2018 7:49 PM, "Paul Hoffman" <p...@flo.org> wrote:
> 
> On Fri, Feb 09, 2018 at 05:34:30PM +0530, SATISH wrote:
> > What is the correct procedure to use cronjobs for sending emails.
> 
> Please resend your message with all the typos removed -- it's very
> difficult to help when there are so many stray asterisks, quotes, etc.
> 
> 
> I find you reply to the OP objectionable.
> 
> Satish is not a native speaker of English.
> 
> Plus there are certain turns of phrase and writing styles that are Indian
> English.
> 
> Just because these are different from what you are accustomed to, does not
> essentially make them wrong.
> 
> Regards,
> Indranil.
> 
> 
> 
> 
> Paul.
> 
> --
> Paul Hoffman <p...@flo.org>
> Software Manager
> Fenway Library Organization
> 550 Huntington Ave.
> Boston, MA 02115
> (617) 442-2384 (FLO main number)
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cronjob Settings Help ?

[Paul Hoffman]

On Fri, Feb 09, 2018 at 05:34:30PM +0530, SATISH wrote:
> What is the correct procedure to use cronjobs for sending emails.

Please resend your message with all the typos removed -- it's very 
difficult to help when there are so many stray asterisks, quotes, etc.

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] error while installation

[Paul Hoffman]

On Thu, Feb 08, 2018 at 03:57:43AM -0500, takan bhatt wrote:
> I am geeting this kind of error
> Err:129 http://ftp.us.debian.org/debian stretch/main i386 perl-doc all
> 5.24.1-3+deb9u2
>   400  Bad Request [IP: 64.50.236.52 80]

I'm sorry you're having difficulties.  You'll have to give us more 
information about what you're doing and what's going wrong, however -- 
we can't read your mind.  :-)

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] ailed to load external entity "/etc/koha/sites/-/koha-conf.xml

[Paul Hoffman]

On Thu, Feb 08, 2018 at 04:43:30AM -0500, takan bhatt wrote:
> after installation over I am getting this msg
> 
> ailed to load external entity "/etc/koha/sites/-/koha-conf.xml

It sounds like you accidentally gave your Koha instance the name "-".  
Can you please tell us which instructions you were using?

Also, what is the output of the following command?

ls -l /etc/koha/sites

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] LDAP Setting on 17.05=Koha

[Paul Hoffman]

I would start by making sure that Koha can connect to the relevant port 
on your LDAP server.  If you have OpenSSL installed, you can check it 
like this:

$ openssl s_time -connect 192.168.1.12:636 -time 1

If it prints a line or two and then nothing else happens, it's not able 
to connect.

Paul.

On Wed, Feb 07, 2018 at 06:34:36PM +0100, Hughes Dimka wrote:
> Hello All,
> 
> I really need help, i have been trying to get koha ldap to work on a
> netword in which i have windows Ad and the linux on a virtual box.
> 
> Below is my settings for ldap.
> 
> /usr/share/koha/misc/koha-install-log
>  1
>  
> ldaps://192.168.1.12
> OU=AO LAGOS,DC=NGFLF,DC=ALUKO-OYEBODE,DC=COM
> CN=citrixadmin,OU=OTHER USERS,OU=USER ACCOUNTS,OU=AO
> LAGOS,DC=NGFLF,DC=ALUKO-OYEBODE,DC=COM
> converge1@
> 1 
> 1 
> 1
> %s...@lagjurdcs01.ngflf.aluko-oyebode.com
>  
> 
> 
> 
> 
>  Aluko & Oyebode 
> Ikoyi
>  920011 
>  001 
> 
> 001
> BS
> 
> 
> 
> 
> 
> 
> 
> To be honest, i have been on this issues of authentication using LDAP and i
> have reached a point that i really need help. Do i have to configure
> openldap client on the ubuntu server???
> 
> 
> -- 
> Hughes Dimka
> Hopewell Solutions Services Nigeria Ltd
> No.15 Adekunle Kuye Street, Off Agbonyin Street, Off Adelabu Street,
> Surulere,Lagos State
> Nigeria
> tel: +2348066951910
> email: hdi...@gmail.com
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha without a2dismod mpm_event or Koha php-fpm on the same box?

[Paul A]

On 2018-02-04 08:20 PM, SuperThin wrote:

Hello Everybody,

In the past, I installed a Koha running out of Ubuntu 16.04. Everything is
OK. But, Koha cannot use as CMS to interact with readers as my expectation.
So, I installed Drupal CMS. The problem:

- Drupal is recommended run with PHP 7.1
- PHP 7.1 will run well with php-fpm
- php-fpm cannot enable with mpm_prefork, but mpm_event
- mpm_event cannot play with itk
- Without itk, AssignUserID cannot be accepted by Apache 2.4

How can I run Koha as www-data user, not koha instance user? Or how to
permit AssignUserID with without mpm_prefork, mpm_itk?


As a reference point, we run Koha and Drupal on separate servers -- 
problem solved (but I'm not saying it can't be done on one and the same 
server...)


Paul
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Bare Bones Import and Merge with Card Data

[Paul Hoffman]

On Thu, Jan 25, 2018 at 11:09:47AM -0500, Alvin W. wrote:
> I've setup a new Koha on an Ubuntu server and am preparing my initial
> upload of data to populate it. I have a file of bare-bones data
> 
> ISBN
> Title
> Author
> 
> I've been working on the assumption that by using ISBN I can collect the
> rest of the data from z39.50 servers.

Maybe for most records, but the hard part may be identifying the ones 
that you don't find a match for and then dealing with them.

> I have figured out how to run a z39.50 search from inside Koha and I have
> been able to merge that with my items. But I haven't seen any way to
> automate that in some sort of batch run for all the items.
> 
> Is it possible to automate the z39.50 search & merge inside Koha?

That would probably be a *lot* of work.

> Or would the better approach be to use a z39.50 client --before-- loading
> the data into Koha and when I build full-content records for the import.

Yes, definitely!

> I've looked at z39.50 client software and almost all of it is either not
> supported, not found, or very, very old -- one link said it was for Windows
> 95!

Index Data's YAZ toolkit is the gold standard for Z39.50 client software:

http://www.indexdata.com/yaz/

I use the Perl module ZOOM that's built on top of YAZ:

https://metacpan.org/pod/distribution/Net-Z3950-ZOOM/lib/ZOOM.pod

> So -- to add card catalog/Marc data to complete my bare bones list -- can
> it be done in Koha or should I build those record before the Import?
> 
> If before the import, can anyone recommend a z39.50 client?

If you can install YAZ and ZOOM then I have a Perl script (zsearch, 
attached) that you can feed a file of PQN-style (Prefix Query Notation) 
queries and get (some) MARC records back.  Since each query is a simple 
ISBN search, you can do it all from the command line -- something like 
this:

### 1. Prepare a file of PQN queries:
$ awk '{print $1}' isbns.txt | tr -dc 0-9Xx | sed 's/^/@attr 1=7 /' > 
searches.pqn

### 2. Run searches on your favorite Z39.50 server and save the first 
###matching MARC bib record for each ISBN:
$ zsearch -h HOST -p PORT -d BASE -m 1 < searches.pqn > found.mrc 2> search.log

### 3. Sanity check -- compare the number of MARC records to the number 
###of queries:
$ perl -0x1d -ne 'END { print "$. records\n" }' found.mrc
$ wc -l searches.pqn

Whichever way you end up doing this, good luck!

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
#!/m1/shared/bin/perl

use strict;
use warnings;

use ZOOM;
use Time::HiRes qw(sleep);
use Getopt::Long
qw(:config posix_default gnu_compat require_order bundling no_ignore_case);

my $host = 'localhost';
my $port = 7091;
my $dbname;
my $preferred_record_syntax = 'usmarc';
my $charset = 'UTF-8';
my $delay = 0.1;
my $randomize;
my ($verbose, $silent);
my $fetch_limit = 1;
my $count_only;
my $die_if_over_limit;
my $die_on_error;
my $die_if_not_found;
my $esn;
my $err;
my %options;

GetOptions(
'h|host=s' => sub { $host = $_[1]; $dbname = $1 if $host =~ s{/(.+)$}{}; 
$port = $1 if $host =~ s/:(\d+)$//; },
'p|port=s' => \$port,
'A|authenticate=s' => sub { set_authentication($_[1]) },
'd|database=s' => \$dbname,
'x|preferred-record-syntax=s' => \$preferred_record_syntax,
'c|charset=s' => \$charset,
'f|from-file=s' => sub { open STDIN, '<', $_[1] or die "Can't open $_[1]: 
$!" },
'v|verbose' => \$verbose,
's|silent' => \$silent,
'k|delay=f' => \$delay,
'r|randomize-delay' => \$randomize,
'K|no-delay' => sub { $delay = 0 },
'm|fetch-limit=i' => \$fetch_limit,
'M|hard-fetch-limit=i' => sub { $fetch_limit = $_[1]; $die_if_over_limit = 
1 },
'n|count-only' => \$count_only,
'E|die-on-error' => \$die_on_error,
'N|die-if-not-found' => \$die_if_not_found,
'O|worldcat=s' => sub {
($host, $port, $dbname) = ('zcat.oclc.org', 210, 'OLUCWorldCat');
set_authentication('@'.glob('~/.oclcauth/'.$_[1]));
},
'e|element-set-name=s' => \$esn,
) or exit usage();

$dbname = 'voyager' if $host eq 'localhost' && !defined $dbname;

my $get_next_query;
if (@ARGV) {
$get_next_query = sub { shift @ARGV };
}
else {
$get_next_query = sub { my $b = ; chomp $b if defined $b; $b };
}

binmode STDOUT;

my $conn = ZOOM::Connection->new(
$host,
$port,
defined($dbname) ? (databaseName => $dbname) : (),
%options,
);

$conn->option('preferredRecordSyntax' => $preferred_record_syntax);
$conn->option('charset' => $charset);
$conn->option('elementSetName' => $esn) if defined $esn;

my $found = 0;
my $not_found = 0;
my $truncated = 0;
my $errors = 0;
my $skipped = 0;

my $exiting;
my $i = 0;

while (defined(my $query = $

[Koha] Hackfest in Marseille, registrations open !

[Paul Poulain]

Hello everyone,

As already announced, the next Koha hackfest in Marseille will be in 
March, 12th-16th. Registrations are open !!!


Should I explain what is the hackfest ?

OK, for newbies, I explain.

That's a week for anyone interested in being involved into Koha. About 
50 persons, librarians and developers, from France and other countries, 
meet to:


 * meet
 * test
 * document
 * translate
 * patch
 * talk
 * share
 * show
 * try
 * miss ... and ... retry
 * discuss how to conquer the world (at least libraries...)
 * eat and drink (OK, drink, it's after day-work. And it's not mandatory)

The FAQ:

*Q= what are the conditions to come ?*
A= none, except wanting to contribute to Koha

*Q= What is the cost ?*
A= it's free (but BibLibre does not pay for traveling fees, hotel, or food)

*Q= where does it take place ?*
A= Marseille, 108 rue Breteuil, in BibLibre office. We provide coffee, 
desk, chairs, internet, video-projectors and cookies (many people come 
with their local candies)


*Q= can I come only for a few days ?*
A= yes, but at least 2 days, in just one day, no time do contribute 
anything.


*Q= I need an official letter*
A= Just drop me an email, I'll send one

*Q= I have no laptop*
A=  tricky... we don't have any spare laptop, and it's hard to 
contribute without laptop...


*Q= how to register ?*
A= easy : drop me an email

*Q= What about hotel, transportation,...*
A= You'll be added to a Google doc when you register.

*Q= I've heard about a cheese lunch, can you explain ?*
A= lunches are organized by BibLibre, in our office (there's no 
restaurant large enough in the area), and each lunch has it's own theme. 
The legendary "cheese lunch" includes 30+ different french cheese, in a 
huge buffet (with some salads...). So you'll discover a part of French 
gastronomy. This year, it will be tuesday 13th (I've been asked a few 
times: "when is the cheese lunch, I can't be here the whole week, so I 
want to be here for the cheese")


*Q= I'm veggie, can you take care of me ?*
A= yes, for sure. Just tell me when you register

*Q= I'm vegan, can you take care of me ?*
A= sorry, but no, too complex. You'll be on your own. But you can eat 
with us, welcome.


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] HTML5 video embedding returns software error

[Paul A]

On 2018-01-03 10:36 AM, Caroline Cyr-La-Rose wrote:

Hello all,

I'm trying to test the HTML5 video embedding functionality (sys pref 
HTML5MediaEnable is "in OPAC and staff client" and HTML5MediaYouTube is 
"embed").


I put a youtube link in the 856 $u and either when I try to save the 
record in Cataloguing or when I try to access the record in the OPAC, I 
get a software error :


garbage after JSON object, at character offset 57801 (before 
";ytplayer.load = fun...") at /usr/share/perl5/WWW/YouTube/Download.pm 
line 226.


This is the exact link I put in 856$u: 
https://www.youtube.com/watch?v=iTzaK4l3UJY


I'm using Koha 16.05 with Firefox Quantum.


Not sure what you may (or not) have done, but that link appears to work 
well in 856$u with FF 57.0.3 on Ubuntu. See 
<http://opac.navalmarinearchive.com/cgi-bin/koha/opac-detail.pl?biblionumber=38127>


Happy New Year to all.
Paul




What am I doing wrong?

Thanks!

Caroline Cyr La Rose, M.S.I.
Bibl. prof. / Chargée de la formation et du soutien

Tél.  : 1 (833) 465-4276
caroline.cyr-la-r...@inlibro.com <mailto:caroline.cyr-la-r...@inlibro.com>

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to secure KOHA requests

[Paul Poulain]

I'm really surprised that it fixed anything... but nevermind, the most 
important is that you're happy now ;)



Le 28/12/2017 à 14:36, wahi a écrit :

Actually I changed the permission of opac-search.pl -xr to others..


On 12/28/2017 05:33 PM, Alvaro Cornejo wrote:

Hi Wahi

What permissions did you assign to the robot.txt? I assume +r ?

Regards,

Alvaro

|-| 

Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde 
cualquier celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias 
via SMS y GPRS online

              Visitenos en www.perusms.com <http://www.perusms.com>

2017-12-28 7:31 GMT-05:00 wahi <w...@sci.am <mailto:w...@sci.am>>:

    Dear all,

    I solved the issue by changing the permission of the mentioned file.

    Thank you for all suggestions and help



    On 12/28/2017 01:49 PM, Paul Poulain wrote:

    Hi Wahi,

    Maybe a bot trying to dig your website. Have you a robot.txt
    file ?
https://wiki.koha-community.org/wiki/Koha_Tuning_Guide#Reduce_CPU_usage_of_webcrawlers:_robots.txt
<https://wiki.koha-community.org/wiki/Koha_Tuning_Guide#Reduce_CPU_usage_of_webcrawlers:_robots.txt>


    Le 27/12/2017 à 14:53, wahi a écrit :

    Dear all,

    Recently we are implemented KOHA on Ubuntu 16.04
    everything is fine, the server has 16GB RAM but we are
    always seeing lack of RAM due to this process:

    /usr/share/koha/opac/cgi-bin/opac/opac-search.pl
    <http://opac-search.pl>

    Is it something which can be restricted ? can we secure
    the requests to KOHA services using Apache ?


    Thank you very much in advance for any suggestion or help.


    Rgards,

     Wahi

    ___
    Koha mailing list http://koha-community.org
    Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
    https://lists.katipo.co.nz/mailman/listinfo/koha
<https://lists.katipo.co.nz/mailman/listinfo/koha>



    ___
    Koha mailing list http://koha-community.org
    Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
    https://lists.katipo.co.nz/mailman/listinfo/koha
    <https://lists.katipo.co.nz/mailman/listinfo/koha>






--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to secure KOHA requests

[Paul Poulain]

Hi Wahi,

Maybe a bot trying to dig your website. Have you a robot.txt file ? 
https://wiki.koha-community.org/wiki/Koha_Tuning_Guide#Reduce_CPU_usage_of_webcrawlers:_robots.txt



Le 27/12/2017 à 14:53, wahi a écrit :

Dear all,

Recently we are implemented KOHA on Ubuntu 16.04 everything is fine, 
the server has 16GB RAM but we are always seeing lack of RAM due to 
this process:


/usr/share/koha/opac/cgi-bin/opac/opac-search.pl

Is it something which can be restricted ? can we secure the requests 
to KOHA services using Apache ?



Thank you very much in advance for any suggestion or help.


Rgards,

 Wahi

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Is this plugin in use? macles.pl

[Paul Poulain]

Hi Owen,

Henri Damien wrote this cataloguing plugin for one of our customer 
(FRANTIQ) a long time ago.


They're no more our customer, I think they're supported by Tamil now, 
cc-ing Frederic



Le 15/12/2017 à 15:22, Owen Leonard a écrit :

There is a plugin for the MARC edit form called macles.pl, "Gestion
des index MACLES" I'm assuming it's specific to UNIMARC.

Does anyone know if this is still in use? It's been broken since I
think version 16.05, so I'm curious whether it can be removed.

Thanks,

   Owen



--
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 mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Configuring smtp mail server to work with Koha

[Paul Hoffman]

Javed,

(Please reply to my message rather than starting a new thread.)

Could you please repeat this, but with a somewhat different sequence of 
commands?

c C4::Letters::SendQueuedMessages
c sendmail
x \%mailcfg
$mailcfg{'debug'} = 2
r

Then post all of the output to the list.

Paul.

On Wed, Dec 06, 2017 at 11:47:18PM +0500, Javed Sahil wrote:
> Hi Paul,
> 
> here are your required results.
> 
> -- javed@iolhost:~$ koha-shell library
> [sudo] password for javed:
> library-koha@iolhost:~$ cd /usr/share/koha/bin/cronjobs
> library-koha@iolhost:/usr/share/koha/bin/cronjobs$ perl -d
> process_message_queue.pl
> 
> Loading DB routines from perl5db.pl version 1.49
> Editor support available.
> 
> Enter h or 'h h' for help, or 'man perldebug' for more help.
> 
> main::(process_message_queue.pl:32):
> 32:my $username = undef;
>   DB<1> c C4::Letters::sendqueuedmessages
> Subroutine C4::Letters::sendqueuedmessages not found.
>   DB<2> c C4::Letters::SendQueuedMessages
> C4::Letters::SendQueuedMessages(/usr/share/koha/lib/C4/Letters.pm:1032):
> 1032:my $params = shift;
>   DB<3> c sendmail
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:170):
> 170:$error = '';
>   DB<4> t
> Trace = on
>   DB<4> r
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:171):
> 171:$log = "Mail::Sendmail v. $VERSION - ". scalar(localtime())
> . "\n";
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:173):
> 173:my $CRLF = "\015\012";
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:174):
> 174:local $/ = $CRLF;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:175):
> 175:local $\ = ''; # to protect us from outside settings
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:176):
> 176:local $_;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:178):
> 178:my (%mail, $k,
> 179:$smtp, $server, $port, $connected, $localhost,
> 180:$fromaddr, $recip, @recipients, $to, $header,
> 181:%esmtp, @wanted_methods,
> 182:   );
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:232):
> 232:foreach $k (keys %mailcfg) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:233):
> 233:if ($k =~ /[A-Z]/) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:239):
> 239:while (@_) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:240):
> 240:$k = shift @_;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:241):
> 241:if (!$k and $^W) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:246):
> 246:$k = ucfirst lc($k);
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:248):
> 248:$k =~ s/\s*:\s*$//o; # kill colon (and possible spaces) at
> end, we add it later.
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:251):
> 251:$k =~ s/-(.)/"-" . uc($1)/ge;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:252):
> 252:$mail{$k} = shift @_;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:253):
> 253:if ($k !~ /^(Message|Body|Text)$/i) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:255):
> 255:$mail{$k} =~ s/\015\012?/\012/go;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:256):
> 256:$mail{$k} =~ s/\012/$CRLF/go;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:240):
> 240:$k = shift @_;
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:241):
> 241:if (!$k and $^W) {
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:246):
> 246:$k = ucfirst lc($k);
> Mail::Sendmail::sendmail(/usr/share/perl5/Mail/Sendmail.pm:248):
> 248:$k

Re: [Koha] Configuring smtp mail server to work with Koha

[Paul Hoffman]

Better yet, do this in the Perl debugger:

c C4::Letters::SendQueuedMessages
c sendmail
$mailcfg{'debug'} = 1
c

That should produce much less verbose debugging output.

Paul.

On Wed, Dec 06, 2017 at 09:39:09AM -0500, Paul Hoffman wrote:
> Javed,
> 
> Here's what I would do.  Note that the two export commands (setting the 
> environment variables PERL5LIB and KOHA_CONF) are unnecessary -- 
> koha-shell sets them for you.
> 
> $ koha-shell library
> $ cd /usr/share/koha/bin/cronjobs
> $ perl -d process_message_queue.pl
> 
> This puts you in the Perl debugger -- you should see a bunch of text 
> ending with a prompt something like this:
> 
>   DB<1>
> 
> At the prompt, enter the command "c C4::Letters::SendQueuedMessages" -- 
> that tells the debugger to run the script, stopping when it gets to the 
> C4::Letters::SendQueuedMessages() function.  Then enter the command "c 
> sendmail" to continue up until the sendmail() function.  Then enter the 
> command "t" to turn tracing on.  Then enter the command "r" to continue 
> until the sendmail() function returns.
> 
> With any luck, somewhere in the voluminous text that flashes by will be 
> a clue that helps us solve your problem.  Copy all of the text into a 
> message to this list.
> 
> Paul.
> 
> On Wed, Dec 06, 2017 at 04:26:21PM +0500, Javed Sahil wrote:
> > Hi Pedro,
> > 
> >   I am facing a problem with koha notifications similar to that you had
> > been facing in the past, your message details at the end of this email.
> > 
> > When I use following commands.
> > 
> > 1.koha-shell library
> > 2.export PERL5LIB="/usr/share/koha/lib"
> > 3.export KOHA_CONF="/etc/koha/sites/library/koha-conf.xml"
> > 4.cd /usr/share/koha/bin/cronjobs
> > 
> > above all go fine, but when i use following command:
> > 
> > 5../process_message_queue.pl
> > 
> > this error message appears:
> > 
> > connect to localhost failed (Connection refused)
> > connect to localhost failed
> > connect to localhost failed (Connection refused) no (more) retries!
> >  at ./process_message_queue.pl line 66.
> > 
> > 
> > Then in patron accounts, email status changes to "failed".
> > 
> > Help Plz.
> > 
> > Below is your problem detail.
> > 
> > Hello,
> > 
> > I have solved the problem:
> > Sendmail.pm needs to have smtp => 'localhost' and port => 25 and the e-mail
> > notifications are now working.
> > 
> > Thank you,
> > 
> > Pedro Amorim
> > 
> > 2015-10-30 14:23 GMT-01:00 Pedro Amorim :
> > 
> > > Hello Galen,
> > >
> > > Thank you for your reply.
> > > I have changed the Sendmail.pm file to point to smtp.gmail.com instead of
> > > localhost and am now receiving these errors:
> > >
> > > # koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/
> > > process_message_queue.pl -v
> > > koha: sending email message to patron: Admin at
> > > /usr/share/koha/lib/C4/Letters.pm line 937.
> > > koha: MAIL FROM: error (530 5.7.0 Must issue a STARTTLS command first.
> > > uj4sm7521289wjc.34 - gsmtp
> > > koha: )
> > > koha: Server said: 530 5.7.0 Must issue a STARTTLS command first.
> > > uj4sm7521289wjc.34 - gsmtp
> > > koha:  at /usr/share/koha/bin/cronjobs/process_message_queue.pl line 66
> > >
> > > I do not know much about configuring mail servers, should I keep the
> > > Sendmail.pm file pointing to localhost and postfix takes care of the
> > > redirecting?
> > >
> > > Thanks again,
> > >
> > > Pedro Amorim
> > 
> > -- 
> > Regards,
> > 
> > Javed Shoukat
> > 
> > Management Trainee Officer (MTO)
> > Lahore University of
> > Management Sciences (LUMS),
> > Lahore.
> > 
> > Contact #: +92 300 6548748 <+92%20300%206548748>
> > Email: javedshoukat...@gmail.com
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> -- 
> Paul Hoffman <p...@flo.org>
> Software Manager
> Fenway Library Organization
> 550 Huntington Ave.
> Boston, MA 02115
> (617) 442-2384 (FLO main number)

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Configuring smtp mail server to work with Koha

[Paul Hoffman]

Javed,

Here's what I would do.  Note that the two export commands (setting the 
environment variables PERL5LIB and KOHA_CONF) are unnecessary -- 
koha-shell sets them for you.

$ koha-shell library
$ cd /usr/share/koha/bin/cronjobs
$ perl -d process_message_queue.pl

This puts you in the Perl debugger -- you should see a bunch of text 
ending with a prompt something like this:

  DB<1>

At the prompt, enter the command "c C4::Letters::SendQueuedMessages" -- 
that tells the debugger to run the script, stopping when it gets to the 
C4::Letters::SendQueuedMessages() function.  Then enter the command "c 
sendmail" to continue up until the sendmail() function.  Then enter the 
command "t" to turn tracing on.  Then enter the command "r" to continue 
until the sendmail() function returns.

With any luck, somewhere in the voluminous text that flashes by will be 
a clue that helps us solve your problem.  Copy all of the text into a 
message to this list.

Paul.

On Wed, Dec 06, 2017 at 04:26:21PM +0500, Javed Sahil wrote:
> Hi Pedro,
> 
>   I am facing a problem with koha notifications similar to that you had
> been facing in the past, your message details at the end of this email.
> 
> When I use following commands.
> 
> 1.koha-shell library
> 2.export PERL5LIB="/usr/share/koha/lib"
> 3.export KOHA_CONF="/etc/koha/sites/library/koha-conf.xml"
> 4.cd /usr/share/koha/bin/cronjobs
> 
> above all go fine, but when i use following command:
> 
> 5../process_message_queue.pl
> 
> this error message appears:
> 
> connect to localhost failed (Connection refused)
> connect to localhost failed
> connect to localhost failed (Connection refused) no (more) retries!
>  at ./process_message_queue.pl line 66.
> 
> 
> Then in patron accounts, email status changes to "failed".
> 
> Help Plz.
> 
> Below is your problem detail.
> 
> Hello,
> 
> I have solved the problem:
> Sendmail.pm needs to have smtp => 'localhost' and port => 25 and the e-mail
> notifications are now working.
> 
> Thank you,
> 
> Pedro Amorim
> 
> 2015-10-30 14:23 GMT-01:00 Pedro Amorim :
> 
> > Hello Galen,
> >
> > Thank you for your reply.
> > I have changed the Sendmail.pm file to point to smtp.gmail.com instead of
> > localhost and am now receiving these errors:
> >
> > # koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/
> > process_message_queue.pl -v
> > koha: sending email message to patron: Admin at
> > /usr/share/koha/lib/C4/Letters.pm line 937.
> > koha: MAIL FROM: error (530 5.7.0 Must issue a STARTTLS command first.
> > uj4sm7521289wjc.34 - gsmtp
> > koha: )
> > koha: Server said: 530 5.7.0 Must issue a STARTTLS command first.
> > uj4sm7521289wjc.34 - gsmtp
> > koha:  at /usr/share/koha/bin/cronjobs/process_message_queue.pl line 66
> >
> > I do not know much about configuring mail servers, should I keep the
> > Sendmail.pm file pointing to localhost and postfix takes care of the
> > redirecting?
> >
> > Thanks again,
> >
> > Pedro Amorim
> 
> -- 
> Regards,
> 
> Javed Shoukat
> 
> Management Trainee Officer (MTO)
> Lahore University of
> Management Sciences (LUMS),
> Lahore.
> 
> Contact #: +92 300 6548748 <+92%20300%206548748>
> Email: javedshoukat...@gmail.com
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Email status changes failed from pending

[Paul Hoffman]

On Sun, Dec 03, 2017 at 04:05:23PM +0500, Javed Sahil wrote:
> Hello everyone!
> I want koha to send emails to patrons for circulation transactions
> like check out, check in, overdue etc. I have installed postfix.
> Everything is set I can send emails from commands line.
> 
> but in patron accounts email status is "pending".
> 
> When I use following commands.
> 
> 1.koha-shell library
> 2.export PERL5LIB="/usr/share/koha/lib"
> 3.export KOHA_CONF="/etc/koha/sites/library/koha-conf.xml"
> 4.cd /usr/share/koha/bin/cronjobs
> 
> above all go fine, but when i use following command:
> 
> 5../process_message_queue.pl
> 
> this error message appears:
> 
> connect to localhost failed (Connection refused)
> connect to localhost failed
> connect to localhost failed (Connection refused) no (more) retries!
>  at ./process_message_queue.pl line 66.

It sounds as though Postfix is not listening on port 25.  Please run the 
following command (as root) and send us the output: 

    netstat -tnlp | fgrep master

And please send us the output of this command, too:

uname -a

Paul.

-- 
Paul Hoffman <p...@flo.org>
Software Manager
Fenway Library Organization
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Email message sending error in koha

[Paul Hoffman]

I am not a Koha expert -- far from it! -- but I'm guessing that you 
neglected to export the environment variable KOHA_CONF when running 
process_message_queue.pl -- if you didn't export it, then the Perl 
script you're trying to run can't "see" it.  Try this:

cd /usr/share/koha/bin/cronjobs
export KOHA_CONF=/etc/koha/sites/library/koha-conf.xml
perl -c ./process_message_queue.pl

With any luck, that will run OK without spitting out a gazillion error 
messages.

Paul.

On Thu, Nov 30, 2017 at 02:46:49PM -0400, Luis Moises Rojas wrote:
> About this issue, we got the following error when we ran:
> sudo apt-get install mailutils
> 
> 
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> P.D: we are using sudo
> 
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Thu, Nov 30, 2017 at 10:37 AM, Javed Sahil <sahil.ke.p...@gmail.com>
> wrote:
> 
> > Hi everyone!
> >
> > I have set postfix with gmail to send Email Notices for  Check In, Check
> > Out, and every transaction made in Circulation Module,
> >
> > But in user accounts Notices tab Email status is pending.
> > I want koha to send email notices immediately.
> >  But it is not sending emails.
> >
> > I have installed "mailutils" using command below:
> > *#  sudo apt-get install mailutils*
> > Everything is ok,
> > I can send emails using the command below:
> >
> > *# mail -s "This is the subject" javedshoukat...@gmail.com
> > <javedshoukat...@gmail.com> <<< 'This is the message'*
> > But notifications emails by koha are not sent,
> >
> > I have tried
> >
> >
> >
> >
> > *# PERL5LIB="/usr/share/koha/lib"#
> > KOHA_CONF="/etc/koha/sites/library/koha-conf.xml"# cd
> > /usr/share/koha/bin/cronjobs# ./process_message_queue.pl
> > <http://process_message_queue.pl>*
> >
> > it returns
> >
> > root@iolhost:/usr/share/koha/bin/cronjobs# ./process_message_queue.pl
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > unable to locate Koha configuration file koha-conf.xml at
> > /usr/share/koha/lib/C4/Context.pm line 242.
> > Use of uninitialized value in concatenation (.) or string at
> > /usr/share/koha/lib/C4/Templates.pm line 153.

Re: [Koha] Batch record modification

[Paul A]

On 2017-11-22 03:26 AM, Hugo Agud wrote:

Good morning,

we have identified a strange behaviour in Batch record modification, the
goal is to create a second 655 tag, but there is no way if there is already
one 655 tag.


How is your MARC Framework set up?

For example, we have:
655 INDEX TERM--GENRE/FORM set as repeatable
and:
subfield a	Genre/form data or focus term	Tab:6, Not repeatable, Not 
mandatory, | Authority:GENRE/FORM,


Paul


the only option is add/update and if we use that, it always replace the
entire field or it adds  a 655$a to the already exist

654_atest-654
655_aTest-655
_942126
_atest-654


Perhaps we do not know how to add a new field if already exists one


any idea?




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha