Re: [Koha] Export authorized values

[Jonathan Druart]

There are also authorised_value_categories (for the categories) and
authorised_values_branches (for the branch limitations).

*Bug 10198* - Add the ability to import and export authorized values (there
is not patch here)

On Tue, 17 Jul 2018 at 14:23 Eric Phetteplace  wrote:

> Hi Narcis,
>
> I don't think that there's a function to export the authorized values, at
> least not on the staff side of the catalog. You could always write a report
> that pulls all the data and then save it as a CSV. This is the minimal SQL
> needed to do so:
>
> SELECT *
> FROM authorised_values
> ORDER BY category
>
>
> That'll pull everything and kind of sort it into groups based on which
> value category the data belongs to.
>
> Best,
>
> ERIC PHETTEPLACE
>
> Systems Librarian
>
>
> libraries.cca.edu | vault.cca.edu | 510.594.3660
>
> 5212 Broadway, Oakland, CA 94618
> 
>
>  8th St., San Francisco, CA 94107
> 
>
> Preferred Pronoun(s): he/him
>
> :(){ :|: & };:
>
>
> On Tue, Jul 17, 2018 at 7:36 AM Narcis Garcia 
> wrote:
>
> > (Using Koha 17.11)
> > As I can do with "MARC frameworks", I want to make a backup of
> > "Authorized values".
> >
> > How can I do?
> >
> > Thank you.
> > ___
> > 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] Indicators in authorities when cataloguing a book record

[Jonathan Druart]

This behaviour has been added by
  commit 0ea53c745632e3b45bcad2d2238e4b126a323231
  Bug 14769: (Follow-up) Let blinddetail look at indicator values
If the indicators are not controlled, blinddetail should not overwrite
what the user already entered. Very strictly seen, we could say that it
is outside the scope. But it is strongly related.

It sounds like it's an expected change.


On Mon, 16 Jul 2018 at 09:50 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Actually you can type, but the field is filled with a space and has a max
> length of 1.
> To edit it you should remove the space then enter the indicator you want.
> Bug?
>
> On Mon, 16 Jul 2018 at 06:01 drojup  wrote:
>
>> Hi,
>>
>> I am using version 18.05
>>
>> Steps that reproduce the issue.
>>
>> 1) Start cataloguing a bibliographic record (default framework).
>>
>> 2) In field 100 I search for an authority and then selecting it.
>>
>> 3) The 100 field has the authority that I selected but I can't type
>> anything
>> in indicators field (in order to add an indicator that I may have forgot).
>>
>> Regards,
>>
>>
>>
>> --
>> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
>> ___
>> 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] Indicators in authorities when cataloguing a book record

[Jonathan Druart]

Actually you can type, but the field is filled with a space and has a max
length of 1.
To edit it you should remove the space then enter the indicator you want.
Bug?

On Mon, 16 Jul 2018 at 06:01 drojup  wrote:

> Hi,
>
> I am using version 18.05
>
> Steps that reproduce the issue.
>
> 1) Start cataloguing a bibliographic record (default framework).
>
> 2) In field 100 I search for an authority and then selecting it.
>
> 3) The 100 field has the authority that I selected but I can't type
> anything
> in indicators field (in order to add an indicator that I may have forgot).
>
> Regards,
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> 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] Koha 18.05.02 released

[Jonathan Druart]

Hi,

The packages for 18.05.02 will be available soon, it will be announced by
Mirko on this list.
Stay tunes!

Regards,
Jonathan

On Tue, 24 Jul 2018 at 07:35 drojup  wrote:

> Hi there,
>
> Is there any documentation about upgrading from 18.05.01 to 18.05.02
> (Ubuntu
> Server 16.04)?
>
> Regards.
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> 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] Koha 18.05.02 released

[Jonathan Druart]

Hello Narcis,

Please comment on bug 20826 with more details.

Regards,
Jonathan

On Tue, 24 Jul 2018 at 04:19 Narcis Garcia  wrote:

> [Koha 17.11.06-1 on Debian 9]
>
> $ apt update
> $ apt-cache show koha-common | grep -ie version
> Version: 18.05.01-2
> Version: 17.11.06-1
>
> $ apt full-upgrade
> The following packages were automatically installed and are no longer
> required:
> [400 packages listed]
> Use 'sudo apt autoremove' to remove them.
> The following packages will be REMOVED:
>   koha-common libhttp-oai-perl
> The following NEW packages will be installed:
>   libnet-libidn-perl libsub-quote-perl
> The following packages will be upgraded:
> apache2 [...]
> 44 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
> Need to get 43.1 MB of archives.
> After this operation, 461 MB disk space will be freed.
> Do you want to continue? [Y/n] n
>
> $ apt install koha-common
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
>
>
> El 24/07/18 a les 00:13, Michael Kuhn ha escrit:
> > Hi Martin
> >
> >> The Koha community is proud to announce the release of 18.05.02.
> >>
> >> This is a maintenance release.
> >> As always you can download the release from
> >> http://download.koha-community.org.
> >>
> >> Have a look at release post :
> >> http://koha-community.org/koha-18-05-02-released
> >> 
> >
> > Thanks!
> >
> > The correct URL to the release post Is:
> >
> > https://koha-community.org/koha-18-05-02-release/
> >
> > Best wishes:
> ___
> 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] software error

[Jonathan Druart]

The item type used by one of the item (items.itype or biblioitem.itemtype)
is not defined in the item type list.

On Wed, 11 Jul 2018 at 04:35 hira.ak...@almusnet.com <
hira.ak...@almusnet.com> wrote:

