- Koha - lists.katipo.co.nz

December 2019 koha-US meeting dates
by Jason Robb 02 Dec '19

02 Dec '19

*koha-US meetings are open to any and all.* *Board Meeting -* When: Wednesday, December 4th at 10:30 am CST (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+board+mee…> ) Where: https://kslib.zoom.us/j/450230564 Agenda: https://docs.google.com/document/d/1jTmCYerQ3tyi1z_o6luPup-SBcLK0InRIjfwA9g… *Board meetings* focus on business-related matters and topics that would otherwise slow down general meetings. *General Meeting* - When: Wednesday, December 11th at 10:30 am CST (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+general+m…> ) Where: https://kslib.zoom.us/j/110290143 *General meetings* put an emphasis on Koha -- bugs, issues, development ideas, workflows -- bring your problems and questions so we can discuss! These meetings also include major organizational decisions and reports from various committees. Meetings are held via Zoom video conferencing. A microphone and camera are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops and Android and iOS on mobile devices. For help getting started, visit: *https://support.zoom.us/hc/en-us/categories/200101697 <https://support.zoom.us/hc/en-us/categories/200101697>* If you have topics for discussion at either meeting, please send them to secretary(a)koha-us.org. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Security Releases 19.05.05 and 18.11.11
by Renvoize, Martin 02 Dec '19

02 Dec '19

Hello everyone, I would like to announce the immediate availability of the latest versions of Koha 19.05 and 18.11 respectively. These are combined bugfix and security releases and should be upgraded to at your earliest convenience. Release notes are available on the website at: https://koha-community.org/koha-19-05-05-release/ and https://koha-community.org/koha-18-11-11-release/ <https://koha-community.org/koha-18-11/> Many thanks to the release maintainers, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

Koha Community Newsletter: November 2019
by Koha Newsletter 02 Dec '19

02 Dec '19

The Koha Community Newsletter for November 2019 is here: https://koha-community.org/koha-community-newsletter-november-2019/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Question about values for create_surperlibrian.pl
by Christos Hayward 28 Nov '19

28 Nov '19

For a new installation, does the following make sense? create_superlibrarian.pl --userid ________ --password ________ --branchcode main --categorycode main --cardnumber 1 If some or all of the --branchcode, --categorycode, or --cardnumber values are not what a beginner wants, what should I be supplying? (Or how can I found out what I should be supplying?) -- Christos Hayward

3 10

Question about accessing singleton koha instance
by Christos Hayward 27 Nov '19

27 Nov '19

I have: - Created a single Koha instance called "catalog". - Set catalog-intra to the same machine in /etc/hosts. - Set the generated VirtualHost in /etc/apache2/sites-enabled/catalog.conf to listen on 8080 as well as additionally telling Apache to listen on 8080. On accessing the administrative interface on 8080, I am prompted for a username and password, and been unable to log in as kohauser, with either the randomly password connected to koha.conf, or another manually specified password it is globally replaced with, or running from the command-line koha-password catalog. How can I get to the point of logging in as an administrator to the only instance through the 8080 administrative web interface? -- Christos Hayward

2 2

Export / import fields to MARC records
by Scott Owen 27 Nov '19

27 Nov '19

