[Koha] Koha 18.05.00.000: Search in Group of Libraries not working after upgrade

[Ata ur Rehman]

Dear All

After upgrading to 18.05.00 from 17.11, searching catalog by limiting to a
group of libraries (OPAC and Staff Client) is not working.  I have come to
know that Library Groups have been re-designed as hierarchy of libraries (
*Bug 15707*
 ) and I
tried to redefine all my groups/sub-groups but still no luck.

Note:  Searching in any single library or All Libraries is working fine
both in OPAC and Staff Client

Thanks in anticipation for any suggestion/advice, please

Regards,

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

Re: [Koha] Listing all biblio records

[Indranil Das Gupta]

Hi Ah Win,

On Tue 29 May, 2018, 9:47 PM Ah Win,  wrote:

We are using one very simple software using MS Access for our school
> libraries in Myanmar and now we would like to use Koha integrated system.
> We would like to import our bibliographic data into Koha and now we are
> testing.
>

Being an MS Access based system it will be easy to export it out as a
spreadsheet. However that's where usually the fun begins :-) the first
thing to identify is whether all your data is in Latin script (i.e.
english) OR if your data also includes data in Burmese script. And if any
data in Burmese script - is it Unicode (UTF-8) or does it involve any ASCII
font replacement hacks for rendering it.

Next is to clean up the data, perform de-duplication of the items (holdings
data) and link them to unique bibliographic records. Now if your old
aoftware had uawd any internal unique key for linking the tables, you can
use this key as your de-duplication key OR if all your records have ISBN
that is also a good dedup key to use.

And while you do all that, you will be required to map your data into
proper marc21 fields as most legacy software are unlikely to be marc
compliant. This is a *crucial* step, where your librarian skills along with
IT skills will get tested the maximum.

Once you have de-duplicated the data, you have to add to the holdings
information like item-level-type, branch codes and also biblio level
itemtype to the biblio records.

Your next stop will be the MarcEdit software where you will need to
generate the unique biblio records marc file as well as the holdings marc
file. And finally if everything goes ok you will have to merge them to get
a new marc file. This is the file that you will import into Koha.

Word of advice if your final marc file is over 1000 Bibliographic records,
it will be helpful if you use MarcEdit to split it up into multiple files
of 1000 records each. Koha will have an easy time ingesting a 1000 records
file at a time, rather than one with say 25,000 records.

That's basically the story of any legacy migration from a non-MARC21
dataset.

Cheers
Indranil.




> Thank you again for your suggestion.
>
> Best regards,
> Ah Win
>
>
>
>
>
>
>
>
>
>
>
>
>
> Ah Win
>
> Vice-President (1)
> Myanmar Library Association
>
>
>
> On 29 May 2018 at 11:07, Father Vlasie  wrote:
>
>> Dear Ah Win,
>>
>> The SQL examples from this page:
>> https://wiki.koha-community.org/wiki/SQL_Reports_Library
>>
>> Can be copied and pasted into the custom SQL reports in Home › Reports
>> (your-koha-install/cgi-bin/koha/reports/reports-home.pl)
>>
>> 1) Copy the SQL from the sample
>>
>> 2) On the Reports page choose + Create from SQL
>>
>> 3) Enter a name for the report
>>
>> 4) Paste in the sample in the SQL box and click Save.
>>
>> 5) Click Saved Reports in the left hand column
>>
>> 6) Click Run on the report you would like.
>>
>> Let us know if it works.
>>
>> Father Vlasie
>>
>> St. Photios Orthodox Theological Seminary
>> 510 Collier Way, Etna, CA 96027, U.S.A.
>> 
>>
>> Website: www.spots.school
>>
>>
>> On 28 May 2018, at 20:29, Ah Win  wrote:
>>
>> Dear Indranil,
>>
>> I am new to the list and librarian from Myanmar.
>>
>> Please help me the way if we are not handy with SQL.
>> For both import and export, please.
>>
>> Many thanks.
>> Ah Win
>>
>>
>>
>>
>>
>>
>> On 27 May 2018 at 03:37, Indranil Das Gupta  wrote:
>>
>>> On Sun 27 May, 2018, 2:33 AM Father Vlasie,  wrote:
>>>
>>> > Hello everyone,
>>> >
>>> > Is there an easy way to export a list of all items in a Koha database?
>>> >
>>>
>>> If you are handy with SQL, take a look at
>>> https://wiki.koha-community.org/wiki/SQL_Reports_Library
>>>
>>> Particularly at the section Bibliographic / Catalogue reports.
>>>
>>>
>>>
>>> > TIA
>>> > FV
>>> > ___
>>> > 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] Proxy Error after MariaDB upgrade to 10.2.14