>
> Hi,
> I added an item on hold ( that was checked out) from OPAC view. It was
> appearing in the list of "holds to pull" from staff view. but when i
> checked in the item and tried to view holds again, I opened page of "holds
> awaiting pickup" it shows me software error page.
> ""
> Can't call method "description" on an undefined value at
> /usr/share/koha/intranet/cgi-bin/circ/waitingreserves.pl line 124.
>
> """
> What might be the issue and how it can be solved?
>
> Thanks
> ___
> 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] Manual for 18.05 updated (+ePub version)

[Jonathan Druart]

Hello,

The manual for 18.05 (work in progress) is available at
https://koha-community.org/documentation/
The different versions contain the last PO files from pootle.

The ePub versions are also available (not for English yet, coming soon).

The PDF versions are not available yet (see my previous email for a first
try).

We are going to try and keep up-to-date these different versions with the
work done by the translators.
Note that this 18.05 versions used the PO from the project "Manual 17.11"
in Pootle, that may be confusing (will be fixed later, any ideas?).

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

Re: [Koha] Manual 17.11 zh_TW is translated.

[Jonathan Druart]

Hi Anthony, the zh_TW is updated and available at
http://koha-community.org/manual/18.05/zh_TW/html/index.html

I noted something wrong:
https://koha-community.org/manual/18.05/zh_TW/html/01_installation.html#marc21-setup
The image is missing

On Thu, 11 Jan 2018 at 18:17 Anthony Mao <maol...@gmail.com> wrote:

> Hi Jonathan,
>
> Thanks.
> My friend told me that PDF format might take longer time than you can
> image. HTML format would be easier.
> I don't know why?
>
> 2018-01-12 0:54 GMT+08:00 Jonathan Druart
> <jonathan.dru...@bugs.koha-community.org>:
> > Hi Anthony,
> >
> > Great job!
> > Just a quick update to tell you I am working on it. I will tell you when
> it
> > is done.
> >
> > Regards,
> > Jonathan
> >
> > On Sun, 24 Dec 2017 at 02:32 Anthony Mao <maol...@gmail.com> wrote:
> >>
> >> Manual 17.11 zh_TW is translated.
> >> http://translate.koha-community.org/zh_TW/man17.11/
> >>
> >> Could someone help update this page?
> >> http://translate.koha-community.org/manual/17.11/zh_TW/html/index.html
> >>
> >> --
> >> Anthony Mao
> >> Fu Jen Catholic University, Taiwan
> >> Skype: maolins
> >> +886 2 29052334 <+886%202%202905%202334> (voice)
> >> ___
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
>
> --
> Anthony Mao
> Fu Jen Catholic University, Taiwan
> Skype: maolins
> +886 2 29052334 <+886%202%202905%202334> (voice)
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Manual 17.11 zh_TW is translated.

[Jonathan Druart]

You translated the |image|

locales/zh_TW/LC_MESSAGES/01_installation.po:msgid "|image1174|"
locales/zh_TW/LC_MESSAGES/01_installation.po:msgstr "|圖片1174|"

It should not be translated :)

On Fri, 12 Jan 2018 at 10:02 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Anthony, the zh_TW is updated and available at
> http://koha-community.org/manual/18.05/zh_TW/html/index.html
>
> I noted something wrong:
> https://koha-community.org/manual/18.05/zh_TW/html/01_installation.html#marc21-setup
> The image is missing
>
>
> On Thu, 11 Jan 2018 at 18:17 Anthony Mao <maol...@gmail.com> wrote:
>
>> Hi Jonathan,
>>
>> Thanks.
>> My friend told me that PDF format might take longer time than you can
>> image. HTML format would be easier.
>> I don't know why?
>>
>> 2018-01-12 0:54 GMT+08:00 Jonathan Druart
>> <jonathan.dru...@bugs.koha-community.org>:
>> > Hi Anthony,
>> >
>> > Great job!
>> > Just a quick update to tell you I am working on it. I will tell you
>> when it
>> > is done.
>> >
>> > Regards,
>> > Jonathan
>> >
>> > On Sun, 24 Dec 2017 at 02:32 Anthony Mao <maol...@gmail.com> wrote:
>> >>
>> >> Manual 17.11 zh_TW is translated.
>> >> http://translate.koha-community.org/zh_TW/man17.11/
>> >>
>> >> Could someone help update this page?
>> >> http://translate.koha-community.org/manual/17.11/zh_TW/html/index.html
>> >>
>> >> --
>> >> Anthony Mao
>> >> Fu Jen Catholic University, Taiwan
>> >> Skype: maolins
>> >> +886 2 29052334 <+886%202%202905%202334> (voice)
>> >> ___
>> >> Koha mailing list  http://koha-community.org
>> >> Koha@lists.katipo.co.nz
>> >> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
>>
>> --
>> Anthony Mao
>> Fu Jen Catholic University, Taiwan
>> Skype: maolins
>> +886 2 29052334 <+886%202%202905%202334> (voice)
>>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Manual 17.11 zh_TW is translated.

[Jonathan Druart]

You should fix these 3:
zh_TW/LC_MESSAGES/01_installation.po:msgstr "|圖片1173|"
zh_TW/LC_MESSAGES/01_installation.po:msgstr "|圖片1174|"
zh_TW/LC_MESSAGES/03_tools.po:msgstr "|iamge1238|"


On Fri, 12 Jan 2018 at 10:10 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> You translated the |image|
>
> locales/zh_TW/LC_MESSAGES/01_installation.po:msgid "|image1174|"
> locales/zh_TW/LC_MESSAGES/01_installation.po:msgstr "|圖片1174|"
>
> It should not be translated :)
>
>
> On Fri, 12 Jan 2018 at 10:02 Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Hi Anthony, the zh_TW is updated and available at
>> http://koha-community.org/manual/18.05/zh_TW/html/index.html
>>
>> I noted something wrong:
>> https://koha-community.org/manual/18.05/zh_TW/html/01_installation.html#marc21-setup
>> The image is missing
>>
>>
>> On Thu, 11 Jan 2018 at 18:17 Anthony Mao <maol...@gmail.com> wrote:
>>
>>> Hi Jonathan,
>>>
>>> Thanks.
>>> My friend told me that PDF format might take longer time than you can
>>> image. HTML format would be easier.
>>> I don't know why?
>>>
>>> 2018-01-12 0:54 GMT+08:00 Jonathan Druart
>>> <jonathan.dru...@bugs.koha-community.org>:
>>> > Hi Anthony,
>>> >
>>> > Great job!
>>> > Just a quick update to tell you I am working on it. I will tell you
>>> when it
>>> > is done.
>>> >
>>> > Regards,
>>> > Jonathan
>>> >
>>> > On Sun, 24 Dec 2017 at 02:32 Anthony Mao <maol...@gmail.com> wrote:
>>> >>
>>> >> Manual 17.11 zh_TW is translated.
>>> >> http://translate.koha-community.org/zh_TW/man17.11/
>>> >>
>>> >> Could someone help update this page?
>>> >>
>>> http://translate.koha-community.org/manual/17.11/zh_TW/html/index.html
>>> >>
>>> >> --
>>> >> Anthony Mao
>>> >> Fu Jen Catholic University, Taiwan
>>> >> Skype: maolins
>>> >> +886 2 29052334 <+886%202%202905%202334> (voice)
>>> >> ___
>>> >> Koha mailing list  http://koha-community.org
>>> >> Koha@lists.katipo.co.nz
>>> >> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>>>
>>>
>>> --
>>> Anthony Mao
>>> Fu Jen Catholic University, Taiwan
>>> Skype: maolins
>>> +886 2 29052334 <+886%202%202905%202334> (voice)
>>>
>>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Vietnamese language choice in OPAC appears in Chinese characters

[Jonathan Druart]

It comes from this line:
installer/data/mysql/mandatory/subtag_registry.sql:VALUES ( 'vi',
'language', 'vi', '㗂越');


On Mon, 22 Jan 2018 at 05:15 Daniel Owens  wrote:

> We have used Koha in Vietnam for several years, and when the vi-VN
> locale is installed, it appears in the OPAC as Chinese characters. Not
> the actual interface, mind you, just in the language selector:
>
>  tabindex="-1" role="menuitem" class="listmenulink">㗂越
>
> That seems to be a bug to me, but maybe there is an explanation? Is
> there a way to fix it? It should be "Tiếng Việt" not "㗂越".
>
> Daniel
>
> ___
> 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] Screenshots internationalization for the manual (and acceptance tests?)

[Jonathan Druart]

Hi Éric,

The screenshot are automatically cropped, did you watch at the examples I
generated?
For each screenshots it retrieves the positions of a list of elements, so
no need to maintain or keep them up-to-date, we just need to keep the same
elements on the pages (id or class). It is the same problem of any selenium
scripts.

As I said, if you generate 1 screenshot in a generic way, it will be kept
up-to-date and for all languages. If you generate it manually, it will not.
I am sure it is less time consuming to write the 5 lines of code than take
and crop a screenshot for the 9 languages we generate the manual.

Cheers,
Jonathan

On Sun, 21 Jan 2018 at 10:37 Eric Bégin <eric.be...@inlibro.com> wrote:

> Good morning all !
>
> For me, having the screenshots in the correct language is quite important.
>
> However, having the screenshots updated every release is not necessary.
> For example, I don't mind if there is a slight difference in the
> screenshot when that difference is not related to the explained feature.
>
> Don't get me wrong, I love the idea of automating the screenshots and
> the possibilities it offers, but I believe that a lot of them will need
> to be edited afterward in order to be cropped, added overlay, and so on,
> which make the automation less appealing.  I also think that it will be
> a nightmare to maintain in the long run and making the documentation
> process even harder.
>
> The option is to generate the screenshots when we can.  Its a long
> process at first, but any body are able to take a screenshot, without
> having to code anything, which is, in my opinion, a big advantage.
>
> My 164 Satochis ($0.02) on this sunday morning :)
>
> Eric
>
> On 2018-01-19 11:29, Jonathan Druart wrote:
> > Hello everybody,
> >
> > I have spent (too much) time trying to automatically generate the
> > screenshots of the manual.
> > The idea behind that was multiple: keep the screenshots up-to-date from
> one
> > version of Koha to the others, and generate screenshots in each language
> of
> > the manual.
> > I was really excited after the first half hour when I successfully took
> my
> > first screenshot with only few lines of code.
> > But after a couple of days I realize that the task is very huge: we have
> > more than 1300 images in the manual, and I have generated only 68 so far.
> >
> > First I need to know how important is that for you. Will it really change
> > our lives to have screenshots translated in other languages (and kept in
> > sync with the interface)? How important is the value added?
> > One thing is sure: if someone wants to translate screenshots, they should
> > do it in a generic way so all languages can take advantage of it.
> >
> > The hidden added value of such mechanism is to add a huge test coverage:
> we
> > are going to make sure the screenshots can be generated in several
> > languages, catching issues we do not cover in our test suites, etc.
> > A bit of technique: the screenshots are taken using Selenium tests (which
> > we already use a bit in the test suites): it simulates a user's
> interaction
> > with the interface.
> >
> > The big problem is that, for now, only developers could help me.
> > But do not stop reading now please :)
> >
> > The code looks like that:
> > C4::Context->set_preference('SpecifyReturnDate', 1);
> > $driver->get($base_url.'circ/returns.pl');
> > screenshot("SpecifyReturnDate", { class => "yui-u first" });
> > For the "SpecifyReturnDate" screenshot, we set the syspref to 1, hit
> > returns.pl and create a screenshot from the element with a class "yui-u
> > first" (yes the element should have an id).
> > As you can imagine this one is part of the easiest ones.
> >
> > Now imagine "FineNotifyAtCheckin", we want to capture the alert box when
> > the patron has fines and returns an item.
> > The code is:
> > C4::Context->set_preference('FineNotifyAtCheckin', 1);
> > my $b = Koha::Items->find(74)->barcode;
> > issue( $patron, $b );
> > Koha::Account::Line->new({ borrowernumber => $patron->borrowernumber,
> > accountno => 1, amountoutstanding => 5 })->store;
> > checkin( $b );
> > screenshot("FineNotifyAtCheckin", { class => "dialog alert" } );
> > Koha::Account::Lines->search({ borrowernumber => $patron->borrowernumber
> > })->delete;
> > First I assume I have an item with itemnumber=74 that can be issued by a
> > given patron. I check it out and create a fine of 5. I check the item in
> > and tadaaa I can take

Re: [Koha] Screenshots internationalization for the manual (and acceptance tests?)

[Jonathan Druart]

Hi Caroline,

I am suggesting to write a (BDD) syntax to help everybody to write these
steps.
You would be able to generate the screenshots and test locally if the steps
are correct.

The syntax would look like the two examples I gave, like:
Scenario: Take a screenshot for FineNotifyAtCheckin
Given I have set the syspref FineNotifyAtCheckin to 1
And I checked an item out to a patron
And I added a fine of 5 to the patron
And I checked the item in
Then I take a screenshot of the element with the class "dialog alert"

You will not need the help of a developer to know if it does what you
expected.

Of course I know it is a big job to generate such steps for every
screenshot, but I think it is the way to go to get up-to-date (and
translated) screenshots in the long term.

I have already did the job for the image "marc21_basic_setup.png" (see the
links at the bottom of my original email) and there are no numbers or
circles. It cannot be automated.

Thanks for your answer.

Jonathan

On Mon, 26 Feb 2018 at 13:44 Caroline Cyr-La-Rose <
caroline.cyr-la-r...@inlibro.com> wrote:

> Hi Jonathan,
>
> I'm not sure I understand everything in your email. Let me know if I'm
> understanding this right. What you are asking is if we (the
> non-technical ppl) would be willing to write up "steps" for each of the
> 1300+ screenshots in the manual so that developers can translate those
> into code to automate the screenshot-taking and deploy it across all
> manuals and all languages.
>
> Do we have enough developers in the community to do that? I don't want
> to speak for the whole documentation team, but I think that if we do it
> little by little (when we review a section or sub-section for example),
> it is feasible. It might take a couple of years to go through the 1300+
> pictures, though. And we would need to have a way to know which
> screenshot has been automated and which is still manual (ideally,
> directly in the manual, maybe with a comment?).
>
> When we want to add a screenshot, let's say for a new feature, how does
> the workflow go? Do we take a manual screenshot first and write up the
> steps? Or just write the steps and wait for the developer to take the
> screenshot?
>
> What about when we want to add squares or circles to point out a
> specific button (do we do that in the manual?) or add numbers like in
> this example you sent :
>
> http://download.koha-community.org/manual/wip_screenshots/en/html/_images/marc21_basic_setup.png
> ?
>
> I hope this helps your reflection
>
> Caroline Cyr La Rose, M.L.I.S.
> 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
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha 18.05 release dates

[Jonathan Druart]

Hello everybody,

Here is the timeline I plan to follow for the 18.05 release:

* April 20 - "Soft" feature freeze, nothing big or with high risk of
side-effects will be included into the final release if not marked as
Passed QA (and the converse is false).
* April 27 - "Hard" feature freeze, nothing considered as an enhancement
will be pushed if not marked as Passed QA (exception will be made for
tests).
* May 4 - String freeze, draft of release notes published
* May 11 - Only bugfixes considered as major, critical or blocker will be
pushed
* May 22 - Final Release

Any comments or change requests?

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

Re: [Koha] Request for adding to List of Support Companies

[Jonathan Druart]

Hi Mohamed,

I do not think cross-posting to several lists is the best way to get an
answer (well apparently yes...)

Maybe you did not get a positive answer because you do not meet the few
requirements, like "link to the Koha website"?
What is your "KohaAcademic Open Sources Solutions by ALZAD" product?
It sounds very confusing to me. Did you customize a version of Koha? Are
the sources available?

Answering there questions may help you to get a positive answer (if this
list is still maintain).

Cheers,
Jonathan

On Fri, 6 Apr 2018 at 09:33 Mohamed Fekry Negm  wrote:

>
> Dear Koha Community,
>
>
>
> Kindly find below ALZAD profile for adding ALZAD company to your community
> support for Koha, please  contact me if you need any further information.
>
> Company Name:  ALZAD for Digital Archiving
>
> Contact Person: Dr. Mohamed Negm - Ms. Rasha Barakat
>
> Contact email: m.n...@alzad.ze / i...@alzad.ae
>
> Website: http://alzad.ae/
>
> Telephone: +971551224802 <+971%2055%20122%204802> - +971551224832
> <+971%2055%20122%204832>
>
> County:  United Arab Emirates
> ___
> 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] Koha 18.05 release dates

[Jonathan Druart]

I'd say it depends on the patchset/area and test coverage.
And also on the time I will be able to dedicate to code review.

On Tue, 3 Apr 2018 at 10:20 Tomas Cohen Arazi <tomasco...@gmail.com> wrote:

> Will you consider REST endpoints 'high-risk'?
>
> El mar., 3 abr. 2018 a las 10:04, Jonathan Druart (<
> jonathan.dru...@bugs.koha-community.org>) escribió:
>
>> Hello everybody,
>>
>> Here is the timeline I plan to follow for the 18.05 release:
>>
>> * April 20 - "Soft" feature freeze, nothing big or with high risk of
>> side-effects will be included into the final release if not marked as
>> Passed QA (and the converse is false).
>> * April 27 - "Hard" feature freeze, nothing considered as an enhancement
>> will be pushed if not marked as Passed QA (exception will be made for
>> tests).
>> * May 4 - String freeze, draft of release notes published
>> * May 11 - Only bugfixes considered as major, critical or blocker will be
>> pushed
>> * May 22 - Final Release
>>
>> Any comments or change requests?
>>
>> Regards,
>> Jonathan
>>
> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io <http://theke.io/>)
> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> GPG: B2F3C15F
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Need help resolving error on item search in Koha 17.11

[Jonathan Druart]

Enable Javascript (i.e. disable NoScript).

On Fri, 13 Apr 2018 at 13:47 Chris Brown  wrote:

> Hello,
>
> We are seeing the following error when doing an "item search" in Koha
> 17.11. We've tried searching on barcode and on author but always see the
> same message.
>
> Our training system (running Koha 17.05) does not show this error.
>
> Is this a bug or are we perhaps doing something wrong?
>
> Thanks!
>
> Chris Brown
>
> Software error:
>
> Unsupported format html at
> /usr/share/koha/intranet/cgi-bin/catalogue/itemsearch.pl line 42.
> ___
> 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] Request for adding to List of Support Companies

[Jonathan Druart]

On which list do you want to appear exactly?

On Fri, 6 Apr 2018 at 10:52 Mohamed Fekry Negm <m.n...@live.com> wrote:

> Hi,
>
>
> Acutely I didn't receive any email asking for list requirements, we have
> many clients using Koha and Dspace, see the below examples, I followed the
> instructions on the website, our products in ALZAD concentrate on Open
> source software, also we are working on developing new module on Koha, so
> what the requirements for adding to the list if it still exists
>
>
> https://www.almajles.gov.ae:1818/
>
>
> http://library.eda.ac.ae/
>
>
> www.uaccc.org/en/opac-search/<http://www.uaccc.org/en/opac-search/>
>
>
> http://sdr.shjlib.gov.ae:8080
>
>
>
>
>
>
> 
> From: Jonathan Druart <jonathan.dru...@bugs.koha-community.org>
> Sent: Friday, April 6, 2018 3:12 PM
> To: Mohamed Fekry Negm
> Cc: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Request for adding to List of Support Companies
>
> Hi Mohamed,
>
> I do not think cross-posting to several lists is the best way to get an
> answer (well apparently yes...)
>
> Maybe you did not get a positive answer because you do not meet the few
> requirements, like "link to the Koha website"?
> What is your "KohaAcademic Open Sources Solutions by ALZAD" product?
> It sounds very confusing to me. Did you customize a version of Koha? Are
> the sources available?
>
> Answering there questions may help you to get a positive answer (if this
> list is still maintain).
>
> Cheers,
> Jonathan
>
> On Fri, 6 Apr 2018 at 09:33 Mohamed Fekry Negm <m.n...@live.com m.n...@live.com>> wrote:
>
> Dear Koha Community,
>
>
>
> Kindly find below ALZAD profile for adding ALZAD company to your community
> support for Koha, please  contact me if you need any further information.
>
> Company Name:  ALZAD for Digital Archiving
>
> Contact Person: Dr. Mohamed Negm - Ms. Rasha Barakat
>
> Contact email: m.n...@alzad.ze / i...@alzad.ae<mailto:i...@alzad.ae>
>
> Website: http://alzad.ae/
>
> Telephone: +971551224802 <+971%2055%20122%204802><tel:+971%2055%20122%204802>
> - +971551224832 <+971%2055%20122%204832><tel:+971%2055%20122%204832>
>
> County:  United Arab Emirates
> ___
> 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
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] fighting feature creep and cleaning up Koha

[Jonathan Druart]

If anyone wants to comment but do not have a bugzilla account and does
not want to create one, you can send me your comments and I will post it
on your behalf.

On Fri, 6 Apr 2018 at 12:32 Gaetan Boisson 
wrote:

>   Hello community,
>
> (please don't answer to this message with comments about the specific
> issues mentioned, do it rather on bugzilla to keep things manageable,
> thanks!)
>
> during the last hackfest in Marseille we started a list of features or
> parts of Koha that currently exist but don't make us entirely happy for
> a reason or another and could be removed. At first i was only thinking
> of broken features that are part of Koha, then defaults that could be
> better, and it grew to whole parts that might be considered not so
> useful. (The list was made mostly by me and two other BibLibre project
> managers : Claudie and Stéphane, Owen also had a look.)
>
> Since we started i have found the right term for what i was concerned
> with: feature creep.
>
> I feel like there's been a very solid effort into refactoring code. But
> we should also consider the features themselves. Every feature comes
> with a cost: we need to maintain the code for it, we need to maintain
> documentation about it, we need to train people about them, etc. Having
> redundant features might look like it leaves choice to the user and is a
> good thing, but it can turn into a mess pretty fast. Another aspect that
> i am really concerned about are features that don't actually work. The
> best example for this according to me is results highlighting. I'm so
> used to the interface I barely see it any longer and don't pay
> attention, but it's broken, and new users notice it. This kind of not
> really functional feature included in the release looks extremely bad in
> my opinion. We need to do something about it to make Koha more
> accessible and better.
>
> As this is very much as controversial as this sounds, some of these bugs
> have generated debates, as expected. So i'm bringing this to the mailing
> list in order for all users to be able to have a look at them and tell
> us what they think. Since there are a few places concerned, an omnibus
> was created:
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20396. I don't
> want to send one message per topic to the list, that would probably be
> way too much. I also think it won't be that productive if the debates
> start from this generic message on the list. If you are a library with a
> strong opinion about one of these issues, i suggest you create an
> account on bugzilla and voice your concerns there. You are most welcome
> to do so in order to say that killing feature X is a great idea! (I
> expect we are more likely to hear from people who are against change
> than from people who are for it.)
>
> I'd like to add that since i don't write code, i'm not going to "kill"
> any of these features myself, this is more about putting the spotlight
> on some aspects of Koha that i think should be streamlined.
>
> Here's what was created so far, i will try to put the more contentious
> issues first:
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20415
>
> Remove UseKohaPlugins system preference
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20417
>
> Remove OpacCloud system preference and feature
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20528
>
> Remove the items tab from the detailed bibliographic view
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20398
>
> Add a system preference to disable search result highlighting in the
> staff interface
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20401
>
> "Item circulation alerts" is overkill and could be removed
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20406
>
> Remove ISBD display
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20408
>
> Remove the availability facet and filter
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20414
>
> Remove COinSinOPACResults system preference and make it always on
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10047
>
> "Cataloguing search maybe useless?": in the cataloguing module, there is
> a different kind of search, that we could do without.
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12561
>
> Omnibus: Deprecate non-XSLT detail and result views
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20399
>
> "Remove "did you mean" for the staff interface"
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20403
>
> Refactor "Keywords to marc mapping"
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20404
>
> Extended patron attributes should always be on
>
>
> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20405
>
> enhanced messaging preference should always be on
>
>
> - 

Re: [Koha] Bath edit record to change one character in a control field

[Jonathan Druart]

Caroline, Katrin,

Indeed, control fields are not handled (yet?) by MARC modification
templates.

Cheers,
Jonathan

On Sun, 15 Apr 2018 at 18:51 Katrin Fischer 
wrote:

> Hi Caroline,
>
> we don't use the tool so far, but I think it might not be possible right
> now.
>
> I've looked in bugzilla and couldn't find a related bug report, only the
> original bug:
>
> Bug 11395 - Batch modifications for records
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11395
>
> Katrin
>
> On 10.04.2018 21:35, Caroline Cyr-La-Rose wrote:
> > Hi all,
> >
> > Is there a way to use the batch record edit / MARC modification
> > template tools to change specific characters in the leader or other
> > control fields?
> >
> > I want to add audience information to a bunch of records. When I try
> > to make my MARC modification template, I can't enter let's say
> > "Add/Update fields 008/22 with value j". The "Field" field is limited
> > to 3 characters, so I can't write 008/22 and the "subfield" field is
> > limited to 1 character so I can't write 22.
> >
> > Thanks for your help!
> >
>
> ___
> 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] Koha for our office library

[Jonathan Druart]

Hi Raimund,

There is a koha-devel list, but that's fine.
Keep trying with kohadevbox, it's the recommended way to give Koha a try
(especially if you want to hack it).
The message is explicit: "You don't have enough free space"
Do you have enough disk space on your host?

Regards,
Jonathan

On Thu, 19 Apr 2018 at 08:02 Raimund Klein  wrote:

> Hi there,
>
> This is Raimund from ThoughtWorks Manchester.
>
> We're looking at adding a management system to our little office library,
> mainly with the view of adding electronic checkout capabilities - we're a
> Tech company highly interested in all things that have to do with little
> sensors etc., so this seems like a reasonable project which could actually
> show off some ideas to our clients in the future.
>
> We already have some capability on the sensor side, but I don't want to
> write an inventory system from scratch. A librarian friend of mine pointed
> me to Koha, and I played around with the demo on the web - quite
> impressive. My next step would be to try it out in combination with
> sticking a tag into a few of our books - for now on my dev machine (a Mac).
>
> Now I understand from the website that Koha usually runs on some flavour of
> Linux, preferably Debian. So I tried several things:
>
> - Setting up a Debian Virtual Box and installing everything there. Turned
> into a lot of pain, probably because I didn't find a good raw Debian image
> to start with.
> - Tried the same with CentOS. I actually got much further, but then I
> noticed that I didn't understand the Koha installation itself.
> - I stumbled upon the Docker image  >
> from the Oslo Public Library. For my purposes, this sounds ideal; however,
> it doesn't seem to work out of the box. When I start it and point my
> browser to localhost:8080 or 8081, all I get is a HTTP 500; the logs
> indicate that the DB isn't set up properly:
> ==> /var/log/koha/name/plack-error.log <==
> DBD::mysql::db do failed: Table 'koha_name.systempreferences' doesn't exist
> [for Statement "
> SELECT * FROM systempreferences WHERE 1 = 0 "] at
> /usr/share/koha/lib/Koha/Database.pm line 93.
> DBD::mysql::st execute failed: Table 'koha_name.systempreferences' doesn't
> exist [for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`,
> `me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE (
> `me`.`variable` = ? )" with ParamValues: 0='casauthentication'] at
> /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832.
> DBD::mysql::st execute failed: Table 'koha_name.systempreferences' doesn't
> exist [for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`,
> `me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE (
> `me`.`variable` = ? )" with ParamValues: 0='caslogout'] at
> /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832.
> DBD::mysql::st execute failed: Table 'koha_name.systempreferences' doesn't
> exist [for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`,
> `me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE (
> `me`.`variable` = ? )" with ParamValues: 0='casserverurl'] at
> /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1832.
>
> - Finally I tried the Vagrant based kohadevbox
>  (from Oslo as well). That won't
> even start for me:
> TASK [Update apt cache if needed]
> **
> fatal: [jessie]: FAILED! => {"changed": false, "msg": "'/usr/bin/apt-get
> dist-upgrade' failed: E: You don't have enough free space in
> /var/cache/apt/archives/.\n", "rc": 100, "stdout": "Reading package
> lists...\nBuilding dependency tree...\nReading state information...\nThe
> following NEW packages will be installed:\n  firmware-linux-free irqbalance
> libglib2.0-0 libglib2.0-data libnuma1\n  linux-image-3.16.0-5-amd64
> shared-mime-info xdg-user-dirs\nThe following packages will be upgraded:\n
> bind9-host dnsutils exim4 exim4-base exim4-config exim4-daemon-light\n
> gcc-4.9-base host isc-dhcp-client isc-dhcp-common libbind9-90\n
> libcurl3-gnutls libdns-export100 libdns100 libgcc1 libicu52
> libirs-export91\n  libisc-export95 libisc95 libisccc90 libisccfg-export90
> libisccfg90\n  liblwres90 libssl1.0.0 libstdc++6 libtiff5 libxml2
> linux-image-amd64 openssl\n  perl perl-base perl-modules sensible-utils\n33
> upgraded, 8 newly installed, 0 to remove and 0 not upgraded.\nNeed to get
> 60.6 MB of archives.\nAfter this operation, 182 MB of additional disk space
> will be used.\n", "stdout_lines": ["Reading package lists...", "Building
> dependency tree...", "Reading state information...", "The following NEW
> packages will be installed:", "  firmware-linux-free irqbalance
> libglib2.0-0 libglib2.0-data libnuma1", "  linux-image-3.16.0-5-amd64
> shared-mime-info xdg-user-dirs", "The following packages will be
> upgraded:", "  bind9-host dnsutils exim4 exim4-base exim4-config
> 

Re: [Koha] Renew Report

[Jonathan Druart]

How look like the new version of the query?

On Mon, 23 Apr 2018 at 12:02 Arshad Iqbal <arshadsan...@gmail.com> wrote:

> I have added reneweddate and renwal as well in sql report but working not
> good
> On Mon, Apr 23, 2018 at 7:38 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Hello Arshad,
>>
>> The renew information is in the same tables issues/old_issues, there are
>> lastreneweddate and renewals.
>>
>> Note that asking the question only once is enough :)
>>
>> Regards,
>> Jonathan
>>
>> On Mon, 23 Apr 2018 at 10:47 Arshad Iqbal <arshadsan...@gmail.com> wrote:
>>
>>> Hi,
>>> I want to convert this checked in sql report into renew sql report. How i
>>> can convert this report. guide me.
>>>
>>> SELECT b.title, b.author, i.itemcallnumber, i.barcode, c.returndate
>>> FROM (SELECT iss.returndate, iss.itemnumber FROM issues iss,
>>> (SELECT @StartDate:=<>,@EndDate:=<>> (-mm-dd)|date>>) AS var
>>> WHERE date(iss.returndate) BETWEEN @StartDate AND @EndDate UNION ALL
>>> SELECT oi.returndate, oi.itemnumber FROM old_issues oi WHERE
>>> date(oi.returndate)
>>> BETWEEN @StartDate AND @EndDate) AS c
>>> LEFT JOIN items i USING (itemnumber)
>>> LEFT JOIN biblio b USING (biblionumber)
>>> WHERE i.homebranch=<>
>>>
>>> --
>>>
>>>
>>> *Muhammad Arshad Iqbal*
>>> Assistant Librarian at Publishing and Student Affairs Directorate,
>>> National University of Science and Technology (NUST) Islamabad.
>>> ___
>>> Koha mailing list  http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>>
>
>
> --
>
>
> *Muhammad Arshad Iqbal*
> Assistant Librarian at Publishing and Student Affairs Directorate,
> National University of Science and Technology (NUST) Islamabad.
> Phone number:051-90851371
> Cell no.+923444900809 <+92%20344%204900809>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Renew Report

[Jonathan Druart]

Hello Arshad,

The renew information is in the same tables issues/old_issues, there are
lastreneweddate and renewals.

Note that asking the question only once is enough :)

Regards,
Jonathan

On Mon, 23 Apr 2018 at 10:47 Arshad Iqbal  wrote:

> Hi,
> I want to convert this checked in sql report into renew sql report. How i
> can convert this report. guide me.
>
> SELECT b.title, b.author, i.itemcallnumber, i.barcode, c.returndate
> FROM (SELECT iss.returndate, iss.itemnumber FROM issues iss,
> (SELECT @StartDate:=<>,@EndDate:=< (-mm-dd)|date>>) AS var
> WHERE date(iss.returndate) BETWEEN @StartDate AND @EndDate UNION ALL
> SELECT oi.returndate, oi.itemnumber FROM old_issues oi WHERE
> date(oi.returndate)
> BETWEEN @StartDate AND @EndDate) AS c
> LEFT JOIN items i USING (itemnumber)
> LEFT JOIN biblio b USING (biblionumber)
> WHERE i.homebranch=<>
>
> --
>
>
> *Muhammad Arshad Iqbal*
> Assistant Librarian at Publishing and Student Affairs Directorate,
> National University of Science and Technology (NUST) Islamabad.
> ___
> 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] Items held by more than one branch

[Jonathan Druart]

I'd say you are missing a group by.

On Mon, 23 Apr 2018 at 10:19 Cab Vinton  wrote:

> Hi, all--
>
> Another report question...
>
> 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.
>
> Including the statement HAVING COUNT(i.itemnumber) > 1 collapses the
> results to just one title. (Strangely, the bib returned only has a
> single item attached.)
>
> I'm missing some basic feature of how SQL operates :-(
>
> 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
> HAVING COUNT(i.itemnumber) > 1
> ORDER BY b.title
>
> Grateful in advance for any assistance!
>
> All best,
>
> Cab Vinton
> Plaistow Public Library
> Plaistow, NH
> ___
> 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] Stage Marc records for import problem

[Jonathan Druart]

(please answer to the list)
Koha 17.11.03 is indeed the latest version. "Koha 4" is not the community
version.
You should be able to install it, following the wiki page instruction, on
top of a debian distribution.

https://wiki.koha-community.org/wiki/Koha_on_Debian

Regards,
Jonathan

On Mon, 26 Mar 2018 at 13:31 Matt Rose <libr...@halswaymanor.org.uk> wrote:

> Hi Jonathan,
>
>
> Many thanks for responding, I appreciate it. I am using  Koha 04.18.06 I
> think, accessible through a shortcut named: Koha staff client  which I
> think came from LibLime-Koha-4.18.06.tar folder that I downloaded.
>
>
> I have just downloaded what I think is the latest version, koha-17.11.03.
> I have literally no idea how to install it onto my Oracle VM Virtual
> Boc Debian 9.3.0 Base Build. I have printed off the Koha on Debian
> instructions from Koha Wiki but am none the wiser!
>
>
> Matt
>
> www.halswaymanor.org.uk
>
> Halsway Manor Centre for the Folk Arts
>
> Somerset
>
> United Kingdom
>
>
> --
> *From:* Jonathan Druart <jonathan.dru...@bugs.koha-community.org>
> *Sent:* 23 March 2018 18:10
> *To:* Matt Rose
> *Cc:* koha@lists.katipo.co.nz
> *Subject:* Re: [Koha] Stage Marc records for import problem
>
> Hi Matt,
>
> Which Koha version do you use? How did you install it?
> Do you see something in the log files?
>
> Regards,
> Jonathan
>
> On Fri, 23 Mar 2018 at 14:52 Matt Rose <libr...@halswaymanor.org.uk>
> wrote:
>
> Hi folks,
>
>
> Beginners question. Why does my Marc records import to Koha freeze when I
> click 'Stage for Import'. Job Progress stays at 0%  See below. many thanks,
> Matt  libr...@halswaymanor.org.uk
>
>
> Koha/Home/Tools/Stage MARC records for import
>
>   *   Select a MARC file to stage in the import reservoir. It will be
> parsed, and each valid record staged for later import into the catalog.
>   *   You can enter a name for this import. It may be useful, when
> creating a record, to remember where the suggested MARC data comes from!
>
> Stage records into the reservoir
>
>   1.
> Select the file to stage:
>
> Upload fileCancel
>
> Upload progress: 100%
>
>
>   1.  Comments about this file:
>   2.  Record type:
> Bibliographic
>
> Authority
>
>   3.  Character encoding:
> UTF-8 (Default)
>
> MARC 8
>
> ISO 5426
>
> ISO 6937
>
> ISO 8859-1
>
> EUC-KR
>
>   4.  Format:
> MARC
>
> MARCXML
>
>
> Look for existing records in catalog?
>
>   1.  Record matching rule:
> Do not look for matching records
>
> ISBN (020$a)
>
> ISSN (022$a)
>
> KohaBiblio (999$c)
>
>   2.  Action if matching record found:
> Replace existing record with incoming record
>
> Add incoming record
>
> Ignore incoming record (its items may still be processed)
>
>   3.  Action if no match is found:
> Add incoming record
>
> Ignore incoming record (its items may still be processed)
>
>
> Check for embedded item record data?
>
>   1.   Yes
>   2.   No
>
>   1.  How to process items:
> Always add items
>
> Add items only if matching bib was found
>
> Add items only if no matching bib was found
>
> Replace items if matching bib was found (only for existing items)
>
> Ignore items
>
>
>
> Job progress:
> 0%
>
> ___
> 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] Reschedule meetings

[Jonathan Druart]

Hello everybody,

The last meetings did not take place and I rescheduled them:

General IRC meeting: General_IRC_meeting_4_April_2018


Developers IRC meeting: Development_IRC_meeting_11_April_2018


Reminder, the documentation IRC meeting is today:
Documentation_IRC_meeting_29_March_2018


Hope to see you there!

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

Re: [Koha] synchro two instances of Koha

[Jonathan Druart]

Hi Giuseppe,

I wrote something to do that few years ago when I worked at BibLibre (
https://git.biblibre.com/biblibre/kss/)
Kss is for "Koha sync system", the idea was to synchronize slave
installations (without internet access during the day) with the master
installation.
It does not appear to have been updated to work with new versions of Koha.
It has been initially written for 3.2 and rewritten for 3.16

Regards,
Jonathan

On Sun, 4 Mar 2018 at 02:07 Giuseppe Angilella <
giuseppe.angile...@ct.infn.it> wrote:

> Hi,
>
> is it possible to synchronize two (online) instances of Koha? I mean, two
> identical installations, updated regularly, residing on two different
> machines, where patrons and administrators can access and modify entries
> independently. Would it possible to synchronize their databases (and
> perhaps some relevant external file), on the basis of the modification
> timestamp of those entries that have been actually modified?
>
> (I am not sure whether my question is simply equivalent to that of
> synchronizing two mysql databases on different servers, for which there
> might be an answer, if I google it correctly: your advice is appreciated.)
>
> Many thanks,
>
> Giuseppe.
> ___
> 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] Stage Marc records for import problem

[Jonathan Druart]

Hi Matt,

Which Koha version do you use? How did you install it?
Do you see something in the log files?

Regards,
Jonathan

On Fri, 23 Mar 2018 at 14:52 Matt Rose  wrote:

> Hi folks,
>
>
> Beginners question. Why does my Marc records import to Koha freeze when I
> click 'Stage for Import'. Job Progress stays at 0%  See below. many thanks,
> Matt  libr...@halswaymanor.org.uk
>
>
> Koha/Home/Tools/Stage MARC records for import
>
>   *   Select a MARC file to stage in the import reservoir. It will be
> parsed, and each valid record staged for later import into the catalog.
>   *   You can enter a name for this import. It may be useful, when
> creating a record, to remember where the suggested MARC data comes from!
>
> Stage records into the reservoir
>
>   1.
> Select the file to stage:
>
> Upload fileCancel
>
> Upload progress: 100%
>
>
>   1.  Comments about this file:
>   2.  Record type:
> Bibliographic
>
> Authority
>
>   3.  Character encoding:
> UTF-8 (Default)
>
> MARC 8
>
> ISO 5426
>
> ISO 6937
>
> ISO 8859-1
>
> EUC-KR
>
>   4.  Format:
> MARC
>
> MARCXML
>
>
> Look for existing records in catalog?
>
>   1.  Record matching rule:
> Do not look for matching records
>
> ISBN (020$a)
>
> ISSN (022$a)
>
> KohaBiblio (999$c)
>
>   2.  Action if matching record found:
> Replace existing record with incoming record
>
> Add incoming record
>
> Ignore incoming record (its items may still be processed)
>
>   3.  Action if no match is found:
> Add incoming record
>
> Ignore incoming record (its items may still be processed)
>
>
> Check for embedded item record data?
>
>   1.   Yes
>   2.   No
>
>   1.  How to process items:
> Always add items
>
> Add items only if matching bib was found
>
> Add items only if no matching bib was found
>
> Replace items if matching bib was found (only for existing items)
>
> Ignore items
>
>
>
> Job progress:
> 0%
>
> ___
> 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] Regarding SMS Setting in KOHA

[Jonathan Druart]

Hi,

Search for "sms" in the manual:
https://koha-community.org/manual/18.05/en/html/02_administration.html?highlight=sms#smssenddriver-smssendusername-and-smssendpassword

Regards,
Jonathan

On Mon, 26 Feb 2018 at 23:30 Lalit Thakur  wrote:

> How can provide the facility for user. I have no idea where is the setting
> of sns in koha. Pls. Provide the path.
>
> On Feb 26, 2018 20:57, "Paul Hoffman"  wrote:
>
> > 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 
> > 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
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Removing of syspref checkdigit

[Jonathan Druart]

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

Re: [Koha] software error when user not superlibrarian tries to find a patron

[Jonathan Druart]

Hello Carolina,

You should upgrade, what you describe is a bug that has been fixed bug
20998. It is part of 17.11.08

Regards,
Jonathan

On Mon, 22 Oct 2018 at 09:29 Carolina Andreu 
wrote:

> Hello Koha community,
> We've found that when a librarian has some permissions (catalog +
> borrowers)
> but not superlibrarian and syspref IndependenBranches is turned on, we get
> a
> software error when this user not superlibrarian tries to find a patron
> within the patrons module: Can't call method "branchcode" on an undefined
> value at /home/www/our_koha/intranet/cgi-bin/members/member.pl line 56.
>
> Still, this user is able to find the same patron searched before if
> cardnumber or borrowernumber is used instead of name.
>
> We're working on Koha 17.11 + Debian 8.
>
> Has someone experienced this behavior and could give any clue? Should we
> report this as a bug?
>
> Thanks in advance!
>
> ___
> 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] Not for Loan

[Jonathan Druart]

Hello Victoria,

If you want even more magic you can try the "Update SQL" button that
appears on the report list view when a report is using the old
biblioitems.marcxml fields.

See those screenshots: https://snag.gy/j17fdl.jpg and
https://snag.gy/1i063z.jpg

Regards,
Jonathan

On Tue, 23 Oct 2018 at 05:23 Ma. Victoria H. Silva-Manuel <
mavicsi...@gmail.com> wrote:

> Yes, it worked like magic.
> Thank you so much for your help.
>
> On Tue, Oct 23, 2018 at 4:19 PM Bob Birchall  wrote:
>
> > Ah yes, sorry.
> > Replace each occurrence of marcxml with metadata
> >
> > That should do it.
> > Bob
> >
> > On 23/10/18 6:51 pm, Ma. Victoria H. Silva-Manuel wrote:
> >
> > We are using 17.11.10.
> > I followed your instructions but i'm still getting the same error
> message.
> >
> > On Tue, Oct 23, 2018 at 3:43 PM Bob Birchall  wrote:
> >
> >> On 23/10/18 6:16 pm, Ma. Victoria H. Silva-Manuel wrote:
> >> > Hi.
> >> >
> >> > I copied this SQL report
> >> >
> >> > SELECT
> >> >  CONCAT(' detail.pl?biblionumber=
> >> ',b.biblionumber,
> >> > '\">', b.title, '' ) AS Title,
> >> >  ExtractValue(bi.marcxml,
> >> > '//datafield[@tag="245"]/subfield[@code="b"]') AS "Subtitle",
> >> >  ExtractValue(bi.marcxml,
> >> > '//datafield[@tag="245"]/subfield[@code="n"]') AS "Part name",
> >> >  ExtractValue(bi.marcxml,
> >> > '//datafield[@tag="245"]/subfield[@code="p"]') AS "Part",
> >> >  b.author AS 'Author',
> >> >  b.copyrightdate AS 'Year',
> >> >  i.barcode AS Barcode,
> >> >  i.itemcallnumber AS 'Callnumber',
> >> >  i.itype AS 'Item Type'FROM biblio bLEFT JOIN items i USING (
> >> > biblionumber ) LEFT JOIN biblioitems bi USING ( biblionumber ) WHERE
> >> > i.notforloan = '1'ORDER BY b.title
> >> >
> >> >
> >> > but I'm got this message when I ran it.
> >> >
> >> > *The following error was encountered:*
> >> > The database returned the following error:
> >> > Unknown column 'bi.marcxml' in 'field list'
> >> > Please check the log for further details.
> >> > Return to previous page
> >> > <
> >>
> http://192.168.1.18:8080/cgi-bin/koha/reports/guided_reports.pl?reports=23=Run%20this%20report#
> >> >
> >> >
> >> > Can anyone tell me what is wrong?
> >>
> >> Hi, do three things:
> >> - delete LEFT JOIN biblioitems bi and replace it with LEFT JOIN
> >> biblio_metadata bi
> >> - at FROM biblio bLEFT JOIN insert a space between b and LEFT
> >> - at i.itype AS 'Item Type'FROM insert a space between Type' and FROM
> >>
> >> The marcxml was taken out of the biblioitems table and put in a separate
> >> biblio_metadata table a couple of versions back. You haven't said what
> >> version you are using, but it must be relatively recent?
> >>
> >> HTH,
> >> Bob Birchall
> >> Calyx
> >> ___
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> https://lists.katipo.co.nz/mailman/listinfo/koha
> >>
> >
> >
> > --
> > Ma. Victoria H. Silva-Manuel
> > Registered Librarian, 3892
> >
> >
> >
>
> --
> Ma. Victoria H. Silva-Manuel
> Registered Librarian, 3892
> ___
> 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] Tabs display in catalogue editing mode

[Jonathan Druart]

Hi Elaine,

I do not recreate, make sure you have correctly cleared the cache of your
browser.


Cheers,
Jonathan

On Tue, 30 Oct 2018 at 19:50 Elaine Bradtke  wrote:

> We just updated to 18.05.05. Now the tabs are displaying strangely -
> covering the buttons (and less often, the buttons hide the tab numbers).
> But it's only a problem with some of the tabs: 1-4 and 8-9. The buttons and
> tabs still seem to function, but they don't display correctly.
> It also only seems to happen in Chrome (it works fine in Firefox). I've
> cleared the browser history in Chrome and restarted it, but it persists.
> Any thoughts?
>
> screenshot:
> https://drive.google.com/open?id=1phJw3ybaRIKiYjnDyv6vXV73Ondg5nAk
>
> Elaine Bradtke
> VWML
> English Folk Dance and Song Society | http://www.efdss.org
> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> 
> Tel+44 (0) 20 7485 2206 <+44%2020%207485%202206> (This number is for
> the English Folk Dance and
> Song Society in London, England. If you wish to phone me personally, send
> an e-mail first. I work off site)
> --
> Registered Company No. 297142
> Charity Registered in England and Wales No. 305999
> ---
> "Writing about music is like dancing about architecture"
> --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
> ___
> 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] Tabs display in catalogue editing mode

[Jonathan Druart]

The bug has been reported for the "list" view on bug 21751.
I do recreate this one on Chrome, and it does not affect Firefox.

On Wed, 31 Oct 2018 at 11:54 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Elaine,
>
> I do not recreate, make sure you have correctly cleared the cache of your
> browser.
>
>
> Cheers,
> Jonathan
>
> On Tue, 30 Oct 2018 at 19:50 Elaine Bradtke  wrote:
>
>> We just updated to 18.05.05. Now the tabs are displaying strangely -
>> covering the buttons (and less often, the buttons hide the tab numbers).
>> But it's only a problem with some of the tabs: 1-4 and 8-9. The buttons
>> and
>> tabs still seem to function, but they don't display correctly.
>> It also only seems to happen in Chrome (it works fine in Firefox). I've
>> cleared the browser history in Chrome and restarted it, but it persists.
>> Any thoughts?
>>
>> screenshot:
>> https://drive.google.com/open?id=1phJw3ybaRIKiYjnDyv6vXV73Ondg5nAk
>>
>> Elaine Bradtke
>> VWML
>> English Folk Dance and Song Society | http://www.efdss.org
>> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
>> <https://maps.google.com/?q=2+Regent's+Park+Road,+London+NW1+7AY=gmail=g>
>> Tel+44 (0) 20 7485 2206 <+44%2020%207485%202206> (This number is for
>> the English Folk Dance and
>> Song Society in London, England. If you wish to phone me personally, send
>> an e-mail first. I work off site)
>> --
>> Registered Company No. 297142
>> Charity Registered in England and Wales No. 305999
>>
>> ---
>> "Writing about music is like dancing about architecture"
>> --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
>> ___
>> 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] More on OPAC Search too slow in Koha 18.05.05

[Jonathan Druart]

Hola Camilo,

Take a look at the value of use_zebra_facets in your koha-conf.xml file.
If enabled, disable it (see bug 13665). You may also want to play with the
value of maxRecordsForFacets.

Saludos,
Jonathan

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13665


On Thu, 8 Nov 2018 at 19:35 Camilo Freire  wrote:

> With respect to my last post on problems in OPAC Search in Koha, I've found
> that the problem is in the method  _get_facets_from_zebra called from the
> method GetFacets of the class Search.pm. The asyncronous programming has
> nothing to do with the problem.
>
> Perhaps someone have had a similar problem or can help me about this.
>
> Thanks in advance
> Camilo Freire
>
>
>
> -- Forwarded message -
> From: Camilo Freire 
> Date: mié., 7 nov. 2018 a las 20:09
> Subject: OPAC Search too slow in Koha 18.05.05
> To: 
>
>
> Good afternoon. My name is Camilo Freire, from Montevideo, Uruguay.
>
> I have a catalogue with around 280.000 bibliographic records in Koha
> 18.05.05. When I do some searches whose hit's number is about 14.000
> records the time of search climbs from an average of 2 seconds per search
> to 40 to 80 seconds around. I've a virtual machine with 6GB of RAM, with a
> virtual Xeon of 2GHz.
>
> Koha is making the OPAC search calling the function getRecords which is in
> the lib/C4/Search.pm file. As I've seen this function first makes a call to
> the ZOOM::search function and then makes an asynchronous loop for getting
> the records (don't do that in ZOOM::search?) and facets, calling the
> _ZOOM_event_function. The Zebra search in ZOOM::search is quite fast, and
> takes no more than 0.3 seconds to perform the search. It seems that the
> delay is in the asynchronous facets in the _ZOOM_event_loop function. Is
> not clear to me what exactly the _ZOOM_event_loop is doing, apart from
> retrieving the facets, which are not necessary for me.
>
> Can I resolve in some way this problem, getting rid of the _ZOOM_event_loop
> or installing other version? As a first step I've enabled plack, which is a
> great help in speeding up the application but not in this case.
>
> Thank you very much in advance.
> ___
> 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] MaxOpenSuggestions Question

[Jonathan Druart]

Hi Lisette,

It's the number of opened/pending suggestions (status=ASKED)

Cheers,
Jonathan

On Thu, 8 Nov 2018 at 18:02 Lisette Scheer 
wrote:

> Hello all, Does MaxOpenSuggestions only count pending suggestions or does
> it count anything that isn't specific status (accepted, rejected, etc.?)
> Thank you!Lisette ScheerSystem Administrative Assistant- Latah County
> Library districtliset...@latahlibrary.org
> ___
> 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] Free KOHA OPAC Mobile App from LIS Academy

[Jonathan Druart]

Hello,

Is the code of the app accessible somewhere?

Regards,
Jonathan

On Mon, 12 Nov 2018 at 10:17 PDIT Library  wrote:

> Dear Professionals,
>
> Happy to share with you all,   One of our innovative product - Koha
> Opac Mobile App has been released from LIS  Academy. It is totally
> free of cost. Any library using KOHA can use this App to reach their
> users remotely through their Android Mobiles.
>
> This Android based Mobile App is an exclusive mobile app designed and
> developed for the libraries using KOHA LMS for automating their
> library system. This app acts as a plug-in and fetches the content
> from existing KOHA LMS and user can use OPAC login credentials to log
> in through the mobile app.
>
> It is freely available on google play store to download. Presently 12
> institutions and 800+ patrons using app..
>
> https://play.google.com/store/apps/details?id=com.lisacademy.org.kohaopac
>
> Demo credintials of KOHA OPAC:
>
> College Code: LISA
> Card Number: Librarian
> Password: Librarian
>
> How to register Libraries to KOHA OPAC:
>
> College Code: admin
> Card Number: library
> Password: librarian
>
> Reach us for any assistance lisacademyorg at gmail.com
> 
>
> Thanks & Regards,
> Dr. P. V. Konnur
> President - LIS Academy, Bangalore
> Former LIS Professor,
> Fulbright Scholar - (UIUC, USA)
> Chairman - State Level Book Selection Committee, Karnataka
> Adviser - VTU Consortium,
> Visvesvaraya Technological University, Belagavi - 590 018,
> Member of Syndicate, KUVEMPU University, Shivamogga,
> Karnataka, India
> Mobile : 09449679737
> E-Mail : pvkonnur at gmail.com
> 
> Website: www.lisacademy.org
>
>
> --
>
> *LIBRARIAN*
>
> *Proudhadevaraya Institute of Technology*
>
> *TB Dam, **HOSAPETE-583 225*
>
> *Ballari District, **Karnataka, India.*
>
>
> *Web http://pdit.ac.in *
>
> *Email**librar...@pdit.ac.in *
>
> *Phone: 08394 259505*
>
> *Phone +91-8394 259505 <+91%2083942%2059505> *
> ___
> 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] Patron Add error

[Jonathan Druart]

Hello Arshad,

Can you confirm you always get this error when you create a new patron?
If you do, please detail the different steps, from the home page of Koha
until the crash.

Regards,
Jonathan

On Sun, 11 Nov 2018 at 02:49 Arshad Iqbal  wrote:

> Koha version is18.05.04
> Patrons fields which i am using for data entry.
> Surname
> Name
> Gender
> Address
> Phon no.
> Email primary
> Card number
> Expiray date
> Circulation note
> User name
> Password
> On Nov 9, 2018 4:45 PM, "Jonathan Druart" <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Hello,
>>
>> What is the exact version of Koha you use?
>> What are the different steps to recreate (on which links to you click)?
>>
>> Regards,
>> Jonathan
>>
>> On Fri, 9 Nov 2018 at 01:27 Arshad Iqbal  wrote:
>>
>>> Hello every one
>>> When i try to enter any patron in koha i am facing this error "Wrong CSRF
>>> token at /usr/share/koha/intranet/cgi-bin/members/memberentry.pl line
>>> 307"
>>> Please help me how to solve this problem?
>>>
>>> --
>>>
>>> Best Regards
>>> *Muhammad Arshad Iqbal*
>>> *Assistant Librarian*
>>> *NUST Central Library *
>>> *National University of Science and Technology (NUST)*
>>> *Sector H-12, Islamabad, Pakistan*
>>> *Tel. Office:051-90851087*
>>> *Cell no.+923444900809 <+92%20344%204900809>*
>>> ___
>>> 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] Possible to customize date format in notices/slips?

[Jonathan Druart]

Hi Arturo,

I do recreate on 17.11.10, not master. Can you open a bug report?
You should not need to specify the dateonly filter for dateexpiry, it's
automatically truncated to only display the date part (as there is no time
part!)

Regards,
Jonathan

On Tue, 13 Nov 2018 at 11:14 Arturo Longoria 
wrote:

> Thank you for your help, Katrin! As a follow up, I attempted to use the
> dateonly placeholder for our membership expiry notice, but the generated
> e-mails did not display as expected. In the notice, I used the following
> text exactly, with a space before and after the pipe character: "Your
> account will expire on <>." But the
> notices that were generated say: "Your account will expire on <>" (with an
> empty left and right angle brackets.
>
> Our library is on Koha 17.11.10, and looking at the database schema, I see
> that the borrowers.dateexpiry column is "date", not "datetime", so that
> could be the reason why the dateonly placeholder doesn't work? But if
> that's the case, why is the "12:00 AM" added if the db column is a date,
> not a datetime?
>
>
> Arturo Longoria
> Reference Librarian/Web Manager
> Texas State Law Library
> www.sll.texas.gov
>
> -Original Message-
> From: Koha  On Behalf Of Katrin Fischer
> Sent: Friday, November 9, 2018 00:59
> To: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Possible to customize date format in notices/slips?
>
> Hi Arturo,
>
> try adding | dateonly to your placeholder variable like this:
>
> << biblio.timestamp | dateonly >>
>
> Hope this helps,
>
> Katrin
>
> On 07.11.18 15:46, Arturo Longoria wrote:
> > Our library recently enabled the MEMBERSHIP_EXPIRY notice to alert
> patrons of expiring accounts. Currently, these notices display the
> expiration date along with a time (“Your account will expire on 12/06/2018
> 12:00 AM”), but is there a way to just display the date without the time? I
> read through the information on the wiki at
> https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips as
> well as the manual, but I did not find any indication that the date format
> can be customized. I thought I’d check in with the list, though, to make
> sure I’m not missing anything.
> >
> > Thanks for any input you may have!
> >
> >
> > Arturo Longoria
> > Reference Librarian/Web Manager
> > Texas State Law Library
> > www.sll.texas.gov
> >
> > ___
> > 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
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Possible to customize date format in notices/slips?

[Jonathan Druart]

I am not sure it's a regression actually.

in master it has been fixed by
commit a236b684fdae8e0da83ca7263b948da971dfc849
Bug 17981: Add a preview mode for notice templates

modified: C4/Letters.pm
@ Letters.pm:887 @ sub _parseletter {
 my $values = $values_in ? { %$values_in } : {};

 if ( $table eq 'borrowers' && $values->{'dateexpiry'} ){
-$values->{'dateexpiry'} = format_sqldatetime(
$values->{'dateexpiry'} );
+$values->{'dateexpiry'} = output_pref({ str =>
$values->{dateexpiry}, dateonly => 1 });
 }

 if ( $table eq 'reserves' && $values->{'waitingdate'} ) {

On Tue, 13 Nov 2018 at 12:21 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Hi Arturo,
>
> I do recreate on 17.11.10, not master. Can you open a bug report?
> You should not need to specify the dateonly filter for dateexpiry, it's
> automatically truncated to only display the date part (as there is no time
> part!)
>
> Regards,
> Jonathan
>
> On Tue, 13 Nov 2018 at 11:14 Arturo Longoria <
> arturo.longo...@sll.texas.gov> wrote:
>
>> Thank you for your help, Katrin! As a follow up, I attempted to use the
>> dateonly placeholder for our membership expiry notice, but the generated
>> e-mails did not display as expected. In the notice, I used the following
>> text exactly, with a space before and after the pipe character: "Your
>> account will expire on <>." But the
>> notices that were generated say: "Your account will expire on <>" (with an
>> empty left and right angle brackets.
>>
>> Our library is on Koha 17.11.10, and looking at the database schema, I
>> see that the borrowers.dateexpiry column is "date", not "datetime", so that
>> could be the reason why the dateonly placeholder doesn't work? But if
>> that's the case, why is the "12:00 AM" added if the db column is a date,
>> not a datetime?
>>
>>
>> Arturo Longoria
>> Reference Librarian/Web Manager
>> Texas State Law Library
>> www.sll.texas.gov
>>
>> -Original Message-
>> From: Koha  On Behalf Of Katrin Fischer
>> Sent: Friday, November 9, 2018 00:59
>> To: koha@lists.katipo.co.nz
>> Subject: Re: [Koha] Possible to customize date format in notices/slips?
>>
>> Hi Arturo,
>>
>> try adding | dateonly to your placeholder variable like this:
>>
>> << biblio.timestamp | dateonly >>
>>
>> Hope this helps,
>>
>> Katrin
>>
>> On 07.11.18 15:46, Arturo Longoria wrote:
>> > Our library recently enabled the MEMBERSHIP_EXPIRY notice to alert
>> patrons of expiring accounts. Currently, these notices display the
>> expiration date along with a time (“Your account will expire on 12/06/2018
>> 12:00 AM”), but is there a way to just display the date without the time? I
>> read through the information on the wiki at
>> https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips as
>> well as the manual, but I did not find any indication that the date format
>> can be customized. I thought I’d check in with the list, though, to make
>> sure I’m not missing anything.
>> >
>> > Thanks for any input you may have!
>> >
>> >
>> > Arturo Longoria
>> > Reference Librarian/Web Manager
>> > Texas State Law Library
>> > www.sll.texas.gov<http://www.sll.texas.gov/>
>> >
>> > ___
>> > 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
>>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Patron Add error

[Jonathan Druart]

Hello,

What is the exact version of Koha you use?
What are the different steps to recreate (on which links to you click)?

Regards,
Jonathan

On Fri, 9 Nov 2018 at 01:27 Arshad Iqbal  wrote:

> Hello every one
> When i try to enter any patron in koha i am facing this error "Wrong CSRF
> token at /usr/share/koha/intranet/cgi-bin/members/memberentry.pl line 307"
> Please help me how to solve this problem?
>
> --
>
> Best Regards
> *Muhammad Arshad Iqbal*
> *Assistant Librarian*
> *NUST Central Library *
> *National University of Science and Technology (NUST)*
> *Sector H-12, Islamabad, Pakistan*
> *Tel. Office:051-90851087*
> *Cell no.+923444900809 <+92%20344%204900809>*
> ___
> 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] CHECK IN ERROR

[Jonathan Druart]

Hello Igbudu,

Did you read the wiki page? Which part(s) need clarification?

Regards,
Jonathan

On Mon, 8 Oct 2018 at 09:03 Igbudu Tersoo  wrote:

> *Hi everyone,*
>
> *I am using koha version 17.11 with the database Mysql ver15.11
> distribution 10.0.36-MariaDB.  I want to "**check in" and the error message
> below appears, I click on about page and the second information about data
> problems comes out. Please what can I do. I have limited knowledge with
> mysql and MariaDB.*
>
> *Thanks a lot.*
>
>
> *Check in error message message*
>
> 037655: Computer Science
> <
> http://154.68.225.19:8001/cgi-bin/koha/catalogue/detail.pl?type=intra=136
> >
>
> *The item has not been checked in due to a configuration issue in your
> system. You must ask an administrator to take a look at the about page
>  and search for
> the "data problems" section*
>
> Top of Form
>
>
> About page information Data problems
>
> Some of your tables have problems with their auto_increment values which
> may lead to data loss.
>
> *You should not ignore this warning.*
>
> The problem is that InnoDB does not keep auto_increment across SQL server
> restarts (it is only set in memory). So on server startup the
> auto_increment values are set to max(table.id)+1.
>
> To know how to avoid this problem see the related wiki page: DBMS auto
> increment fix <
> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix>
> Problems found Patrons
>
> The following ids exist in both tables *borrowers* and *deletedborrowers*:
>
> 4
> Checkouts
>
> The following ids exist in both tables *issues* and *old_issues*:
>
> 16, 17, 18
>
>
>
> Warnings regarding the system configuration
>
> *Preferences and parameters*
>
> *Warning*
>
> You are missing the  entry in your koha-conf.xml file.
> That will bring a performance boost to enable it.
> ___
> 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] Patrons account expires once the user login to opac

[Jonathan Druart]

Hi Mohammed,
Not sure about that but, should not it be
  
instead of
  2019-09-30
?

On Tue, 2 Oct 2018 at 09:25 Mohammad Nashbat  wrote:

> Hi All,
>
> I have a problem with the patrons expiry, all patron accounts expires once
> user login to opac even is I renewed them from my admin side. We have an
> integration with ldap but again under
> (/etc/koha/sites/alfaisal/koha-conf.xml) I have the expiry date updated to
> (2019-09-30), so when I do the renewal from
> the admin side it's renewed to that date (2019-09-30) but once the user
> login to the opac and logout it changed to one year back which it was the
> old date in koha-conf.xml, I also updated the dates under (Patron
> categories) under enrollment period to be (2019-09-30), but all of this
> didn't work, any suggestions.
>
> Thanks & Best Regards,
>
> Mohammed
>
>
> 
>
> DISCLAIMER: This electronic mail transmission contains confidential
> information intended only for the person(s) named. Any use, distribution,
> copying or disclosure by any other person is strictly prohibited. If you
> received this transmission in error, please notify the sender by reply
> e-mail and then destroy the message. Opinions, conclusions, and other
> information in this message that do not relate to the official business of
> Alfaisal University shall understand to be neither given nor endorsed by
> Alfaisal University. The contents of any attachment to this e-mail may
> contain software viruses, which could damage your own computer system.
> While "Alfaisal University" has taken every reasonable precaution to
> minimize this risk, we cannot accept liability for any damage which you
> sustain as a result of software viruses. You should carry out your own
> virus checks before opening the attachment.
> ___
> 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] Patrons account expires once the user login to opac

[Jonathan Druart]

Indeed, I read the code too quickly.
It says:
516   
517   

then:
532 The  subelements establish the relationship between mysql
fields and LDAP attributes. The element name
533 is the column in mysql, with the "is" characteristic set to the LDAP
attribute name.  Optionally, any content
534 between the element tags is taken as the default value.

Maybe you need to set the "is" attribute to the LDAP attribute name?

On Tue, 2 Oct 2018 at 10:30 Mohammad Nashbat  wrote:

> Hi Jonathan,
>
>
>
> This is part of the ldap integration and not it’s correct, it has been
> like that since long time. But any way even if I take it out I’m still
> facing the same proble.
>
>
>
> *Thanks & Best Regards,*
>
>
>
> *Mohammed Nashbat*
>
> *Library Instructor*
>
>
>
> *From:* Jonathan Druart [mailto:jonathan.dru...@bugs.koha-community.org]
> *Sent:* Tuesday, October 02, 2018 03:48 م
> *To:* Mohammad Nashbat
> *Cc:* koha@lists.katipo.co.nz
> *Subject:* Re: [Koha] Patrons account expires once the user login to opac
>
>
>
> Hi Mohammed,
>
> Not sure about that but, should not it be
>
>   
>
> instead of
>
>   2019-09-30
>
> ?
>
>
>
> On Tue, 2 Oct 2018 at 09:25 Mohammad Nashbat 
> wrote:
>
> Hi All,
>
> I have a problem with the patrons expiry, all patron accounts expires once
> user login to opac even is I renewed them from my admin side. We have an
> integration with ldap but again under
> (/etc/koha/sites/alfaisal/koha-conf.xml) I have the expiry date updated to
> (2019-09-30), so when I do the renewal from
> the admin side it's renewed to that date (2019-09-30) but once the user
> login to the opac and logout it changed to one year back which it was the
> old date in koha-conf.xml, I also updated the dates under (Patron
> categories) under enrollment period to be (2019-09-30), but all of this
> didn't work, any suggestions.
>
> Thanks & Best Regards,
>
> Mohammed
>
>
> 
>
> DISCLAIMER: This electronic mail transmission contains confidential
> information intended only for the person(s) named. Any use, distribution,
> copying or disclosure by any other person is strictly prohibited. If you
> received this transmission in error, please notify the sender by reply
> e-mail and then destroy the message. Opinions, conclusions, and other
> information in this message that do not relate to the official business of
> Alfaisal University shall understand to be neither given nor endorsed by
> Alfaisal University. The contents of any attachment to this e-mail may
> contain software viruses, which could damage your own computer system.
> While "Alfaisal University" has taken every reasonable precaution to
> minimize this risk, we cannot accept liability for any damage which you
> sustain as a result of software viruses. You should carry out your own
> virus checks before opening the attachment.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> --
>
> DISCLAIMER: This electronic mail transmission contains confidential
> information intended only for the person(s) named. Any use, distribution,
> copying or disclosure by any other person is strictly prohibited. If you
> received this transmission in error, please notify the sender by reply
> e-mail and then destroy the message. Opinions, conclusions, and other
> information in this message that do not relate to the official business of
> Alfaisal University shall understand to be neither given nor endorsed by
> Alfaisal University. The contents of any attachment to this e-mail may
> contain software viruses, which could damage your own computer system.
> While “Alfaisal University” has taken every reasonable precaution to
> minimize this risk, we cannot accept liability for any damage which you
> sustain as a result of software viruses. You should carry out your own
> virus checks before opening the attachment.
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Field 606 doesnt add multiple x subfields

[Jonathan Druart]

Patch attached, please test.

On Fri, 28 Sep 2018 at 10:37 anjoze  wrote:

> Thanks for your feedback.
> I've filed a new bug:
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21448
>
>
>
> -
> Koha version:   16.05.05
>- -
> José Anjos
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> 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] Help testing marc staging performance issues

[Jonathan Druart]

Hi Barton,

> I believe this typically happens under plack.

These scripts should not run under plack, check your apache config file
(search for "ProxyPass" in apache-shared-intranet-plack.conf)

Cheers,
Jonathan

On Wed, 19 Sep 2018 at 19:17 Barton Chittenden 
wrote:

> Hi, All!
>
> At ByWater, we've had a few reports of
>
> "Home › Tools › Stage MARC records for import" timing out on large import
> batches, with the message "there was an error."
>
> When this happens, there are typically two batches under
>
> Home › Tools › Manage staged MARC records
>
> The first batch will show a number of records, and the second batch will
> show 0 records.
>
> I believe this typically happens under plack. I'm having a *very* difficult
> time re-creating the error, so I don't have any plack error logs, I don't
> have any good numbers on how many records cause the problem.
>
> One of our libraries told me that the problem seems to be worse when using
> matching rules.
>
> If you've seen issues like this, I would love to know
>
> 1) What version of Koha you're using
> 2) How many records you were importing
> 3) If you were doing any sort of record matching
> 4) Any other relevant details
> 5) If you have access to the server error logs, I'd like to know what
> messages you see there.
>
> I'd like to file a bug, but without being able to replicate the problem, I
> can't get any traction there.
>
> Thanks,
>
> --Barton
> ___
> 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] DBMS auto increment issue - BUG19016

[Jonathan Druart]

Important note: This is a destructive method, you are going to lose
circulation data!

Please do not forget to mention it when you suggest people to remove rows
from their tables :)

On Thu, 20 Sep 2018 at 19:39 Luis Moises Rojas 
wrote:

> Hi,
> I still do not know why this happen and when they going to fix it.
> I have several solutions which i am going to submit , but here is:
>
> Go to old_issues and delete those itemnumber. You can use the phpmyadmin or
> use the console
>
> Delete from old_issues where itemnumber=here goes your number
>
> El jue., 20 de sept. de 2018 4:05 PM, Sven Halm 
> escribió:
>
> > Hi all,
> >
> > i have got the BUG19016 (
> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19016) problem
> > in my production environment. The koha system information says:
> >
> > ---start quote---
> > Problems found
> > Items
> >
> >
> > The following ids exist in both tables items and deleteditems :
> >
> > 1016, 1017 Checkouts
> >
> >
> > The following ids exist in both tables issues and old_issues :
> >
> > 587, 590, 589, 586, 584, 585, 588, 583, 582
> > ---end quote---
> >
> > After i had read the artikels i implemented the init script (see [
> > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix |
> > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix ] ).
> >
> > But how can i resolve the problem? I don't know how to do that.
> >
> > Could you help, please?
> >
> > Kind regards
> > Sven
> >
> > library: [ https://lesehoehle.foerderverein-hellwegschule.de/ |
> > https://lesehoehle.foerderverein-hellwegschule.de ]
> >
> > ___
> > 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] Koha Upgrade

[Jonathan Druart]

See bug 20826
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20826

On Thu, 20 Sep 2018 at 07:07 Ashok Francis 
wrote:

> Dear All,
>
> I am running koha17.05.04 on Lubuntu i386. WHen I try to upgrade koha, I am
> getting the following error. Can you please help me what is missing here?
>
> root@GSS-LIBRARY-SERVER:/home/gss-library-server# sudo apt-get install
> koha-common
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is
> not going to be installed
>Depends: libsearch-elasticsearch-perl but it is not going to
> be installed
>Depends: perl-modules-5.26 but it is not installable or
> libtest-simple-perl (>= 1.302073)
> E: Unable to correct problems, you have held broken packages.
> ___
> 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] DBMS auto increment issue - BUG19016

[Jonathan Druart]

The script on bug 19016 is supposed to deal with corrupted data correctly.
At least for issues/old_issues (read comment 13 carefully!). However
problems have been found for other tables, like items and biblio (see
comments 16 and 17).

On Fri, 21 Sep 2018 at 12:42 Luis Moises Rojas 
wrote:

> Hello everybody,
>
> We all know this is destructive, meanwhile, which is the better soluction
> in this case?
> Thanks
>
> El jue., 20 de sep. de 2018 a la(s) 19:01, Jonathan Druart (
> jonathan.dru...@bugs.koha-community.org) escribió:
>
>> Important note: This is a destructive method, you are going to lose
>> circulation data!
>>
>> Please do not forget to mention it when you suggest people to remove rows
>> from their tables :)
>>
>> On Thu, 20 Sep 2018 at 19:39 Luis Moises Rojas 
>> wrote:
>>
>>> Hi,
>>> I still do not know why this happen and when they going to fix it.
>>> I have several solutions which i am going to submit , but here is:
>>>
>>> Go to old_issues and delete those itemnumber. You can use the phpmyadmin
>>> or
>>> use the console
>>>
>>> Delete from old_issues where itemnumber=here goes your number
>>>
>>> El jue., 20 de sept. de 2018 4:05 PM, Sven Halm 
>>> escribió:
>>>
>>> > Hi all,
>>> >
>>> > i have got the BUG19016 (
>>> > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19016)
>>> problem
>>> > in my production environment. The koha system information says:
>>> >
>>> > ---start quote---
>>> > Problems found
>>> > Items
>>> >
>>> >
>>> > The following ids exist in both tables items and deleteditems :
>>> >
>>> > 1016, 1017 Checkouts
>>> >
>>> >
>>> > The following ids exist in both tables issues and old_issues :
>>> >
>>> > 587, 590, 589, 586, 584, 585, 588, 583, 582
>>> > ---end quote---
>>> >
>>> > After i had read the artikels i implemented the init script (see [
>>> > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix |
>>> > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix ] ).
>>> >
>>> > But how can i resolve the problem? I don't know how to do that.
>>> >
>>> > Could you help, please?
>>> >
>>> > Kind regards
>>> > Sven
>>> >
>>> > library: [ https://lesehoehle.foerderverein-hellwegschule.de/ |
>>> > https://lesehoehle.foerderverein-hellwegschule.de ]
>>> >
>>> > ___
>>> > 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
>>>
>>
> --
> *Luis Moisés Rojas P.*
>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Hea - any enhancement requests?

[Jonathan Druart]

Hi everybody,

I have been working on the Hea website (hea.koha-community.org) this
afternoon to fix an issue reported by Sonia [1].
I noticed that the display and the information of the libraries are
not always accurate and useful, but I have trouble providing something
that would be ergonomic.

There are 2 things to display: the Koha's installations and the libraries
A Koha installation can have several libraries (branches).
We have 3 views:
- See all libraries https://hea.koha-community.org/libraries
- See by country https://hea.koha-community.org/libraries-by-country
- See on a map https://hea.koha-community.org/libraries-on-a-map

On the map there are only the installations that are displayed.
Before today all libraries from all installations were displayed on
the "all libraries" view, one row per library. It is still as it but
they are now grouped by installation: for instance search for
"Bibliothèque université Lyon 3" and you will see the different
libraries for this installation. I feel like it is better but not
perfect. We should at least remove the second if there is only 1
library and that it has the same value as the installation.

On the "by country" I have not changed anything, but libraries are
displayed. It seems that it would be better to display the
installations instead.

Basically my feeling is that we should only display the installations
on the map, "by country" and maybe on "all libraries" as well. And the
details of the installation on the installation view (for instance
https://hea.koha-community.org/libraries/602 for Lyon 3).

I guess somebody else could think the contrary and prefer to highlight
"per library" instead of "per installation".

I am open to any suggestions, feel free to open issue on the tracker
of the project or simply by answering to this email.

Regards,
Jonathan

PS: Yes some old/wrong data must be removed. I planned to remove all
data that have not been updated in the last 6 months (which represent
~300 installations out of 1145), but actually some seem valid, so it
is certainly a bug somewhere...

[1] https://gitlab.com/koha-community/hea-app/issues/1
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] ACQUISITION ERROR

[Jonathan Druart]

Hello,
I do not recreate the error you have. Do you have access to the server
and the Koha log file?
There is certainly another error displayed in it that would help more.
Regards,
Jonathan
Le jeu. 13 déc. 2018 à 07:02, Igbudu Tersoo  a écrit :
>
> Hi great ones,
> we are using koha 18.05.06 running on ubuntu 18.04.1 LTS. the database is
> mysql ver14.14 Distrib 5.7.24, when i create a vendor from "New Vendor" and
> save. afterwards, from "search vendor" when i search for the vendor i just
> created, the search return "Your Search returned no results" . this means
> that the vendor i just created and saved is not in the database. please
> what can i do?
>
> Thank you in anticipation of your kind assistance.
>
> Murphy  Igbudu
> Systems Librarian
> University Library and Information Services
> Benue State University, Makurdi.
> +234-8038434748
> ___
> 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] upgrading from koha 3.0/debian lenny to koha 18/ubuntu 16

[Jonathan Druart]

Hi,
It's a known bug, see bug 21931 (there is a patch to test!)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21931
Regards,
jonathan
Le jeu. 13 déc. 2018 à 06:25, Tanzeem M.B  a écrit :
>
> Hi
>
> I am upgrading from koha 3.0.2 to a latest supported version.
> My present koha installation is koha version 3.0 installed in Debian Lenny
> In the new installation on another machine I have loaded ubuntu 16
> and installed the latest version of koha 18.
> I took the backup of koha from debian.
> Restored the database in the new installation of koha 18 in ubuntu16.
> Then upgraded the database schema
> and run zebra-rebuld indexing.
> which run successfully. I rebooted the system and loaded the installed koha
> in the browser with url
> http://.:8080
> and the web-installer got run again and after the update database step I
> got the following error
> ```Updating database structure
>
> Update report :
>
>- Status: 500
>- Content-type: text/html
>-
>- Software error:
>- DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column
>'me.weight' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 110
>- 
>- 
>- For help, please send mail to the webmaster (mailto:[no
>address given]">[no address given]), giving this error message
>- and the time and date of the error.
>-
>- 
>
> Update errors :
>
>- [Thu Dec 13 14:28:24 2018] updatedatabase.pl: DBD::mysql::st execute
>failed: Unknown column 'me.weight' in 'field list' [for Statement "SELECT
>`me`.`id`, `me`.`name`, `me`.`label`, `me`.`type`, `me`.`weight` FROM
>`search_field` `me` WHERE ( `me`.`name` = ? )" with ParamValues: 0='ta'] at
>/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1834.
>- [Thu Dec 13 14:28:24 2018] updatedatabase.pl:
>DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.weight' in
>'field list' at /usr/share/koha/lib/Koha/Objects.pm line 110
>
> ```
> Please help to move further.
>
> With Thanks & Regards
>
> Mr. Tanzeem M B
> +91 9446705956
>
> Thiruvananthapuram
> ___
> 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] quotation marks not displaying correctly

[Jonathan Druart]

Hi Elaine,

It's a bug indeed, could you fill a new bug report and assign it to me?

Cheers,
Jonathan
Le mar. 11 déc. 2018 à 16:20, Elaine Bradtke  a écrit :
>
> Quotation marks in our catalogue are displaying strangely.  I don't know
> how long it's been going on (we don't have many records with quotation
> marks). We're running 18.11
> Here's an example
> Fiddle tune history : bad tunes
> It should read Fiddle tune history : "bad" tunes
> https://catalogue.efdss.org/cgi-bin/koha/opac-detail.pl?biblionumber=78890
>
> I've cleared the cache, updated Chrome and also tested it in Firefox. Still
> there.
> Here's the strange part - if I go in and edit out the  and put in
> proper quotation marks, and save it, it seems to stick.  However, if I open
> the record for editing, even if I don't touch any fields, it changes back
> to   It also happens to quotation marks in other fields, not just the
> title.
> I couldn't find a bug reported for this, so I'm wondering if anyone else
> has seen this happen, or if it might be some internal problem?
>
> Elaine Bradtke
> VWML
> English Folk Dance and Song Society | http://www.efdss.org
> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> Song Society in London, England. If you wish to phone me personally, send
> an e-mail first. I work off site)
> --
> Registered Company No. 297142
> Charity Registered in England and Wales No. 305999
> ---
> "Writing about music is like dancing about architecture"
> --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
> ___
> 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 IN ACQUISITION MODULE

[Jonathan Druart]

John,

I have updated the page https://koha-community.org/download-koha/
To remove the " (up to version 5.6)" for MySQL requirement and add the
18.04 (Bionic Beaver). as supported distro.

Regards,
Jonathan
Le lun. 10 déc. 2018 à 10:10, John Sterbenz  a écrit :
>
> Hello Murphy,
>
> It is my understanding that 18.04 is not yet supported as an OS (16.04 is,
> though)--MySQL 5.7 is also not supported (version should be "up to 5.6"--or
> use MariaDB instead).
>
> If you're not too far along in your efforts, you might want to start over
> with that OS/SQL server configuration to see if that works.
>
> John
>
>
> -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=-
> John E. Sterbenz, Jr.
> Senior Associate Librarian
> Manager, Electronic Collections Administration
> 700 East University Avenue
> Kresge Hall, 4th Floor East
> Suite K4511
> Kresge Library Services
> The University of Michigan
> Ann Arbor, Michigan, USA 48109-1234
>
> TEL: (734) 764-5746
>
>
> On Mon, Dec 10, 2018 at 5:30 AM Igbudu Tersoo 
> wrote:
>
> > Hi Great ones,
> >
> > I am using koha 18.05 running on ubuntu 18.04 and database is Mysql ver
> > 14.14 Distrib 5.7.24. I am trying to set up the acquisition module. i have
> > set a library budget and created funds. afterwards, when i create a vendor
> > and save. i now go to manage orders to search for the vendor i just
> > created.  the error seen below pops up. please how do i resolve this?
> > thanks in advance.
> > Software error:
> >
> > Can't use an undefined value as an ARRAY reference at
> > /usr/lib/x86_64-linux-gnu/perl5/5.26/DBI.pm line 2081.
> >
> > For help, please send mail to the webmaster ([no address given]), giving
> > this error message and the time and date of the error.
> >
> > Murphy Igbudu
> >
> > System Librarian
> >
> > Benue State University
> >
> > Library & Information Services
> >
> > Makurdi. Nigeria.
> >
> > +234-8038434748
> > ___
> > 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] quotation marks not displaying correctly

[Jonathan Druart]

I have opened the bug report, a patch is coming soon:
Bug 21986 - quotation marks are wrongly escaped in several places
Note that it also impacts items and authorities edition
Le mer. 12 déc. 2018 à 09:14, Jonathan Druart
 a écrit :
>
> Hi Elaine,
>
> It's a bug indeed, could you fill a new bug report and assign it to me?
>
> Cheers,
> Jonathan
> Le mar. 11 déc. 2018 à 16:20, Elaine Bradtke  a écrit :
> >
> > Quotation marks in our catalogue are displaying strangely.  I don't know
> > how long it's been going on (we don't have many records with quotation
> > marks). We're running 18.11
> > Here's an example
> > Fiddle tune history : bad tunes
> > It should read Fiddle tune history : "bad" tunes
> > https://catalogue.efdss.org/cgi-bin/koha/opac-detail.pl?biblionumber=78890
> >
> > I've cleared the cache, updated Chrome and also tested it in Firefox. Still
> > there.
> > Here's the strange part - if I go in and edit out the  and put in
> > proper quotation marks, and save it, it seems to stick.  However, if I open
> > the record for editing, even if I don't touch any fields, it changes back
> > to   It also happens to quotation marks in other fields, not just the
> > title.
> > I couldn't find a bug reported for this, so I'm wondering if anyone else
> > has seen this happen, or if it might be some internal problem?
> >
> > Elaine Bradtke
> > VWML
> > English Folk Dance and Song Society | http://www.efdss.org
> > Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> > Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> > Song Society in London, England. If you wish to phone me personally, send
> > an e-mail first. I work off site)
> > --
> > Registered Company No. 297142
> > Charity Registered in England and Wales No. 305999
> > ---
> > "Writing about music is like dancing about architecture"
> > --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)
> > ___
> > 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] Hea - any enhancement requests?

[Jonathan Druart]

There is now a wiki page about Hea - https://wiki.koha-community.org/wiki/Hea
Le mer. 12 déc. 2018 à 19:34, Jonathan Druart
 a écrit :
>
> Hi everybody,
>
> I have been working on the Hea website (hea.koha-community.org) this
> afternoon to fix an issue reported by Sonia [1].
> I noticed that the display and the information of the libraries are
> not always accurate and useful, but I have trouble providing something
> that would be ergonomic.
>
> There are 2 things to display: the Koha's installations and the libraries
> A Koha installation can have several libraries (branches).
> We have 3 views:
> - See all libraries https://hea.koha-community.org/libraries
> - See by country https://hea.koha-community.org/libraries-by-country
> - See on a map https://hea.koha-community.org/libraries-on-a-map
>
> On the map there are only the installations that are displayed.
> Before today all libraries from all installations were displayed on
> the "all libraries" view, one row per library. It is still as it but
> they are now grouped by installation: for instance search for
> "Bibliothèque université Lyon 3" and you will see the different
> libraries for this installation. I feel like it is better but not
> perfect. We should at least remove the second if there is only 1
> library and that it has the same value as the installation.
>
> On the "by country" I have not changed anything, but libraries are
> displayed. It seems that it would be better to display the
> installations instead.
>
> Basically my feeling is that we should only display the installations
> on the map, "by country" and maybe on "all libraries" as well. And the
> details of the installation on the installation view (for instance
> https://hea.koha-community.org/libraries/602 for Lyon 3).
>
> I guess somebody else could think the contrary and prefer to highlight
> "per library" instead of "per installation".
>
> I am open to any suggestions, feel free to open issue on the tracker
> of the project or simply by answering to this email.
>
> Regards,
> Jonathan
>
> PS: Yes some old/wrong data must be removed. I planned to remove all
> data that have not been updated in the last 6 months (which represent
> ~300 installations out of 1145), but actually some seem valid, so it
> is certainly a bug somewhere...
>
> [1] https://gitlab.com/koha-community/hea-app/issues/1
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Remove 23.59 info on Slips

[Jonathan Druart]

Hi Giannis,

Try << table.field | dateonly >>

Regards,
Jonathan
Le mer. 5 déc. 2018 à 05:42, Giannis Tsakonas  a écrit :
>
> Dear colleagues
>
> we would like to erase the time section from the due date information on
> all slips. As far as we know, the JQuery below erases this piece of info
> on staff client and OPAC interfaces.
>
> $("#issuest td:contains('23:59')").each(function() {
> var text = $(this).text().replace('23:59', '');
> $(this).text(text);
> });
> $(".datedue:contains('23:59')").each(function() {
> var text = $(this).text().replace('23:59', '');
> $(this).text(text);
> });
>
> Testing this however, seems that it does not work on Slips. This creates
> a conflict between working hours and info that the users get through
> slips.
>
> Note: we do not do hourly loans.
>
> Any help will be very much appreciate.
>
> G
> ___
> 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] Help required for problem related with KOHA

[Jonathan Druart]

Hi, What is you version of Koha?
Le mar. 20 nov. 2018 à 02:53, D Thma  a écrit :
>
> Dear   ,
>
> Help is required to rectify the problem crop up while trying to access KOHA
> ...
>
> The problem generated is as follows :
> Software error:
>
> Can't call method "STORE" on an undefined value at
> /usr/share/perl5/DBIx/Connector.pm line 38.
> BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 88.
> Compilation failed in require at
> /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23.
> BEGIN failed--compilation aborted at
> /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23.
>
> For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
>
>
> Kindly advice...
>
>
> Thank You
> ___
> 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 IN ACQUISITION MODULE

[Jonathan Druart]

Hello,

Which exact version of Koha are you using? 18.05.?
Do you have another error displayed in the log file?

Regards,
Jonathan
Le lun. 10 déc. 2018 à 07:32, Igbudu Tersoo  a écrit :
>
> Hi Great ones,
>
> I am using koha 18.05 running on ubuntu 18.04 and database is Mysql ver
> 14.14 Distrib 5.7.24. I am trying to set up the acquisition module. i have
> set a library budget and created funds. afterwards, when i create a vendor
> and save. i now go to manage orders to search for the vendor i just
> created.  the error seen below pops up. please how do i resolve this?
> thanks in advance.
> Software error:
>
> Can't use an undefined value as an ARRAY reference at
> /usr/lib/x86_64-linux-gnu/perl5/5.26/DBI.pm line 2081.
>
> For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
>
> Murphy Igbudu
>
> System Librarian
>
> Benue State University
>
> Library & Information Services
>
> Makurdi. Nigeria.
>
> +234-8038434748
> ___
> 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 IN ACQUISITION MODULE

[Jonathan Druart]

Hi John,

This is not true, all supported versions of Koha include a trick to
support MySQL 5.7 and MariaDB 10.2.4 (see bug 20229).
Ubuntu 18.04 is also supported.

Regards,
Jonathan
Le lun. 10 déc. 2018 à 10:10, John Sterbenz  a écrit :
>
> Hello Murphy,
>
> It is my understanding that 18.04 is not yet supported as an OS (16.04 is,
> though)--MySQL 5.7 is also not supported (version should be "up to 5.6"--or
> use MariaDB instead).
>
> If you're not too far along in your efforts, you might want to start over
> with that OS/SQL server configuration to see if that works.
>
> John
>
>
> -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=-
> John E. Sterbenz, Jr.
> Senior Associate Librarian
> Manager, Electronic Collections Administration
> 700 East University Avenue
> Kresge Hall, 4th Floor East
> Suite K4511
> Kresge Library Services
> The University of Michigan
> Ann Arbor, Michigan, USA 48109-1234
>
> TEL: (734) 764-5746
>
>
> On Mon, Dec 10, 2018 at 5:30 AM Igbudu Tersoo 
> wrote:
>
> > Hi Great ones,
> >
> > I am using koha 18.05 running on ubuntu 18.04 and database is Mysql ver
> > 14.14 Distrib 5.7.24. I am trying to set up the acquisition module. i have
> > set a library budget and created funds. afterwards, when i create a vendor
> > and save. i now go to manage orders to search for the vendor i just
> > created.  the error seen below pops up. please how do i resolve this?
> > thanks in advance.
> > Software error:
> >
> > Can't use an undefined value as an ARRAY reference at
> > /usr/lib/x86_64-linux-gnu/perl5/5.26/DBI.pm line 2081.
> >
> > For help, please send mail to the webmaster ([no address given]), giving
> > this error message and the time and date of the error.
> >
> > Murphy Igbudu
> >
> > System Librarian
> >
> > Benue State University
> >
> > Library & Information Services
> >
> > Makurdi. Nigeria.
> >
> > +234-8038434748
> > ___
> > 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] Branches limitations for locations

[Jonathan Druart]

The problem is bigger I think, as it impacts all AVs (as well as
patron's categories - see bug 21255).
However this specific problem could indeed be solved quite easily with
the dynamic dropdowns.

Le mer. 19 déc. 2018 à 16:07, Joy Nelson  a écrit :
>
> I remember this feature from 3.12 (bugzilla 7919).  We've had libraries
> that have run into the same issue you have Sonia.  Generally we suggest
> that they add their branch (MAIN branch) to the branch limitations for all
> authorised values so that they can then see those values when cataloging.
> Conversely, we've had larger consortiums that set up a Technical Services
> branch that the catalogers are assigned to and that branch is then added to
> the list of the authorised values branch limitations.
>
> While both of those are 'free' workarounds for the library, I can see room
> for improvement in this area.  I talked to our educators and developers and
> thought these might make two great options to enhance this functionaliy.
>
> 1. Paul's idea to make the authorised value dropdowns change dynamically is
> nice.  Kyle mentioned this could be done with some javascript and an API
>
> 2. Our educators thought perhaps we should add a permission to the
> cataloging area that is something like "view and choose all authorized
> values".  So catalogers would have this particular option selected and all
> values would appear in the list for selection when creating items.
>
> -joy
>
> On Wed, Dec 19, 2018 at 9:24 AM Paul Poulain 
> wrote:
>
> > 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
> >
>
>
> --
> Joy Nelson
> Vice President of Implementations
>
> ByWater Solutions 
> Support and Consulting for Open Source Software
> Phone/Fax (888)900-8944
> What is 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] Software error - /usr/share/koha/intranet/cgi-bin/acqui/neworderempty.pl line 247.

[Jonathan Druart]

Hello Aliki,

Please upgrade to the latest 17.11.x (17.11.15) to confirm it is not
fixed already.

Regards,
Jonathan

Le mar. 26 févr. 2019 à 09:22, Aliki  a écrit :
>
> Hello everybody!
>
>
>
> It’s been 2 weeks that I’m trying to add a book suggestion to a vendor’s
> basket, and all I get when I click on the +order button, is the following
> message.
>
> Any ideas what is going wrong?
>
> *Software error:*
>
> Can't call method "effective_create_items" on an undefined value at
> /usr/share/koha/intranet/cgi-bin/acqui/neworderempty.pl line 247.
>
>
>
> Time zone in Athens (GMT+2)
>
> Monday, February 25, 2019, 4:19 PM
>
>
>
> *Koha version:*
>
> 17.11.05.000
>
> *OS version ('uname -a'):*
>
> Linux linuxsrv 3.16.0-6-686-pae #1 SMP Debian 3.16.56-1+deb8u1 (2018-05-08)
> i686
>
> *Perl interpreter:*
>
> /usr/bin/perl
>
> *Perl version:*
>
> 5.020002
>
>
>
> Best regards
> --
> Aliki Pavlidou
> ___
> 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] search result list is void of information

[Jonathan Druart]

Hi Giuseppe (cc the list I forgot in my previous answer),
I would try a full zebra reindex, then search for relevant
errors/warnings in the Koha log files if the reindex did not fix the
problem.
Regards,
Jonathan

Le mar. 19 févr. 2019 à 10:32, Giuseppe Ciaccio
 a écrit :
>
> On Tue, 19 Feb 2019, Jonathan Druart wrote:
>
> > Hi Giuseppe,
>
> Hello,
>
> > Did you modify the value of OPACXSLTResultsDisplay?
>
> No
>
> > Did you correctly chose the MARC flavour value during the installation 
> > process?
>
> Yes (it is unimarc in our case, and it was the same with previous install of 
> koha).
>
> Giuseppe
>
> > Regards,
> > Jonathan
> >
> > Le lun. 18 févr. 2019 à 09:07, giuseppe  a écrit 
> > :
> >>
> >> Hello all,
> >>
> >> I've replaced an old Koha 17.11 by a fresh install of Koha 18.11.  After
> >> install, as superlibrarian I successfully populated the DB with sample
> >> records including a couple of items, for test purposes.
> >>
> >> <http://koha.1045719.n5.nabble.com/file/t341209/Screenshot_2019-02-17_17-55-30.png>
> >>
> >> Afterwards, as normal user I tried a search for a keyword matching more 
> >> than
> >> one record, and thus I got a list of search results.
> >>
> >> <http://koha.1045719.n5.nabble.com/file/t341209/Screenshot_2019-02-18_12-38-57.png>
> >>
> >> The list is correct, but, as you can see, each entry is void of textual
> >> information -- no title/author/etc. .  If I click on the "image preview" of
> >> one single entry (not visible in the screenshot) I get access to the full
> >> info of that entry, which shows correct.  But the search results void of
> >> textual information is uninformative for a user.  This misbehaviour was not
> >> present in Koha 17.11.  Is this just a matter of misconfiguration?  What
> >> should I do to restore the original behaviour?
> >>
> >> Thank you.
> >>
> >>
> >>
> >> --
> >> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> >> ___
> >> 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] Koha 18.05 Patron search broken for non-superlibrarian users

[Jonathan Druart]

Hello Mai,

Which exact version are you using?
What you describe seems to have been fixed by bug 20998, which is part
of 18.05.02
Last 18.05.x release is 18.05.08

Regards,
Jonathan

Le jeu. 21 févr. 2019 à 14:36, Mai  a écrit :
>
> Dear all,
> We're experiencing problems with patron search on Koha 18.05
> When a non-superlibrarian staff member looks up a patron, the following
> error occurs:
>
> > Can't call method "branchcode" on an undefined value at
> > /usr/share/koha/intranet/cgi-bin/members/member.pl line 56,  line
> > 751.
>
> If the superlibrarian looks up the same user, It'll retrieve it correctly.
> Additionaly, If the non-superlibrarian staff member looks up the same
> patron from either the Circulation module or the "Check out" tab at Koha's
> Home, it's information is also retrieved correctly.
> Switching the non-superlibrarian staff member to superlibrarian fixes the
> issue but for obvious reasons, it's not ideal.
>
> This happens regardless of the patron we look up.
> Thanks in advance,
>
> --
> Maite Arakaki
> ___
> 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] koha 18.11.03 make test FAIL

[Jonathan Druart]

Hello Andi

Le mar. 12 mars 2019 à 22:40, Andi Sugandi  a écrit :
>
> Hi all,
>
> I am trying to install Koha on Ubuntu 18.04 via tar-ball.
> https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_tarball

Why not using the debian package?

> I already setup every preparations necessary.
>
> I run:
> #01. perl Makefile.PL
> http://paste.opensuse.org/view/simple/85793620
>
> #02. make
> http://paste.opensuse.org/view/simple/99861731
>
> #03. But fails in 'make test'
> http://paste.opensuse.org/view/simple/30313228
>
> How to investigate it?

The relevant error is:

"""
t/LangInstaller.t ... 1/39 Missing 'xgettext'
executable. Have you installed the gettext package?
"""
You need gettext to be installed.

> Is it related to "koha 17.05.00 make test FAIL"
> https://lists.katipo.co.nz/public/koha/2017-June/048140.html ?

Maybe, not sure.

> What do you suggest?

Install using the packages :)
https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages


> Thanks in advance.
>
> Best regards
> --
> Andi Sugandi.
> ___
> 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] Trying to use a template in Batch record modification

[Jonathan Druart]

Hi Michael,

For kidding I wanted to answer you that dots were missing.
But actually:
% echo '...'|wc -m # number of dots before ger
36
% echo '190315b |  00| 0 '|wc -m # all chars before ger
26

Maybe there are too many?

Regards,
Jonathan

Le ven. 15 mars 2019 à 15:42, Michael Kuhn  a écrit :
>
> Hi
>
> Currently some Koha newbies have forgotten to add the value "ger" in
> MARC 041$a when catalogueing, but they did add the correct value "ger"
> in MARC 008,35-37. However, this results in some missing entries in the
> language facet. The plain MARC view in the OPAC of such a record may
> look like this:
>
>   000 00216nam a22001097a 4500
>   999 _c470
>   _d470
>   003 OSt
>   005 20190315191317.0
>   008 190315b |  00| 0 ger d
>   040 _cOSt
>   245 _aTest
>   942 _2z
>   _cBK
>
> In fact it is missing
>
>   041 _ager
>
> Thus I tried using the MARC modification templates in Koha menu "Tools >
> Batch record modification", adding a template with the following action
> (as copied from the interface):
>
> Add new field 041$a with value ger if 008 matches RegEx
> m/^...ger..$/
>
> When I run this action over the given record, Koha tells me that the
> bibliographic record has successfully been modified - but in fact
> nothing has changed.
>
> Besides it is not possible to unload that record using "Data export",
> but it is there an can be searched via staff client and OPAC.
>
> What is wrong with my evil doing? Is it something with my regular
> expression?
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> ___
> 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] Are there alternatives to increase performance do Koha Library?

[Jonathan Druart]

Hello Victor,

Why do you want to increase performance? Is Koha slow? The search or any pages?
Which version of Koha are you using? Is Plack enabled? Memcached? Any
warnings on the about page?
Are you using Zebra or Elastic? If Zebra, are you using the Zebra
facets (use_zebra_facets in the config file)?
Did you read https://wiki.koha-community.org/wiki/Performance?

As you can see we need more information to answer you correctly.

Regards,
Jonathan

Le lun. 11 mars 2019 à 15:04, Victor Barroso Oliveira
 a écrit :
>
> Are there alternatives to increase performance do Koha Library?
> ___
> 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] No indication to patron that they have exceeded the allowed failed login attempts

[Jonathan Druart]

Hi Arturo,
See bug 21311 for the reason.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21311
Regards,
Jonathan

Le lun. 18 mars 2019 à 18:12, Arturo Longoria
 a écrit :
>
> Hello,
>
> I'm not sure if I've stumbled upon a bug, or if I'm not using the 
> FailedLoginAttempts system preference correctly -- could someone offer any 
> feedback? I'd be happy to file a bug report if it is indeed a bug!
>
> Our library is on 18.05.10. Our FailedLoginAttempts preference is set to 5. 
> When I purposely enter the wrong password to an account, I can see that the 
> login_attempts column for the user is incremented. But when it goes past 5, I 
> never see the message alerting me that I've exceeded my login attempts and 
> need to reset my password. Instead, I keep seeing the same standard message 
> warning me about it: "You entered an incorrect username or password. Please 
> try again! [...]"
>
> The bug indicates that I should be prompted to reset my password, but that 
> never happens 
> (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18314). And if I 
> enter the correct password after exceeding 5 login attempts, I'm still 
> blocked but without any useful feedback, so a patron would never know what's 
> happening even if they eventually remembered their password. Upon resetting 
> the password via the staff client, I can finally log in with the correct pw.
>
> Am I missing something? Or is this a bug?
>
> Thank you!
>
> Arturo Longoria
> Reference Librarian/Web Manager
> Texas State Law Library
> www.sll.texas.gov
> ___
> 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] Trying to use a template in Batch record modification

[Jonathan Druart]

Michael,

Yes indeed, it's a bug in Koha::SimpleMARC::field_equals, please report it.

Regards,
Jonathan

Le lun. 18 mars 2019 à 17:12, Michael Kuhn  a écrit :
>
> Hi Alvaro
>
>  >> How about changing a record with already with ger to any other
>  >> language?
>  >
>  >> I don't know exactly what you mean. Editing the record manually from
>  >> "ger" to any other MARC language code is no problem
>  >
>  > I mean you can try to use the batch record modification tool to change
>  > the "ger to "abc" for example and see if it does do the change as
>  > opposite of as when you "add" ger. With this we can test if it behaves
>  > differently between those cases and might give us a clue.
>  >
>  > In the test I'll use a language code that you do not use or does not
>  > exist so you can then easy spot those records and return the language
>  > code back to "ger" easily
>
> Ah, OK. But no, as far as I can see there is no possibility to use the
> batch record modification tool to change the content of a control field
> in this way (i. e. only position 35-37), since control fields are
> organized in a different way than the usual data fields. At the moment
> it seems to me this tool generally has some problems to deal with
> control fields and that may be the reason why it saves my action but
> doesn't do anything when I actually run it.
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Are there alternatives to increase performance do Koha Library?

[Jonathan Druart]

Hi Victor,

Please keep the list in copy.
I would suggest you to turn off the zebra facet (edit the Koha conf
and put '0' into use_zebra_facets).
Restart memcached and plack then try again.

Regards,
Jonathan

Le mer. 20 mars 2019 à 13:58, Victor Barroso Oliveira
 a écrit :
>
> Koho 18.11.03 and Zebra are using 100% CPU and causing slow access.
> How can I solve this problem?
>
>
> Em sex, 15 de mar de 2019 às 09:36, Jonathan Druart 
>  escreveu:
>>
>> Hello Victor,
>>
>> Why do you want to increase performance? Is Koha slow? The search or any 
>> pages?
>> Which version of Koha are you using? Is Plack enabled? Memcached? Any
>> warnings on the about page?
>> Are you using Zebra or Elastic? If Zebra, are you using the Zebra
>> facets (use_zebra_facets in the config file)?
>> Did you read https://wiki.koha-community.org/wiki/Performance?
>>
>> As you can see we need more information to answer you correctly.
>>
>> Regards,
>> Jonathan
>>
>> Le lun. 11 mars 2019 à 15:04, Victor Barroso Oliveira
>>  a écrit :
>> >
>> > Are there alternatives to increase performance do Koha Library?
>> > ___
>> > 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] unable to upload downloaded file from download folder

[Jonathan Druart]

Hello Rajesh,
Have a look at the about page, "System information" tab. You may see
warnings related to your problem.
Regards,
Jonathan

Le ven. 8 févr. 2019 à 05:38, takan bhatt  a écrit :
>
> Sir/Madam
>
> I am using Koha 18.11, mysql Ver 15.1 Distrib 10.0.36-MariaDB, Ubuntu
> 16.04. While I am trying to upload books in the field 856u, I am not able
> to upload file. I check xml file, path is ok. But at the same time, the
> uploads directory has not access to copy files. Kindly help me.
>
>
> Rajesh Bhatt
> Grims, VAPI
> India
> ___
> 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] Koha importing biblio with items error

[Jonathan Druart]

Hi Dorothy,

I do not think it's data related. How did you install Koha? Which version?
Do you have something in the JS console? Or something that could be
useful in the Koha logs?

Regards,
Jonathan

Le mar. 12 févr. 2019 à 09:14, Dorothy Chong
 a écrit :
>
> Hi everyone,
>
> Our library is hoping to transfer into Koha but has so far had issues with 
> staging the records with items. Without the 952 field it works fine, and it 
> also worked fine when it was just 952$a, $b, and $y. Whenever I try to stage 
> the file it just comes back with “fail to submit form: error”. What is the 
> problem with my MARC please?
>
> Also we have an issue with Zebra error message 10007 - what should we do with 
> that?
>
> =LDR  0nam a220Ia 4500
> =008  190212sxx000\\0\\und\\d
> =020  \\$a29177103
> =082  \\$a001.5 KRU
> =090  \\$a001.5 KRU
> =100  \\$aKrupar, Karen R.
> =245  \\$aCommunication Games :
> =245  \\$bParticipant's Manual /
> =250  \\$a.
> =264  \\$aU.S.A. :
> =264  \\$bThe Free Press,
> =264  \\$c1973
> =440  \\$a.
> =650  \\$aCommunication|Educational games
> =952  \\$a[library name]$b[library name]$o001.5 KRU$p05$yBook
>
> =LDR  0nam a220Ia 4500
> =008  190212sxx000\\0\\und\\d
> =020  \\$a.
> =082  \\$a001.94 WIL
> =090  \\$a001.94 WIL
> =100  \\$aWilson, Clifford
> =245  \\$aCrash go the chariots; an alternative to chariots of the Gods? /
> =250  \\$a.
> =264  \\$bHedges & Bell
> =440  \\$a.
> =650  \\$a.
> =952  \\$a[library name]$b[library name]$o001.94 WIL$p06$yBook
>
> Thanks very much,
> Dorothy
> ___
> 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] Koha Password Recovery

[Jonathan Druart]

Hello Peter,

Same as my previous answer, it seems that you modified the notice template. How?
You want to display the fields "surname" and "firstname", not "userid".

Regards,
Jonathan

Le ven. 15 févr. 2019 à 03:05, Peter Lau  a écrit :
>
> In the email that I received for the captioned, I don’t know when I was
> addressed with my email account (peter.lau) instead of my name (Peter Lau)
>
> Dear peter.lau
>
> This email has been sent in response to your password recovery request for
> the account *peter.lau*.
>
> You can now create your new password using the following link:
> http://koha.yccece.edu.hk//cgi-bin/koha/opac-password-recovery.pl?uniqueKey=$2a$08$vCwNb7rynR1t0PYc0w38ze
> 
>
> This link will be valid for 2 days from this email's reception, then you
> must reapply if you do not change your password.
>
> Thank you.
>
> Thanks & regards,
>
> *Peter Lau*
>
> Librarian
>
> Tel: (852) 3977 9868 | Email: peter@yccece.edu.hk | Fax: (852) 23384320
>
>  [image:
> https://docs.google.com/uc?export=download=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE5NNu=0BzpPRj4UE0XeT1R2WUt2dnhmTFBBeEpVR3dqcU5QbnF6NVg4PQ]
>
> 2 Tin Wan Hill Road, Tin Wan, Aberdeen
>
> *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk
> ___
> 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] FW: Koha password recovery

[Jonathan Druart]

Hi Peter,

The original content of this template starts with "This email has been
sent...", the "Dear" part does not exist.
It seems that you modified it, with which content?

Regards,
Jonathan

Le jeu. 3 janv. 2019 à 00:08, Peter Lau  a écrit :
>
> =?UTF-8?B?S29oYSBwYXNzd29yZCByZWNvdmVyeQ==?=
>
> I wonder if there’s a way to properly address the recipient of the user who
> has requested for a password change instead of just Dear [].
>
> Thanks & regards,
>
> *Peter Lau*
>
> Librarian
>
> Tel: (852) 3977 9868 | Email: peter@yccece.edu.hk | Fax: (852) 23384320
>
>  [image:
> https://docs.google.com/uc?export=download=1wiYZQsqhNTJZjyNbLJx-6ODZyoYE5NNu=0BzpPRj4UE0XeT1R2WUt2dnhmTFBBeEpVR3dqcU5QbnF6NVg4PQ]
>
> 2 Tin Wan Hill Road, Tin Wan, Aberdeen
>
> *YCCECE, Here We Grow Our Future | *www.yccece.edu.hk
>
>
>
> *From:* libr...@yccece.edu.hk [mailto:libr...@yccece.edu.hk]
> *Sent:* Thursday, 3 January 2019 11:03 AM
> *To:* peter@yccece.edu.hk
> *Subject:* Koha password recovery
>
>
>
> Dear [],
>
> This email has been sent in response to your password recovery request for
> the account *peter.lau*.
>
> You can now create your new password using the following link:
> http://koha.yccece.edu.hk//cgi-bin/koha/opac-password-recovery.pl?uniqueKey=$2a$08$77H6O2uz0p8X2G1QhFXv4e
> 
>
> This link will be valid for 2 days from this email's reception, then you
> must reapply if you do not change your password.
>
> Thank you.
> ___
> 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] Unable to upload "koha-coverflow-plugin-v2.4.25"

[Jonathan Druart]

Hi Murphy,

Did you verify the permissions of the plugins directory?
See the pluginsdir entry in the koha-conf.xml file

Regards,
Jonathan

Le ven. 25 janv. 2019 à 11:16, Igbudu Tersoo  a écrit :
>
> Hi,
> I am using koha 18.11 running on ubuntu 16.04. I am trying to upload the
> plugin file "koha-coverflow-plugin-v2.4.25" and am receiving this error
> message "*Cannot unpack file to the plugins directory. Please verify that
> the Apache user can write to the plugins directory". *
> Please i need help.
> Thank you.
>
> Murphy Igbudu
> Systems Librarian
> University Library and Information
> Services, Benue State University
> Makurdi. Nigeria.
> ___
> 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 show description of item type in ISSUESLIP

[Jonathan Druart]

Replace the whole checkedout "loop" with the FOR loop
The example in the test file should give you an idea about how to do that.


El vie., 17 may. 2019 07:49, Michael Kuhn  escribió:

> Hi Jonathan
>
> Thanks for the code! I have included it as follows, but in fact the
> whole thing is in another loop called "checkedout":
>
> 
> 
> <> <>
> [% USE ItemTypes %]
> [% FOREACH checkout IN checkouts %]
> [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> [% END %]
> Fällig am: <>
> 
> 
>
> I tested and there is some output now, but instead of
>
> Book1 Barcode1
> ItemtypeOfBook1
> Fällig am: DueDateBook1
>
> Book2 Barcode2
> ItemtypeOfBook2
> Fällig am: DueDateBook2
>
> it shows like this:
>
> Book1 Barcode1
> ItemtypeOfBook1
> ItemtypeOfBook2
> Fällig am: DueDateBook1
>
> Book2 Barcode2
> ItemtypeOfBook1
> ItemtypeOfBook2
> Fällig am: DueDateBook2
>
> Very often an issue slip does does contain more than two books so for
> example with seven checked out books for every single book all seven
> item types of all seven books are shown. Do maybe you know the solution
> to this problem?
>
> Unfortunately I couldn't find the place, where 
> or object variable "checkout" is documented. I have found Plugin
> "ItemTypes" in page
> https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit but
> it says it is "To be documented".
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
>
>
>
>
>
>
>
>
> Am 16.05.19 um 20:52 schrieb Jonathan Druart:
> > And so, this should work:
> >
> > [% USE ItemTypes %]
> > [% FOREACH checkout IN checkouts %]
> > [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> > [% END %]
> >
> > Le jeu. 16 mai 2019 à 13:46, Jonathan Druart
> >  a écrit :
> >>
> >> Sorry, I am completely wrong.
> >>
> >> See an example in the test file:
> t/db_dependent/Letters/TemplateToolkit.t
> >> The variable 'checkout' does not exist, you need to loop on
> >> 'checkouts' as there are several checkouts :)
> >>
> >> Le jeu. 16 mai 2019 à 13:42, Jonathan Druart
> >>  a écrit :
> >>>
> >>> Hi Michael,
> >>>
> >>> ISSUESLIP is not ready for TT syntax.
> >>> See also bug 15283.
> >>>
> >>> Regards,
> >>> Jonathan
> >>>
> >>> Le jeu. 16 mai 2019 à 09:40, Michael Kuhn  a écrit :
> >>>>
> >>>> Hi
> >>>>
> >>>> Our notice ISSUESLIP does contain the following lines:
> >>>>
> >>>> <> <>
> >>>> <>
> >>>> Fällig am: <>
> >>>>
> >>>> Unfortunately the content of field "items.itype" is coded, so the
> output
> >>>> of the middle line is just "06" or "20" instead of the actual
> >>>> description of the respectve item type (e. g. "CD" instead of 06, or
> >>>> "DVD" instead of 20). We have tried to replace "<> />" by
> >>>>
> >>>> [% IF items.itype == '06' %] CD
> >>>> [% ELSIF items.itype == '20' %] DVD
> >>>> [% ELSE %]
> >>>> [% END %]
> >>>>
> >>>> or
> >>>>
> >>>> [% IF ( items.itype == '06' ) %] CD
> >>>> [% ELSIF ( items.itype == '20' ) %] DVD
> >>>> [% ELSE %]
> >>>> [% END %]
> >>>>
> >>>> or
> >>>>
> >>>> [% IF ( items.itype == '06' ) %] CD[% END %]
> >>>> [% IF ( items.itype == '20' ) %] DVD[% END %]
> >>>>
> >>>> or
> >>>>
> >>>> [% SWITCH items.itype %]
> >>>> [% CASE '06' %] CD
> >>>> [% CASE '20' %] DVD
> >>>> [% END %]
> >>>>
> >>>> or
> >>>>
> >>>> [% IF items.itype %]
> >>>> [% USE ItemTypes %]
> >>>> [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> >>>> [% END %]
> >>>>
> >>>> Though, none of these worked - nothing happened. Can anyone please
> tell
> >>>> me the correct way how to achieve this, if this is possible at all?
> >>>>
> >>>> Best wishes: Michael
> >>>> --
> >>>> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg.
> Fachausweis
> >>>> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> >>>> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> >>>> ___
> >>>> 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] Install guide for current version

[Jonathan Druart]

Hi Narcis,

What do you suggest?
->Documentation
-->Documentation
will look weird :)

We already have that for "About", "Get involved", "KohaCon" and "Support".

Regards,
Jonathan

Le mar. 28 mai 2019 à 10:10, Narcis Garcia  a écrit :
>
> Some time ago I annotated this path:
> www.koha-community.org
> -> Documentation
> --> Install
> ---> Koha on Debian
>
> in my recipe for new installs.
> And today I was becoming crazy to find this, because I only was seeing
> Unsupported versions documentation.
>
> As a suggestion for website menus: Add a menu item instead of only
> depending on menu caption.
> ___
> 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] Koha 18.11 - LC Authorities dataset upload - Free-floating subdivisions

[Jonathan Druart]

Hi Craig,

This sounds like a bug, GEN_SUBDIV should be a defined. Could you open
a bug report?

Regards,
Jonathan

Le ven. 31 mai 2019 à 09:36, Craig Butosi  a écrit :
>
> Hi everyone,
>
> After some playing around, I discovered that the authority records were
> given a Koha-specific value of "GEN_SUBDIV" in field 942 (this tag is
> hidden by default so it will not appear in the editor screen before you
> make it display). I therefore created a new authority type in
> Administration with the code "GEN_SUBDIV" and linked it to authority field
> 180 and bingo, the Internal Server Error disappears:
>
> http://library.craigbutosi.ca/cgi-bin/koha/opac-authoritiesdetail.pl?authid=3436
>
> I have yet to see if this fix applies to all of the subdivisions in my
> file. When I have some quiet time, I'll review.
>
> All best,
>
> Craig Butosi, MA, MLIS, B Mus (Hons)
> Library: library.craigbutosi.ca
>
>
>
> On Fri, May 31, 2019 at 10:16 AM Craig Butosi  wrote:
>
> > Hi Katrin,
> >
> > Thanks for your reply. Interestingly, when you navigate to a subdivision
> > authority record from the staff client, you can get to the MARC data just
> > fine. For example,
> >
> > Subdivision: *Effect of logging on:*
> >
> > Tab 0: https://www.dropbox.com/s/fdlwh5o3ja7uzff/Subdiv1.PNG?dl=0
> > Tab 1: https://www.dropbox.com/s/13xc61qaypfo4fz/Subdiv2.PNG?dl=0
> > Tab 6: https://www.dropbox.com/s/ft0lhw8pd0en08z/Subdiv3.PNG?dl=0
> >
> > Plack Error:
> >
> > I have a smattering of the following error in the plack log file:
> > "Can't call method "authtypetext" on an undefined value at
> > /usr/share/koha/opac/cgi-bin/opac/opac-authoritiesdetail.pl line 89."
> > which seems to coincide with attempting to click the "Details" button on
> > the authorities list from the OPAC.
> >
> > I wonder if this error occurs because there is no defined authority type
> > for free-floating subdivisions?
> >
> > All best,
> >
> > Craig Butosi, MA, MLIS, B Mus (Hons)
> > Library: library.craigbutosi.ca
> >
> >
> >
> > On Mon, May 27, 2019 at 3:24 PM Katrin Fischer 
> > wrote:
> >
> >> Hi Craig,
> >>
> >> what's the error in your plack error log that appears with the Internal
> >> server error? Could you give an example of how these free-floating
> >> subdivisions look like in MARC? What is the field for the main heading?
> >>
> >> It could be a bug or requiring an enhancement - a bit hard to tell
> >> without knowing more. Having an internal server error is never nice, so
> >> filing a bug might make sense anyway.
> >>
> >> Katrin
> >>
> >> On 09.05.19 14:52, Craig Butosi wrote:
> >> > Hi everyone,
> >> >
> >> > Koha 18.11 on Ubuntu 16.04 (MariaDb)
> >> >
> >> > I recently discovered that the Library of Congress has released their
> >> 2014
> >> > authorities as a free, open-access dataset in Marc8, xml, and Utf8
> >> formats.
> >> > This is great! (
> >> > https://www.loc.gov/cds/products/MDSConnect-subject_authorities.html)
> >> >
> >> > I am in the process of batch uploading the subject authority file into
> >> my
> >> > instance of Koha. I'm about half complete (or about 220,000 entries).
> >> >
> >> > I noticed, however, that the file includes free-floating subdivisions,
> >> > which are part of the dataset as their own record as if they were main
> >> > headings. These have been uploaded as such into my system.
> >> >
> >> > I get an "Internal Server Error" page if I attempt to click on the
> >> Details
> >> > button of any of these sub-divisions in the OPAC authority browse page.
> >> Not
> >> > a huge deal, but something that should be mentioned. E.g.,
> >> >
> >> http://library.craigbutosi.ca/cgi-bin/koha/opac-authoritiesdetail.pl?authid=3436
> >> > )
> >> >
> >> > I was wondering if this should be treated as a bug, and if anyone has
> >> done
> >> > something similar and is (or is not) getting the same error.
> >> >
> >> > I reindexed zebra after uploading, but the error persists.
> >> >
> >> > Thanks all,
> >> >
> >> > Craig Butosi, MA, MLIS, B Mus (Hons)
> >> > Library: library.craigbutosi.ca
> >> > ___
> >> > 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
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Cannot find records created in KoHa

[Jonathan Druart]

Or KOHA, but only if you want to shout how much you love it.

Le ven. 31 mai 2019 à 14:49, Chris Cormack  a écrit :
>
> Just a quick off topic reply, as I've seen a few people spell Koha as KoHa.
> It is a te reo Māori word and can be spelt Koha or koha
>
> Here's a slide about the name from last week at Kohacon19
> https://slides.com/ranginui/kohacon19#/2
>
> Chris
>
> On Sat, 1 Jun 2019, 1:58 AM Lichtsteiner Patric (lici), 
> wrote:
>
> > Hi,
> >
> > I guess this is a very basic and silly question.
> >
> > I just created my first record with some items. Among other things I
> > filled in the field "Number (ISBN)” with 100.100.
> >
> > Using the advanced catalog search I’m trying to find my record, but
> > nothing is found:
> > No results match your search for 'nb: 100.100'.
> >
> > What did I miss?
> >
> > Best,
> > Patric
> > ___
> > 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] invalid data, cannot decode object

[Jonathan Druart]

Hello Ron,

What is the return of the following SQL query:
select biblionumber, metadata from biblio_metadata where id=1;

Regards,
Jonathan

Le dim. 16 juin 2019 à 03:54, Ronald Vyhmeister
 a écrit :
>
> Dear Colleagues,
>
>
>
> We’ve turned up a new error… when I do a search from the user interface, I
> get this error
>
>
>
> Invalid data, cannot decode object (id=16037, format=marcxml, schema=MARC21)
>
>
>
> The id number changes depending on the search.
>
>
>
> The weird thing is that if logged into the –intra site, the search works
> normally.
>
>
>
> We’re running Koha 19.05 with all the updates in place.
>
>
>
> Thanks in advance for your assistance.
>
>
>
> Ron
>
> -
> Ronald Vyhmeister, PhD
> Academic Dean
> IT Manager
> Middle East University
> Beirut, Lebanon
> ronald.vyhmeis...@meu.edu.lb
> Mobile:+961-81767015
> Office: +961 1 685-800 x 102
>
> US: +1 301-244-9191
> Technology is dominated by two kinds of people:
> Those who manage what they do not understand
> and those who understand that which they do not manage.
> ___
> 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] Unwanted e-mail about UseTransportCostMatrix

[Jonathan Druart]

Hi Michael,
Restart memcached and plack to make sure the pref's value is not
fetched from the cache.
The code raising this warning is pretty trivial:

189 my $use_transport_cost_matrix =
C4::Context->preference("UseTransportCostMatrix");
190 if ($use_transport_cost_matrix) {
191 $transport_cost_matrix = TransportCostMatrix();
192 unless (keys %$transport_cost_matrix) {
193 warn "UseTransportCostMatrix set to yes, but matrix
not populated";

Le mar. 25 juin 2019 à 03:30, Michael Kuhn  a écrit :
>
> Hi
>
> Since two days I am receiving the following unwanted e-mail from my demo
> installation (running Koha 19.05.00) every hour:
>
> ##
>
> Subject: Cron cd / && run-parts --report /etc/cron.hourly
>
>
> /etc/cron.hourly/koha-common:
> UseTransportCostMatrix set to yes, but matrix not populated at
> /usr/share/koha/lib/C4/HoldsQueue.pm line 193.
>
> ##
>
> But in fact system preference "UseTransportCostMatrix" is NOT set to yes:
>
> mysql> select value from systempreferences where
> variable="UseTransportCostMatrix";
> +---+
> | value |
> +---+
> | 0 |
> +---+
> 1 row in set (0.00 sec)
>
>
> What does it mean and how can I prevent getting this unwanted e-mail?
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> ___
> 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] invalid data, cannot decode object

[Jonathan Druart]

It means you have missing biblio_metadata for some of your
bibliographic records.

Is it a new fresh install? Did you just upgrade to 19.05? How did you
import your records?

The following SQL query will return the biblionumber that do not have
a biblio_metadata entry:
SELECT COUNT(*) FROM biblio b LEFT JOIN biblio_metadata m ON
b.biblionumber=m.biblionumber WHERE m.biblionumber IS NULL;

Le mer. 19 juin 2019 à 01:19, Ronald Vyhmeister
 a écrit :
>
> Here's what we get using ID = 1
>
>  0 row(s) returnedIf the item is one that exists, here is the result.
> Any assistance
> appreciated.
>
> |23684 | 
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.loc.gov/MARC21/slim
> http://www.loc.gov/standards
> /marcxml/schema/MARC21slim.xsd"
> xmlns="http://www.loc.gov/MARC21/slim;>
>
>   00952nam a2200253Ia 4500
>   20190321165616.0
>   0930624s1991cau   000 0 eng
> d
>   190321sxx000 0 und
> d
>   
> DLC
>   
>   
> eng
>   
>   
> DLC
>   
>   
> DLC
>   
>   
> Cerna, Miguel Angel
>   
>   
> The power of small groups in the church
>   
>   
> Miguel Angel Cerna
>   
>   
> Newbury Park, CA
>   
>   
> El Camino Pub
>   
>   
> c1991
>   
>   
> 243 p
>   
>   
> 22 cm
>   
>   
> The Power of Small Groups in the Church tells how
> your churc
> h can be organized and inspired to witness with dramatic results.  This book
> will b
> e an effective guide to every pastor who wants his church to grow.  It will
> help re
> volutionize your ministry.   I highly recommend it!quot;  Dr. Werner
> Vyhmeiste
> r, Dean of Theological Seminary, Andrews University
>   
>   
> Divina commedia
>   
>   
> BK
>   
>   
> 23684
> 23685
>   
> 
>
> -
> Ronald Vyhmeister, PhD
> Academic Dean
> IT Manager
> Middle East University
> Beirut, Lebanon
> ronald.vyhmeis...@meu.edu.lb
> Mobile:+961-81767015
> Office: +961 1 685-800 x 102
> US: +1 301-244-9191
> Technology is dominated by two kinds of people:
> Those who manage what they do not understand
> and those who understand that which they do not manage.
>
>
> -Original Message-
> From: Jonathan Druart 
> Sent: Wednesday, June 19, 2019 3:55 AM
> To: Ronald Vyhmeister 
> Cc: koha 
> Subject: Re: [Koha] invalid data, cannot decode object
>
> Hello Ron,
>
> What is the return of the following SQL query:
> select biblionumber, metadata from biblio_metadata where id=1;
>
> Regards,
> Jonathan
>
> Le dim. 16 juin 2019 à 03:54, Ronald Vyhmeister
>  a écrit :
> >
> > Dear Colleagues,
> >
> >
> >
> > We’ve turned up a new error… when I do a search from the user
> > interface, I get this error
> >
> >
> >
> > Invalid data, cannot decode object (id=16037, format=marcxml,
> > schema=MARC21)
> >
> >
> >
> > The id number changes depending on the search.
> >
> >
> >
> > The weird thing is that if logged into the –intra site, the search
> > works normally.
> >
> >
> >
> > We’re running Koha 19.05 with all the updates in place.
> >
> >
> >
> > Thanks in advance for your assistance.
> >
> >
> >
> > Ron
> >
> > --
> > ---
> > Ronald Vyhmeister, PhD
> > Academic Dean
> > IT Manager
> > Middle East University
> > Beirut, Lebanon
> > ronald.vyhmeis...@meu.edu.lb
> > Mobile:+961-81767015
> > Office: +961 1 685-800 x 102
> >
> > US: +1 301-244-9191
> > Technology is dominated by two kinds of people:
> > Those who manage what they do not understand and those who understand
> > that which they do not manage.
> > ___
> > 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 Koha staff theme plugin

[Jonathan Druart]

Hi Frido,
Do you have screenshots? :)
Cheers,
Jonathan

Le mer. 19 juin 2019 à 08:42, Fridolin SOMERS
 a écrit :
>
> Hi
>
> I'm proud to give you a new Koha staff theme plugin :
> https://github.com/biblibre/koha-plugin-theme-intranet-lsd
>
> You should read the README ;)
>
> Have fun XD
>
> --
> Fridolin SOMERS 
> BibLibre, France - software and system maintainer
> ___
> 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] Regarding the KOHA old version migration issue

[Jonathan Druart]

No output from a linux command means: everything is ok!
Did you try a full reindexation to fix the search problem?

Le lun. 6 mai 2019 à 02:32, Rejeesh K.Nair  a
écrit :

> Dear Jonathan,
>
> Thanks for your mail.
>
> We have executed the following commands, but the same didn't provide any
> response and the search module is not working.
>
> root@kslc:~# koha-zebra restart koha_library
> root@kslc:~# koha-zebra status koha_library
> root@kslc:~# koha-zebra start koha_library
>
> Thanks & Regards,
> *Rejeesh K.Nair* | Senior Software Engineer
> Web Designing and Development | Web Hosting
> Email:rejeeshkn...@gmail.com |
> rejeeshkn...@yahoo.com
> Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
> Mob: +91 (0) 9495316906
> Find Me : Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn
> <http://in.linkedin.com/in/rejeeshknair>|Twitter
> <https://twitter.com/rejeeshknair>|Google+
> <https://plus.google.com/+RejeeshKNair>
>
> Disclaimer : This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify us.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
> *Please consider the environment before printing this email.*
>
>
> On Sat, May 4, 2019 at 6:58 PM Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Hello,
>> It's not an error, it's a warning ("Deprecated script used").
>> It means that the script is going to be removed in upcoming versions.
>> You can use the script koha-zebra instead, with the stop/start/restart
>> parameters, to not get this warning.
>> Regards,
>> Jonathan
>>
>> Le sam. 4 mai 2019 à 01:36, Rejeesh K.Nair  a
>> écrit :
>> >
>> > Hi Owen,
>> >
>> > Thanks for your mail.
>> >
>> > Please see the below link.
>> >
>> > https://ibb.co/K7ddjz0
>> >
>> > Thanks & Regards,
>> > *Rejeesh K.Nair* | Senior Software Engineer
>> > Web Designing and Development | Web Hosting
>> > Email:rejeeshkn...@gmail.com |
>> > rejeeshkn...@yahoo.com
>> > Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
>> > Mob: +91 (0) 9495316906
>> > Find Me : Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn
>> > <http://in.linkedin.com/in/rejeeshknair>|Twitter
>> > <https://twitter.com/rejeeshknair>|Google+
>> > <https://plus.google.com/+RejeeshKNair>
>> >
>> > Disclaimer : This email and any files transmitted with it are
>> confidential
>> > and intended solely for the use of the individual or entity to whom they
>> > are addressed. If you have received this email in error please notify
>> us.
>> > This message contains confidential information and is intended only for
>> the
>> > individual named. If you are not the named addressee you should not
>> > disseminate, distribute or copy this e-mail. Please notify the sender
>> > immediately by e-mail if you have received this e-mail by mistake and
>> > delete this e-mail from your system. If you are not the intended
>> recipient
>> > you are notified that disclosing, copying, distributing or taking any
>> > action in reliance on the contents of this information is strictly
>> > prohibited.
>> > *Please consider the environment before printing this email.*
>> >
>> >
>> > On Fri, May 3, 2019 at 5:11 PM Owen Leonard 
>> wrote:
>> >
>> > > > Please see the below image for your reference.
>> > >
>> > > This mailing list doesn't accept attachments, so you'll need to post
>> > > the image somewhere else and provide a link.
>> > >
>> > >   -- Owen
>> > >
>> > > --
>> > > Web Developer
>> > > Athens County Public Libraries
>> > > https://www.myacpl.org
>> > > ___
>> > > 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] How to show description of item type in ISSUESLIP

[Jonathan Druart]

Hi Michael,

This test
https://gitlab.com/koha-community/Koha/blob/master/t/db_dependent/Letters/TemplateToolkit.t#L602
will show you the exact equivalent of the template ISSUESLIP using the TT
syntax.

You can use both syntax in the same template, but you have to use the
variables that exist. Which means you shouldn't use the TT syntax inside a
 loop. I would suggest you to rewrite the whole template using
the TT syntax, it will make it easier to write and more readable.

Regards,
Jonathan

El vie., 17 may. 2019 11:17, Michael Kuhn  escribió:

> Hi Jonathan
>
>  > Replace the whole checkedout "loop" with the FOR loop
>  > The example in the test file should give you an idea about how to do
>  > that.
>
> What test file do you mean? I can't find any hint on what the construct
> "" actually does, neither in the Koha wiki nor
> in the Koha manual.
>
> Unfortunately I don't seem to understand the different concepts between
>  and TT-Plugins at all...
>
> Indeed the page
> https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit says
> "You can mix an match (use hungry alligators <> together
> with TT syntax) in one notice template" but after all it's me who's all
> mixed up...
>
> Can you please enlighten me, or give me the link to some kind of
> documentation?
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
>
>
>
> > El vie., 17 may. 2019 07:49, Michael Kuhn  > <mailto:m...@adminkuhn.ch>> escribió:
> >
> > Hi Jonathan
> >
> > Thanks for the code! I have included it as follows, but in fact the
> > whole thing is in another loop called "checkedout":
> >
> > 
> > 
> > <> <>
> > [% USE ItemTypes %]
> > [% FOREACH checkout IN checkouts %]
> > [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %] />
> > [% END %]
> > Fällig am: <>
> > 
> > 
> >
> > I tested and there is some output now, but instead of
> >
> > Book1 Barcode1
> > ItemtypeOfBook1
> > Fällig am: DueDateBook1
> >
> > Book2 Barcode2
> > ItemtypeOfBook2
> > Fällig am: DueDateBook2
> >
> > it shows like this:
> >
> > Book1 Barcode1
> > ItemtypeOfBook1
> > ItemtypeOfBook2
> > Fällig am: DueDateBook1
> >
> > Book2 Barcode2
> > ItemtypeOfBook1
> > ItemtypeOfBook2
> > Fällig am: DueDateBook2
> >
> > Very often an issue slip does does contain more than two books so for
> > example with seven checked out books for every single book all seven
> > item types of all seven books are shown. Do maybe you know the
> solution
> > to this problem?
> >
> > Unfortunately I couldn't find the place, where
> > 
> > or object variable "checkout" is documented. I have found Plugin
> > "ItemTypes" in page
> > https://wiki.koha-community.org/wiki/Notices_with_Template_Toolkit
> but
> > it says it is "To be documented".
> >
> > Best wishes: Michael
> > --
> > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg.
> Fachausweis
> > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> > T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch
> > <mailto:m...@adminkuhn.ch> · W www.adminkuhn.ch <
> http://www.adminkuhn.ch>
> >
> >
> >
> >
> >
> >
> >
> >
> > Am 16.05.19 um 20:52 schrieb Jonathan Druart:
> >  > And so, this should work:
> >  >
> >  > [% USE ItemTypes %]
> >  > [% FOREACH checkout IN checkouts %]
> >  > [% ItemTypes.GetDescription(checkout.item.effective_itemtype)
> > %]
> >  > [% END %]
> >  >
> >  > Le jeu. 16 mai 2019 à 13:46, Jonathan Druart
> >  >  > <mailto:jonathan.dru...@bugs.koha-community.org>> a écrit :
> >  >>
> >  >> Sorry, I am completely wrong.
> >  >>
> >  >> See an example in the test file:
> > t/db_dependent/Letters/TemplateToolkit.t
> >  >> The variable 'checkout' does not exist, you need to loop on
> >  >> 'checkouts' as there are several checkouts :)
> >  >

Re: [Koha] How to show description of item type in ISSUESLIP

[Jonathan Druart]

Hi Michael,

ISSUESLIP is not ready for TT syntax.
See also bug 15283.

Regards,
Jonathan

Le jeu. 16 mai 2019 à 09:40, Michael Kuhn  a écrit :
>
> Hi
>
> Our notice ISSUESLIP does contain the following lines:
>
> <> <>
> <>
> Fällig am: <>
>
> Unfortunately the content of field "items.itype" is coded, so the output
> of the middle line is just "06" or "20" instead of the actual
> description of the respectve item type (e. g. "CD" instead of 06, or
> "DVD" instead of 20). We have tried to replace "<>" by
>
> [% IF items.itype == '06' %] CD
> [% ELSIF items.itype == '20' %] DVD
> [% ELSE %]
> [% END %]
>
> or
>
> [% IF ( items.itype == '06' ) %] CD
> [% ELSIF ( items.itype == '20' ) %] DVD
> [% ELSE %]
> [% END %]
>
> or
>
> [% IF ( items.itype == '06' ) %] CD[% END %]
> [% IF ( items.itype == '20' ) %] DVD[% END %]
>
> or
>
> [% SWITCH items.itype %]
> [% CASE '06' %] CD
> [% CASE '20' %] DVD
> [% END %]
>
> or
>
> [% IF items.itype %]
> [% USE ItemTypes %]
> [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> [% END %]
>
> Though, none of these worked - nothing happened. Can anyone please tell
> me the correct way how to achieve this, if this is possible at all?
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> ___
> 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 show description of item type in ISSUESLIP

[Jonathan Druart]

Sorry, I am completely wrong.

See an example in the test file: t/db_dependent/Letters/TemplateToolkit.t
The variable 'checkout' does not exist, you need to loop on
'checkouts' as there are several checkouts :)

Le jeu. 16 mai 2019 à 13:42, Jonathan Druart
 a écrit :
>
> Hi Michael,
>
> ISSUESLIP is not ready for TT syntax.
> See also bug 15283.
>
> Regards,
> Jonathan
>
> Le jeu. 16 mai 2019 à 09:40, Michael Kuhn  a écrit :
> >
> > Hi
> >
> > Our notice ISSUESLIP does contain the following lines:
> >
> > <> <>
> > <>
> > Fällig am: <>
> >
> > Unfortunately the content of field "items.itype" is coded, so the output
> > of the middle line is just "06" or "20" instead of the actual
> > description of the respectve item type (e. g. "CD" instead of 06, or
> > "DVD" instead of 20). We have tried to replace "<>" by
> >
> > [% IF items.itype == '06' %] CD
> > [% ELSIF items.itype == '20' %] DVD
> > [% ELSE %]
> > [% END %]
> >
> > or
> >
> > [% IF ( items.itype == '06' ) %] CD
> > [% ELSIF ( items.itype == '20' ) %] DVD
> > [% ELSE %]
> > [% END %]
> >
> > or
> >
> > [% IF ( items.itype == '06' ) %] CD[% END %]
> > [% IF ( items.itype == '20' ) %] DVD[% END %]
> >
> > or
> >
> > [% SWITCH items.itype %]
> > [% CASE '06' %] CD
> > [% CASE '20' %] DVD
> > [% END %]
> >
> > or
> >
> > [% IF items.itype %]
> > [% USE ItemTypes %]
> > [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> > [% END %]
> >
> > Though, none of these worked - nothing happened. Can anyone please tell
> > me the correct way how to achieve this, if this is possible at all?
> >
> > Best wishes: Michael
> > --
> > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> > T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> > ___
> > 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 show description of item type in ISSUESLIP

[Jonathan Druart]

And so, this should work:

[% USE ItemTypes %]
[% FOREACH checkout IN checkouts %]
[% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
[% END %]

Le jeu. 16 mai 2019 à 13:46, Jonathan Druart
 a écrit :
>
> Sorry, I am completely wrong.
>
> See an example in the test file: t/db_dependent/Letters/TemplateToolkit.t
> The variable 'checkout' does not exist, you need to loop on
> 'checkouts' as there are several checkouts :)
>
> Le jeu. 16 mai 2019 à 13:42, Jonathan Druart
>  a écrit :
> >
> > Hi Michael,
> >
> > ISSUESLIP is not ready for TT syntax.
> > See also bug 15283.
> >
> > Regards,
> > Jonathan
> >
> > Le jeu. 16 mai 2019 à 09:40, Michael Kuhn  a écrit :
> > >
> > > Hi
> > >
> > > Our notice ISSUESLIP does contain the following lines:
> > >
> > > <> <>
> > > <>
> > > Fällig am: <>
> > >
> > > Unfortunately the content of field "items.itype" is coded, so the output
> > > of the middle line is just "06" or "20" instead of the actual
> > > description of the respectve item type (e. g. "CD" instead of 06, or
> > > "DVD" instead of 20). We have tried to replace "<>" by
> > >
> > > [% IF items.itype == '06' %] CD
> > > [% ELSIF items.itype == '20' %] DVD
> > > [% ELSE %]
> > > [% END %]
> > >
> > > or
> > >
> > > [% IF ( items.itype == '06' ) %] CD
> > > [% ELSIF ( items.itype == '20' ) %] DVD
> > > [% ELSE %]
> > > [% END %]
> > >
> > > or
> > >
> > > [% IF ( items.itype == '06' ) %] CD[% END %]
> > > [% IF ( items.itype == '20' ) %] DVD[% END %]
> > >
> > > or
> > >
> > > [% SWITCH items.itype %]
> > > [% CASE '06' %] CD
> > > [% CASE '20' %] DVD
> > > [% END %]
> > >
> > > or
> > >
> > > [% IF items.itype %]
> > > [% USE ItemTypes %]
> > > [% ItemTypes.GetDescription(checkout.item.effective_itemtype) %]
> > > [% END %]
> > >
> > > Though, none of these worked - nothing happened. Can anyone please tell
> > > me the correct way how to achieve this, if this is possible at all?
> > >
> > > Best wishes: Michael
> > > --
> > > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> > > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> > > T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> > > ___
> > > 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] Regarding the KOHA old version migration issue

[Jonathan Druart]

No output from a linux command means: everything is ok!
Did you try a full reindexation to fix the search problem?

Le mer. 8 mai 2019 à 01:37, Rejeesh K.Nair  a
écrit :

> Hi,
>
> Gentle reminder regarding my previous mail.
>
> Thanks & Regards,
> *Rejeesh K.Nair* | Senior Software Engineer
> Web Designing and Development | Web Hosting
> Email:rejeeshkn...@gmail.com |
> rejeeshkn...@yahoo.com
> Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
> Mob: +91 (0) 9495316906
> Find Me : Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn
> <http://in.linkedin.com/in/rejeeshknair>|Twitter
> <https://twitter.com/rejeeshknair>|Google+
> <https://plus.google.com/+RejeeshKNair>
>
> Disclaimer : This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify us.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
> *Please consider the environment before printing this email.*
>
>
> On Mon, May 6, 2019 at 1:02 PM Rejeesh K.Nair 
> wrote:
>
>> Dear Jonathan,
>>
>> Thanks for your mail.
>>
>> We have executed the following commands, but the same didn't provide any
>> response and the search module is not working.
>>
>> root@kslc:~# koha-zebra restart koha_library
>> root@kslc:~# koha-zebra status koha_library
>> root@kslc:~# koha-zebra start koha_library
>>
>> Thanks & Regards,
>> *Rejeesh K.Nair* | Senior Software Engineer
>> Web Designing and Development | Web Hosting
>> Email:rejeeshkn...@gmail.com |
>> rejeeshkn...@yahoo.com
>> Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
>> Mob: +91 (0) 9495316906
>> Find Me : Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn
>> <http://in.linkedin.com/in/rejeeshknair>|Twitter
>> <https://twitter.com/rejeeshknair>|Google+
>> <https://plus.google.com/+RejeeshKNair>
>>
>> Disclaimer : This email and any files transmitted with it are
>> confidential and intended solely for the use of the individual or entity to
>> whom they are addressed. If you have received this email in error please
>> notify us. This message contains confidential information and is intended
>> only for the individual named. If you are not the named addressee you
>> should not disseminate, distribute or copy this e-mail. Please notify the
>> sender immediately by e-mail if you have received this e-mail by mistake
>> and delete this e-mail from your system. If you are not the intended
>> recipient you are notified that disclosing, copying, distributing or taking
>> any action in reliance on the contents of this information is strictly
>> prohibited.
>> *Please consider the environment before printing this email.*
>>
>>
>> On Sat, May 4, 2019 at 6:58 PM Jonathan Druart <
>> jonathan.dru...@bugs.koha-community.org> wrote:
>>
>>> Hello,
>>> It's not an error, it's a warning ("Deprecated script used").
>>> It means that the script is going to be removed in upcoming versions.
>>> You can use the script koha-zebra instead, with the stop/start/restart
>>> parameters, to not get this warning.
>>> Regards,
>>> Jonathan
>>>
>>> Le sam. 4 mai 2019 à 01:36, Rejeesh K.Nair  a
>>> écrit :
>>> >
>>> > Hi Owen,
>>> >
>>> > Thanks for your mail.
>>> >
>>> > Please see the below link.
>>> >
>>> > https://ibb.co/K7ddjz0
>>> >
>>> > Thanks & Regards,
>>> > *Rejeesh K.Nair* | Senior Software Engineer
>>> > Web Designing and Development | Web Hosting
>>> > Email:rejeeshkn...@gmail.com |
>>> > rejeeshkn...@yahoo.com
>>> > Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
>>> > Mob: +91 (0) 9495316906
>>> > Find Me : Facebook <https://www.facebook.com/rejeeshnairk>|LinkedIn
>>> > <http://in.linkedin.com/in/rejeeshknair>|Twitter
>>> > <https://twitter.com/rejeeshknair&

Re: [Koha] Upgrading from Koha 17.11 to 18.11 --- anything to watch out for?

[Jonathan Druart]

Hi Chris,
It does not depend on the Koha version, but the MySQL/MariaDB version,
please double check the wiki page.
https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
Regards,
Jonathan

Le mar. 2 avr. 2019 à 02:58, Chris Brown  a écrit :
>
> Hi Hector,
>
> Thank you for your advice -- I will keep it in mind. We plan to upgrade
> over Easter when the libraries that we support will all be closed. I will
> take a full snapshot of the server (virtual machine) first so we can roll
> back if disaster strikes, and we already keep off-machine daily backups.
>
> Do I still need to apply the "auto increment fix" in 18.11?
>
> Chris Brown
>
>
> On Mon, Apr 1, 2019 at 11:00 PM Hector Gonzalez  wrote:
>
> > Hello, you should have a complete backup that you trust and know how to
> > restore.  Both the database and the host files.
> >
> > Also, if the upgrade includes your database server, the upgrade may fail,
> > as the upgrade might turn mysql off and leave it off while other packages
> > -like koha-common- get upgraded, and koha-common requires mysql to be up,
> > in order to upgrade your database schema.  Make sure your mysql/mariadb
> > packages are upgraded before letting koha upgrade.
> >
> > Other than that, it should be that simple.
> >
> > Hector Gonzalez.
> >
> > > On Mar 31, 2019, at 1:09 PM, Chris Brown  wrote:
> > >
> > > Hello,
> > >
> > > We are currently running Koha 17.11 (installed from Debian packages) on
> > > Debian 9.3, and we want to upgrade to Koha 18.11
> > >
> > > Is it really as simple as:
> > >
> > > sudo apt-get update
> > > sudo apt-get upgrade
> > >
> > > or is there anything else I need to watch out for? For example, do I need
> > > to take action to update the database schema?
> > >
> > > Best Regards,
> > >
> > > Chris Brown
> > > ___
> > > 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
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Regarding the KOHA old version migration issue

[Jonathan Druart]

Hello,
It's not an error, it's a warning ("Deprecated script used").
It means that the script is going to be removed in upcoming versions.
You can use the script koha-zebra instead, with the stop/start/restart
parameters, to not get this warning.
Regards,
Jonathan

Le sam. 4 mai 2019 à 01:36, Rejeesh K.Nair  a écrit :
>
> Hi Owen,
>
> Thanks for your mail.
>
> Please see the below link.
>
> https://ibb.co/K7ddjz0
>
> Thanks & Regards,
> *Rejeesh K.Nair* | Senior Software Engineer
> Web Designing and Development | Web Hosting
> Email:rejeeshkn...@gmail.com |
> rejeeshkn...@yahoo.com
> Web: www.rejeeshknair.com |Skype:rejeeshkalliyilnair
> Mob: +91 (0) 9495316906
> Find Me : Facebook |LinkedIn
> |Twitter
> |Google+
> 
>
> Disclaimer : This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify us.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
> *Please consider the environment before printing this email.*
>
>
> On Fri, May 3, 2019 at 5:11 PM Owen Leonard  wrote:
>
> > > Please see the below image for your reference.
> >
> > This mailing list doesn't accept attachments, so you'll need to post
> > the image somewhere else and provide a link.
> >
> >   -- Owen
> >
> > --
> > Web Developer
> > Athens County Public Libraries
> > https://www.myacpl.org
> > ___
> > 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] Koha 19.05 Invalid data, cannot decode object (id=, format=marcxml, schema=MARC21)

[Jonathan Druart]

You can paste the result of the following query:
select metadata from biblio_metadata where id=2;

Le mer. 26 juin 2019 à 08:25, Eugen Bastron
 a écrit :
>
> Hello Jonathan,
>
> The upgrade process from version 18 was without errors.
>
> Count =1
>
> How can I check the XML?
>
> Bevor upgrade was details-option ok.
>
> Mit besten Grüßen/С уважением
> IT-Manager
> Eugen Bastron/Евгений Бастрон
>
> Am 26.06.19, 16:15 schrieb "Jonathan Druart" 
> :
>
> Hi Eugen,
>
> Same problem, same questions :)
>
> The error says that the XML data in biblio_metadata.metadata is not
> correct (or does not exist).
>
> Try: select count(*) from biblio_metadata where id=2;
> It will tell you if the metadata for this bibliographic record exists or 
> not.
> If it exists => my guess is that the XML is incorrect
> If it does not exist, additional question => from which version did
> you upgrade? Maybe you got an error during the upgrade process?
>
> Regards,
> Jonathan
>
> Le mer. 26 juin 2019 à 05:57, Eugen Bastron
>  a écrit :
> >
> > Dear Colleagues,
> >
> > after update to the Version 19.05 I cant see any details in catalog.
> >
> > The detail script get the Software error. Searching is running without 
> problems.
> >
> > 
> cgi-bin/koha/catalogue/detail.pl?biblionumber=2=scs_1561546292007
> >
> > Software error:
> > Invalid data, cannot decode object (id=2, format=marcxml, schema=MARC21)
> >
> >
> > All of the data in the catalog I have imported as MARC21.
> >
> > I have already tried to truncate the database and reimport the data.
> >
> > Any solutions?
> >
> > I think it is the same error:
> > https://www.mail-archive.com/koha@lists.katipo.co.nz/msg24021.html
> >
> >
> > Mit besten Grüßen,
> >
> > Eugen Bastron
> > IT-Manager
> >
> > Deutsches Historisches Institut Moskau
> >
> > ___
> > 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] Koha 19.05 Invalid data, cannot decode object (id=, format=marcxml, schema=MARC21)

[Jonathan Druart]

Hi Eugen,

Same problem, same questions :)

The error says that the XML data in biblio_metadata.metadata is not
correct (or does not exist).

Try: select count(*) from biblio_metadata where id=2;
It will tell you if the metadata for this bibliographic record exists or not.
If it exists => my guess is that the XML is incorrect
If it does not exist, additional question => from which version did
you upgrade? Maybe you got an error during the upgrade process?

Regards,
Jonathan

Le mer. 26 juin 2019 à 05:57, Eugen Bastron
 a écrit :
>
> Dear Colleagues,
>
> after update to the Version 19.05 I cant see any details in catalog.
>
> The detail script get the Software error. Searching is running without 
> problems.
>
> cgi-bin/koha/catalogue/detail.pl?biblionumber=2=scs_1561546292007
>
> Software error:
> Invalid data, cannot decode object (id=2, format=marcxml, schema=MARC21)
>
>
> All of the data in the catalog I have imported as MARC21.
>
> I have already tried to truncate the database and reimport the data.
>
> Any solutions?
>
> I think it is the same error:
> https://www.mail-archive.com/koha@lists.katipo.co.nz/msg24021.html
>
>
> Mit besten Grüßen,
>
> Eugen Bastron
> IT-Manager
>
> Deutsches Historisches Institut Moskau
>
> ___
> 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] Koha 17.05 randomly repeating an earlier transaction.

[Jonathan Druart]

Hi Raymund,

I would also check the access logs around this timestamp.

Regards,
Jonathan

Le ven. 12 avr. 2019 à 03:29, Raymund Delahunty
 a écrit :
>
> We have recently had two examples of what appears to be Koha issuing an item 
> to a reader “by itself” without any staff member doing the operation. Both 
> took place at the same library site, and same issue desk, but different staff 
> users logged on. We are multi-site, multi-issue desk, with heavy use of 
> self-issue, but the problem is only reported (so far) using Circulation (so 
> no SIP2 traffic), and at the one location. Yesterday we received this:
> “This morning Koha decided to randomly issue an item to a student. The 
> student wasn't present- she only emailed us once she had automatic 
> notification of her borrowing the item. The item was issued at 10:13 today. 
> This never happened. We still have the item in our cupboard. It looks like 
> Koha duplicated the student's previous transaction that had taken place a 
> couple of days earlier. Neither of us on the desk issued the item, or 
> remember anything unusual. Could it be that when we logged into Koha, it had 
> that transaction still in its memory somehow”)
> Our support company have advised: “We have investigated this transaction in 
> the logs but there isn't anything to indicate what might have happened.  It 
> is recorded as a checkout in the standard way.
> |  29319123 | 2019-04-09 10:13:04 | 341304 | CIRCULATION | ISSUE  |  370312 | 
> 1407873
> I'm afraid there isn't very much more we can do regarding this […]”
> The previous example was sort-of similar- a laptop was returned by a user and 
> it was *immediately* issued to a staff member who had borrowed (and returned) 
> the item *the previous day*. She immediately complained that she was at her 
> office, and away from the library, and had NOT borrowed the laptop.
> Has anyone experience this? Any ideas what we should look for? Thanks for any 
> suggestions.
> Ray Delahunty
> University of the Arts London
> This email and any attachments are intended solely for the addressee and may 
> contain confidential information. If you are not the intended recipient of 
> this email and/or its attachments you must not take any action based upon 
> them and you must not copy or show them to anyone. Please send the email back 
> to us and immediately and permanently delete it and its attachments. Where 
> this email is unrelated to the business of University of the Arts London or 
> of any of its group companies the opinions expressed in it are the opinions 
> of the sender and do not necessarily constitute those of University of the 
> Arts London (or the relevant group company). Where the sender's signature 
> indicates that the email is sent on behalf of UAL Short Courses Limited the 
> following also applies: UAL Short Courses Limited is a company registered in 
> England and Wales under company number 02361261. Registered Office: 
> University of the Arts London, 272 High Holborn, London WC1V 7EY
> ___
> 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] invalid data, cannot decode object

[Jonathan Druart]

Hello,

Please take a look at bug 23425, I have provided a patch to try and
understand the cause of the problem.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23425

Regards,
Jonathan

Le lun. 29 juil. 2019 à 07:42, dolf  a écrit :
>
> I'm getting the same error with one book. We also haven't seen this error
> before version 19.05.
> Here is the offending MARC record:
>
> MariaDB [koha_rsc]> select * from biblio_metadata where biblionumber=39335;
> *** 1. row ***
>   id: 32057
> biblionumber: 39335
>   format: marcxml
>   schema: MARC21
> metadata: 
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.loc.gov/MARC21/slim
> http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd;
> xmlns="http://www.loc.gov/MARC21/slim;>
>
>   00588nam a22001931a 4500
>   
> 39335
> 39335
>   
>   264910
>   OSt
>   20190712083916.0
>   130225s1966dk |  |||
> 0|eng||
>   
> RSC
>   
>   
> Hammershaimb, E.
>   
>   
> Some aspects of Old Testament prophecy from Isaiah to
> Malachi /
> by E. Hammershaimb.
>   
>   
> K p3 s�benhavn :
> Rosenkilde og Bagger,
> 1966.
>   
>   
> 116 p. ;
> 24 cm.
>   
>   
> Teologiske Skrifter ;
> 4
>   
>   
> Bible
> O.T.
> Prophets
> Criticism, interpretation, etc.
>   
>   
> Prophecy.
>   
>   
> ddc
> BOOK
>   
> 
>
> Could it be a unicode issue? See field $260a.
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> 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] Problem with showing next result in Staff search

[Jonathan Druart]

Hello Claes,

I can recreate the issue on master and 17.11.00, so it seems that it
is a long standing bug.
Could you open a bug report?

Does someone remember it has worked at some point?

Regards,
Jonathan

Le mer. 21 août 2019 à 03:09, Claes Eriksson  a écrit :
>
> Thank you Katrin for your reply.
>
> Following your test scheme I could be a little bit more detailed. There is a 
> difference if I go to page 2 or any other page, let us use page 4. We have 
> number of results presented set to 50  and this is what happen:
>
> - Search a common term that gives multiple result pages
> - Navigate to the second page
> - Open detail page for last result on the page  CLAES: that is record no 100
> - Click next: Note the title of the record   CLAES: error - I get record 51. 
> Should be no 101
> - Go back to search results using link  CLAES: I land on page 2, which in a 
> way is correct since last shown detailed record was 51 on page 2
> (- Record is the first on page 3 that I ended up on)
>
> I start all over again and  repeat the scheme but navigate to page 4 instead:
> - Search a common term that gives multiple result pages
> - Navigate to the second page   CLAES: Navigate to page 4 instead
> - Open detail page for last result on the page CLAES: that is record no 200
> - Click next: Note the title of the record  CLAES: error - I still get record 
> 51. Should be no 201
> - Go back to search results using link CLAES: Now I land on page 5, which is 
> correct if I in the last step had seen the details of record 201. This 
> behavior is different than above.
>
> It is absolutely not the most acute problem we have but it is a little bit 
> odd.
>
> BR Claes
>
> -Original Message-
> From: Koha  On Behalf Of Katrin Fischer
> Sent: den 19 augusti 2019 08:07
> To: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Problem with showing next result in Staff search
>
> Hi Claes,
>
> I've tried to replicate this in our 18.11.x installation, but saw the 
> expected behavior:
>
> - Search a common term that gives multiple result pages
> - Navigate to the second page
> - Open detail page for last result on the page
> - Click next: Note the title of the record
> - Go back to search results using link
> - Record is the first on page 3 that I ended up on
>
> Do you have any local changes that could cause this?
>
> Katrin
>
>
> On 09.08.19 12:04, Claes Eriksson wrote:
> > Hello,
> >
> > After an advanced search in Staff client which retrieve more than 100 
> > results or at least 3 pages of results (we show 50 on every page), I go to 
> > result 100 on page 2 and show details for that record.
> > When I then click on the link "Next" (result) I expect to see record 101 on 
> > page 3. Instead I get number 51 on page 2.
> > (It seems that the browser is redirected to result page 1 - during a
> > fraction of a second I see result page 1.) Following this I can click 
> > "Return to results" and will be sent to page 2.
> >
> > I cannot find anything in Bugzilla about this and I will file a new bug if 
> > I am correct.
> > We are on Koha version: 18.11.08.000
> >
> >
> > Best regards
> > Claes
> > 
> > Claes Eriksson
> > Systems Librarian
> >
> > Department of Communication, Marketing and Library (KOMBI) Swedish
> > National Road and Transport Research Institute (VTI) VTI, SE-581 95
> > Linkoeping, Sweden
> > Tel: +46-13-20 40 00  Direct: +46-13-20 41 99
> > E-mail: claes.eriks...@vti.se
> >
> >
> > ___
> > 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
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha upgrade from 3.2 to 19.05

[Jonathan Druart]

Hello Walid,

It should be as simple as:
- Backup your DB
- Create a new Koha installation using the debian packages
- Restore the DB dump
- Login and execute the upgrade using the web interface

Regards,
Jonathan

Le jeu. 22 août 2019 à 09:44, Sultan Qaboos Cultural Center Library
 a écrit :
>
> Hello,
>
> Our library is planning to upgrade Koha from the version 3.2 to 19.05
> (latest).
>
> Could you please give us a complete tutorial, system requirements, and the
> things we have to do (backup ?, etc,) before starting the upgrade.
>
> Is it possible to upgrade directly from 3.2 to 19.05 ? or we have to
> upgrade to lower versions before?
>
> Best regards,
> Walid
>
>
> --
> *Sultan Qaboos Cultural Center Library*
> 1100 16th St, NW
> Washington, DC 20036
> libr...@sqcc.org
> 202-677-3967, x104
> ___
> 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] items.fine is zero although fines are calculated

[Jonathan Druart]

Hello Stephan,

It should still work. Are you using the default template?
From which version did you upgrade?

Regards,
Jonathan

Le mer. 21 août 2019 à 20:15, zefanja  a écrit :
>
> Hello,
>
> I have a strange problem: Fines are calculated and shown in the fines
> tab of a user, but in our overdue notice (email) fines are 0.00. We use
> <> in our template and it worked till our upgrade to 19.05.
> Is items.fine deprecated or did I miss something?
>
> Our Koha version: 19.05.02.000
>
> Best Regards,
> Stephan
> ___
> 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 while Staging MARC records

[Jonathan Druart]

Hi Elaine,
It means that something went wrong. You should get a more complete error.
Can you copy the whole error message?
Regards,
Jonathan

Le ven. 23 août 2019 à 12:29, Elaine Bradtke  a écrit :
>
> Can anyone tell me what this might mean?
> Software error:
> /usr/share/koha/intranet/cgi-bin/tools/stage-marc
> Elaine Bradtke
> VWML
> English Folk Dance and Song Society | http://www.efdss.org
> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> Song Society in London, England. If you wish to phone me personally, send
> an e-mail first. I work off site)
> --
> Registered Company No. 297142
> Charity Registered in England and Wales No. 305999
> ___
> 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 while Staging MARC records

[Jonathan Druart]

Heh, was a bit late here! :)

Le dim. 1 sept. 2019 à 12:41, Jonathan Druart
 a écrit :
>
> Hi Elaine,
> It means that something went wrong. You should get a more complete error.
> Can you copy the whole error message?
> Regards,
> Jonathan
>
> Le ven. 23 août 2019 à 12:29, Elaine Bradtke  a écrit :
> >
> > Can anyone tell me what this might mean?
> > Software error:
> > /usr/share/koha/intranet/cgi-bin/tools/stage-marc
> > Elaine Bradtke
> > VWML
> > English Folk Dance and Song Society | http://www.efdss.org
> > Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
> > Tel+44 (0) 20 7485 2206 (This number is for the English Folk Dance and
> > Song Society in London, England. If you wish to phone me personally, send
> > an e-mail first. I work off site)
> > --
> > Registered Company No. 297142
> > Charity Registered in England and Wales No. 305999
> > ___
> > 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