Hi all, Wondering if any of you have advice on how to perform an export and them import back into the MARC records ? One of my people would like to add Lexicon information to the MARC biblio for each record.... Specifically we would like to: export a list of MARC biblios in csv / Excel format, (maybe by barcode # ???) modify the 526 a-d fields with our Lexicon information in the CSV update / import the csv back into the MARC biblio record(s)... Anyone have a process / step by step on how to do something like this ? Thanks in advance, -S

2 2

Re: [Koha] GDPR - Statistics and anonymization
by Jonathan Druart 26 Nov '19

26 Nov '19

Michal, Redirection the discussion back to the list. What do you mean by "we want to see them as results from borrower searches"? What I understood is that libraries want to collect statistics on transactions even when the patron's records have been deleted. So: 1/ Create a patron (it's copied to borrowers and anonymized_borrowers) 2/ Do some transactions (it's in statistics and anonymized_transactions) 3/ Update a patron (it's updated in borrowers and anonymized_borrowers, if option 1 is picked) 4/ Delete the patron (moved from borrowers to deletedborrowers) 6/ Clean/purge the deletedborrowers => anonymized_* tables are still there, statistics still possible 7/ When needed, given parameters, anonymized_* entries will be deleted. Le ven. 22 nov. 2019 à 15:51, Mike D. <black23(a)gmail.com> a écrit : > > Hello, > I think that thinks are maybe less complicated. I really like Your idea with hash. But if we anonymize (replace by some generated hash or something similar) name, adress, telephone, e-mai and adress, noticess, we don't need related information about borrowers. Because we cut the rope between data and person. Anonymized borrower records we can set as "anonymized" and store them separately from "live" borrowers, because we want to see them as results from borrower searches. What do You think about this? > > Michal > > pá 22. 11. 2019 v 15:41 odesílatel Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> napsal: >> >> 2 tables vs 1 table :) >> >> Le ven. 22 nov. 2019 à 15:28, Mike D. <black23(a)gmail.com> a écrit : >> > >> > Hello Jonathan, >> > what options? I miss a point :-) >> > >> > Michal >> > >> > pá 22. 11. 2019 v 15:17 odesílatel Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> napsal: >> >> >> >> Thanks for the help Michal, >> >> What about the two options I have? >> >> >> >> Le jeu. 21 nov. 2019 à 17:58, Mike D. <black23(a)gmail.com> a écrit : >> >> > >> >> > Hi Jonathan, >> >> > I’m volunteer for debate about processes and anon tools and methods. I’m ready to be tester of bugs. Koha is GDPR ready but some points could be improved for easier everyday usage in libraries. Because if something is clear and easy everybody do it without fear and stress. >> >> > >> >> > Thank You >> >> > >> >> > Michal >> >> > >> >> > čt 21. 11. 2019 v 17:14 odesílatel Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> napsal: >> >> >> >> >> >> Hello everybody, >> >> >> >> >> >> I have been contracted by KohaLa to work on some GDPR requirements. >> >> >> The main idea is to "anonymize" patron's data but letting the library >> >> >> access the transactions' statistics. >> >> >> >> >> >> I am going to present you what I am planning to implement, in order to >> >> >> collect ideas and answers. >> >> >> >> >> >> There are the following steps I have in mind: >> >> >> 1. Pseudonymization [1] of patron's data >> >> >> 2. Improve deletion of patron related date (tables statistics, >> >> >> old_reserves, deletedborrowers) >> >> >> 3. Add the ability to remove data that have been pseudonymized >> >> >> >> >> >> I see 2 ways to achieve point 1: >> >> >> * We create 2 tables, 1 for the patrons, 1 for the transactions. >> >> >> - borrowers_anonymized will contain: hash_id, has_cardnumber, >> >> >> branchcode, creation_date, categorycode, bsort1, bsort2, >> >> >> [borrower_attributes] >> >> >> - transaction_anonymized will contain: hash_id, transaction_type, >> >> >> branchcode, itemnumber, holdingbranch, location, itemcallnumber, >> >> >> itemtype, timestamp >> >> >> >> >> >> hash_id will be generated using the borrowernumber and a key (that >> >> >> will be stored on the server, path in koha-conf) >> >> >> >> >> >> Pros: Easier to understand and manipulate as it follows existing structure. >> >> >> We track patron's modifications (this is the most important part) >> >> >> Cons: tech part: new config, a new path have to be created (minor) >> >> >> >> >> >> * We create only 1 table, (nosql-like). It will contain the same data >> >> >> as previously, without the hash_id >> >> >> >> >> >> Pros: No new config. Data are never updated and we have the values >> >> >> when the transactions has been processed. >> >> >> Cons: Data are not updated :) >> >> >> >> >> >> About borrower_attributes, the initial specification asks for 2 >> >> >> attributes defined in a syspref. I think it should be configurable, >> >> >> with a join table (Pro: more flexible, Con: SQL requests more complex) >> >> >> >> >> >> I think we should have the 2 tables and keep a link between the >> >> >> anonymized_patrons and anonymized_transactions tables. >> >> >> >> >> >> What do you think? >> >> >> I am going to start the implementation very soon in order to plan an >> >> >> integration early in the 20.05 dev cycle. >> >> >> >> >> >> Regards, >> >> >> Jonathan >> >> >> >> >> >> [1] https://en.wikipedia.org/wiki/Pseudonymization >> >> >> _______________________________________________ >> >> >> Koha mailing list http://koha-community.org >> >> >> Koha(a)lists.katipo.co.nz >> >> >> https://lists.katipo.co.nz/mailman/listinfo/koha

3 6

error occurred while importing the database structure
by Davide Spanu 26 Nov '19

26 Nov '19

Good evening to all. I have tried several times to install Koha on a new server and I continue to receive database error(s). I follow the procedure step by step but I just can't understand where I'm wrong. The error I get with the webinstaller is this (then, consequently, many others). The following error occurred while importing the database structure: [Thu Nov 21 18:26:44 2019] install.pl: DBD::mysql::st execute failed: BLOB, TEXT, GEOMETRY or JSON column 'changed_fields' can't have a default value at /usr/share/perl5/DBIx/RunSQL.pm line 273. Please contact your system administrator Something is wrong with Mysql, but I don't understand what. I thank all of you in advance. Davide

4 3

Multilingual Searching and ICU Chains
by Charles Kelley 26 Nov '19

26 Nov '19

Hello, all! I am developing a catalog of multilingual, multiscript materials: Arabic, Bengali, Burmese, Chinese, English, French, German, Japanese, Korean, Mongolian, Russian, Vietnamese, to name but a few. Since both Koha and MarcEdit are UTF8, I can enter the cataloging records and edit them in their appropriate script. What I cannot do is to search them. I have seen on the Koha Community wiki is that ICU chains have to be configured. Here's the link: https://wiki.koha-community.org/wiki/ICU_Chains_Library. I also found an exchange about this: https://lists.katipo.co.nz/public/koha/2012-January/031714.html. Is one to infer that the ICU chain has to be configured for each writing system? Are there other multilingual libraries that have implemented multilingual, multiscript searching in Koha and how did they do so? Many thanks for your help in this matter. -- -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley 1-5-2 Tsukimino #210 Yamato-shi, Kanagawa-ken, 〒242-0002 JAPAN 1-301-741-7122 [US cell] 011-81-80-4714-5490 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

4 7

Fully enabling the installation
by Christos Hayward 25 Nov '19

25 Nov '19

Hello! I am an author with website at cjshayward.com and trying to ship off a laptop to a dear monastery with a working Koha 19.05 installation under Linux Mint 19.2. A particular peculiarity is that is as a workaround to a non-functioning 'B' key, I have set a hostname and instance name of "holy-reading" instead of the usual "library". I have installed, from the 19.05 release wiki, up to the point where it says to log in via Lynx. That gets an Ubuntu "It worked!" page; when I use a standard browser to pull up holy-reading.holycross.org, it redirects to holy-reading.holycross.org/cgi-bin/koha/maintenance.pl: *System Maintenance* The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator One way I may have misconfirgured it is by failing to specify decent hostnames between administrative and enduser use. If that is believably the problem, how should I edit things so that the enduser and administrative interfaces are on separate hostnames? Thanks, -- Christos Hayward

1 0