[JanM]

Hi Barton, 

this work perfect. 

user@www2:~$ user@www2:~$ sudo koha-list
-bash: user@www2:~$: command not found
user@www2:~$ [sudo] password for user:
-bash: [sudo]: command not found
user@www2:~$ library
-bash: library: command not found
user@www2:~$ sudo koha-mysql library
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 1174405
Server version: 10.2.14-MariaDB-log openSUSE package

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.

MariaDB [testothek2]>




###


Currently running the "Upgrading database schema for library" again, these
are the errors so far after a few hours: 

Upgrading database schema for library

DBD::mysql::db do failed: Lost connection to MySQL server during query [for
Statement "
SELECT * FROM systempreferences WHERE 1 = 0 "] at
/usr/share/koha/lib/Koha/Database.pm line 109.


DBD::mysql::st execute failed: Lost connection to MySQL server during query
[for Statement "SELECT `me`.`variable`, `me`.`value`, `me`.`options`,
`me`.`explanation`, `me`.`type` FROM `systempreferences` `me` WHERE (
`me`.`variable` = ? )" with ParamValues: 0='version'] at
/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1834.



--
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] Staff Login Statistics

[Mr Mutsikiwa Admire]

We are interested in establishing login statistics by our library staff. 
If possible even listing the actions that were done by a given staff as 
that which appears in the patron modification log


--

Kind Regards,

Admire Mutsikiwa (Mr)
ICT Manager
Libraries
University of Zimbabwe
Tel:+263-4-303276
Mob:+263782476883

“It is easy to dodge our responsibilities, but we cannot dodge the 
consequences of dodging our responsibilities.”  Josiah Charles Stamp


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

Re: [Koha] Fwd: OPAC Page not available and login credentials don't work

[Indranil Das Gupta]

As a community we have stopped supporting LiveDVD as a option for
installation since around 2012-13.

The moment you release a LiveDVD based system, it is already stale. In many
cases LiveDVDs are custom forks with undocumented tweaks that make these a
liability if the creator is not responsive enough.

Cheers
Indranil.



On Tue 29 May, 2018, 6:07 PM takan bhatt,  wrote:

> After updating in Debian 9, OPAC is working smoothly. no issues.
> Sometimes, I wonder that kiya is easy to install in debian and many blogs
> are useful and directing well. Any windows user can install Koha just using
> copy paste in terminal from Vimal Kumar's Koha Geek, also bug fixing is
> possible. Then why we go for Live DVD.. Earlier, I tried live DVD (Koha on
> Ubuntu MATE) but I found bit slow on my machine compared to pure debian 9
> +Koha.  Others may have their openion. But my experience is that community
> is helping us (I am also new) Thanks Koha Community
>
> On Tue 29 May, 2018, 5:55 PM Mark Alexander,  wrote:
>
> > Excerpts from Bedanta Borah's message of 2018-05-28 10:45:54 -0700:
> > > 2) In case of  koha livedvd, all features were doing fine untill I
> > updated
> > > the system and the koha-common packages. After the update, my root user
> > and
> > > password (koha_library & koha123) stopped working. But I can login with
> > > another patron which I had created before the update was done. Why I
> > loose
> > > database user access after updating the software?
> > >
> > > Q) How can I regain the database user access?
> >
> > I'm not sure if the following will help, but I did notice something
> > that may be related in the release notes for 18.05 here:
> >
> >   https://koha-community.org/koha-18-05-released/
> >
> > Here is what they say about this issue:
> >
> >   No more login with the database user
> >
> >   It is no longer possible to use the database user to login into Koha.
> >   You should first create a superlibrarian patron and use it for logging
> > in.
> >   [...]
> >   It is no longer possible to use the database user (defined in
> > koha-conf.xml) to login into Koha.
> >   You should first create a superlibrarian patron and use it for logging
> > in.
> >   See the script misc/devel/create_superlibrarian.pl
> >
> > This was discussed in this bug:
> >
> >   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489
> > ___
> > 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] Fwd: OPAC Page not available and login credentials don't work

[takan bhatt]

After updating in Debian 9, OPAC is working smoothly. no issues.
Sometimes, I wonder that kiya is easy to install in debian and many blogs
are useful and directing well. Any windows user can install Koha just using
copy paste in terminal from Vimal Kumar's Koha Geek, also bug fixing is
possible. Then why we go for Live DVD.. Earlier, I tried live DVD (Koha on
Ubuntu MATE) but I found bit slow on my machine compared to pure debian 9
+Koha.  Others may have their openion. But my experience is that community
is helping us (I am also new) Thanks Koha Community

On Tue 29 May, 2018, 5:55 PM Mark Alexander,  wrote:

> Excerpts from Bedanta Borah's message of 2018-05-28 10:45:54 -0700:
> > 2) In case of  koha livedvd, all features were doing fine untill I
> updated
> > the system and the koha-common packages. After the update, my root user
> and
> > password (koha_library & koha123) stopped working. But I can login with
> > another patron which I had created before the update was done. Why I
> loose
> > database user access after updating the software?
> >
> > Q) How can I regain the database user access?
>
> I'm not sure if the following will help, but I did notice something
> that may be related in the release notes for 18.05 here:
>
>   https://koha-community.org/koha-18-05-released/
>
> Here is what they say about this issue:
>
>   No more login with the database user
>
>   It is no longer possible to use the database user to login into Koha.
>   You should first create a superlibrarian patron and use it for logging
> in.
>   [...]
>   It is no longer possible to use the database user (defined in
> koha-conf.xml) to login into Koha.
>   You should first create a superlibrarian patron and use it for logging
> in.
>   See the script misc/devel/create_superlibrarian.pl
>
> This was discussed in this bug:
>
>   https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489
> ___
> 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] Proxy Error after MariaDB upgrade to 10.2.14

[Barton Chittenden]

Jan,

Do you have console access to the *Koha* server?

If so, log in there, and assuming that you are running a package install of
Koha, you can run

sudo koha-list

This will tell you which instances of koha are installed (unless you've
gotten fancy, there will only be one)

Then you can run

sudo koha-mysql instance-name

Where instance-name is the output from koha-list.

The script koha-mysql will read the username, password, database name,
server name and port number from koha-conf.xml, and will connect to the
database if it is up and running. If you can't connect,

1) check the settings in koha-conf.xml
2) have your IT department check that the port is open in the firewall.
3) have them restart mysql.

On Tue, May 29, 2018, 06:17 JanM  wrote:

> Thanks Michael, but i forgot to mention that the mariadb server is hosted
> by
> our computing center and i only have access to the phpmyadmin page, but not
> to the console of this server. This is due to our privacy policies... the
> Koha server is hosted on a local server in the network.
>
>
>
>
>
> --
> 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] Fwd: OPAC Page not available and login credentials don't work

[Mark Alexander]

Excerpts from Bedanta Borah's message of 2018-05-28 10:45:54 -0700:
> 2) In case of  koha livedvd, all features were doing fine untill I updated
> the system and the koha-common packages. After the update, my root user and
> password (koha_library & koha123) stopped working. But I can login with
> another patron which I had created before the update was done. Why I loose
> database user access after updating the software?
> 
> Q) How can I regain the database user access?

I'm not sure if the following will help, but I did notice something
that may be related in the release notes for 18.05 here:

  https://koha-community.org/koha-18-05-released/

Here is what they say about this issue:

  No more login with the database user

  It is no longer possible to use the database user to login into Koha.
  You should first create a superlibrarian patron and use it for logging in.
  [...]
  It is no longer possible to use the database user (defined in koha-conf.xml) 
to login into Koha.
  You should first create a superlibrarian patron and use it for logging in.
  See the script misc/devel/create_superlibrarian.pl

This was discussed in this bug:

  https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20489
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Proxy Error after MariaDB upgrade to 10.2.14

[JanM]

Thanks Michael, but i forgot to mention that the mariadb server is hosted by
our computing center and i only have access to the phpmyadmin page, but not
to the console of this server. This is due to our privacy policies... the
Koha server is hosted on a local server in the network. 





--
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

Re: [Koha] Proxy Error after MariaDB upgrade to 10.2.14

[Michael Kuhn]

Hi Jan

Am 29.05.2018 um 10:21 schrieb JanM:
> Is there a way to test the database connection via Console?

If Mysqld is running you should be able to see something listening on 
default port 3306 at all:


# telnet localhost 3306
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
S
5.5.60-0+deb8u1�-Q6Y?l%p&!�kgCYt]Ur^`F{mysql_native_password

... Disconnect with CTRL+R+] ...

However, you should also be able to connect via SQL command line to get 
the mysql prompt:


$ mysql -uUSER -pPASSWORD DATABASENAME
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 11765
Server version: 5.5.60-0+deb8u1 (Debian)

Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input 
statement.


mysql>

Hope this helps.

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] Proxy Error after MariaDB upgrade to 10.2.14

[JanM]

Is there a way to test the database connection via Console? 



--
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