- Koha - lists.katipo.co.nz

Re: [Koha] Source of Acquisition
by Charles Kelley 06 Dec '19

06 Dec '19

Hello Alvaro et al! In our latest exchange, on 5 Dec 2019 08:28, you wrote: You might concatenate the acquisition number and the Access Db id on 952$i > with a character separator like a pipe, asterisk, semicolon, etc. ie > 2019-01325|54342. > Yes, that's an excellent suggestion. My supervisor and I are arranging a meeting with the other principals to look at a number of issues and settle them before the catalog goes live. Once you get rid of the old Access DB system you can run a query to the > Koha DB biblio table and, using the separator, remove all reference to the > old AccessDB. How does one do that in Koha, through the Tool -> Batch Item Modification? I know how to run a query, but it's the changing of a group of records by removing a portion of one field or subfield that I don't understand. This is all new to me, and I'd be grateful for whatever help your can offer. -- -- 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.

2 1

Source of Acquisition
by Charles Kelley 06 Dec '19

06 Dec '19

Hello, all! I have been asked to add a new indexed item field (subfield, that is). Here's the story. My library keeps track of its acquisitions in an old Access database. Each acquisition is given a unique ID number consisting of two parts: the year of acquisition and its sequence in the acquisition scheme for the year. <acquisition year>-<sequence number> For example the acquisition number of *A dictionary of Japanese and English idiomatic equivalents*, ISBN 0870111116, c. 1, is 1986-1003. The acquisition number of the same title, c. 2, ordered in the same batch as c. 1, is 1986-1003. This means, as you might already induce, that in 1986, c. 1 and c. 2 were the 1003rd books ordered. A third copy ordered later in the year would get the acquisition number 1986-1657. If a fourth copy is ordered in two years, it might get acquisition number 1988-0384; meaning it was the 384th work ordered in 1988. I am building a Koha catalog this library's from a spreadsheet and Access database, I have been asked to preserve this acquisition number. It is very important to the staff, and I am too new to challenge the staff about it. I am confident that in a few years, we'll have a better different system in operation; but for the present, I think I ought to keep it. Well, I can insert the number into the 952$e field. I could repurposed the 952$k field since that field is not in use. If I do the former (952$e), I can rely on the regular Koha indexing handle the number, the indexing, and so on. If I do the latter (952$k), I have to create and build a new index;* and I run the risk that Koha will dedicate 952$k to a function in the future. Have libraries in this discussion list done 952$e? Have libraries in this discussion list done $952$k? Is there an alternative solution? Abandoning the porting is not, at this stage, an option although I concede that in the future, we will likely end up dropping this version of the acquisition number. * I have read the sections on building an index on the Koha wiki. Thanks for your help, everyone. -- -- 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.

3 2

Fwd: Koha-US Koha-a-thon Call for Proposals
by David Nind 05 Dec '19

05 Dec '19

For some reason this didn't make it to the list... Koha-US is planning an online conference we are calling Koha-a-thon. Koha-a-thon will be an online-conference on April 23, 2020, beginning at the start of the day on the US east coast (13:00 UTC) to the end of the day on the US west coast (4:00 UTC, April 24) (Find out what time that is for you here <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha-US+Koha-a-th…>.) Koha-a-thon will be free and open to anyone who wishes to attend and participate. Its entirety will be streamed live on YouTube and the content will be recorded so that anyone who wishes can view the presentations at a later date. At this time we are asking for presentation proposals. If there's anything you'd like to talk about, please fill out the form at https://forms.gle/jRUQwJ4Tn4Qq862p8 Presentations can be as short as 10 minutes or as long as 60 on any topic related to Koha, or any other open source topics related to Koha, the Koha community, libraries, or anything else you think of as "Open." And if you'd like to submit more than one proposal, please do so. We will be accepting proposals through January 10, 2020. If you have any questions, please let us know at conferences(a)koha-us.org or info(a)koha-us.org Thanks, Lisette Scheer 2019 vice president - koha-US

1 0

EDI and managing suggestions
by BOUIS Sonia 05 Dec '19

05 Dec '19

Hello, We are not using EDI yet in my University but we have an exchange of data with our supplier that is not far from an EDI system to manage the orders. My colleagues are ordering directly on the website of our supplier and are receiving the biblio records through a ISO2709 file. They have just to create a basket and upload this file to create their order in koha. After that, we send the koha EAN-ordernumber text file to our supplier. It's so easy for them that they are complaining about the suggestions management in Koha. If they want to keep the link between the suggestion, the acquisition, the biblio record and the item, they have to manage all the suggestion twice. One time in Koha and one time on our supplier website. But it's the only way to notify the patron when his suggestion is ordered and received. I am wondering if people that use the EDI process in koha have found a way to link suggestions to acquisitions. I've seen that a Bugzilla tickect have been opened that could apparently solve our problem : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19358 Is anyone working on this ? Thank you for your feedbacks. Cheers Sonia BOUIS Responsable du Service des applications documentaires BIBLIOTHÈQUES UNIVERSITAIRES Bibliothèque de la Manufacture UNIVERSITÉ JEAN MOULIN LYON 3 1C AVENUE DES FRÈRES LUMIÈRE CS 78242 69372 LYON CEDEX 08 ligne directe : +33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

1 0

Re: [Koha] Source of Acquisition
by Charles Kelley 05 Dec '19

05 Dec '19

Hello, Karin et al! In our latest exchange, on 4 Dec 2019, at 08:14, you wrote: In German libraries an acquisition number like this is very common. > There is a specific Koha item subfield for it already: 952$i = stocknumber > or inventory number. It is indexed in Zebra and there are some value > builders (like stocknumberAV.pl) to generate different sequential number > patterns that can be used with it or could be adapted to generate what you > currently have. Thank you for the suggestion. I thought of 952$i. But I'm also asked to keep the Access DB record number and I put it in 952$i. However, consultation of the Access DB is likely to end sooner than later, and certainly long before the acquisition number is abandoned. I hear the staff refer to the acquisition number often enough and it is rare I hear about the Access DB. Since we are only in the development stage, it would easy to rededicate the 952$i to the library acquisition number and copy the Access DB record number into 952$x along with other staff notes. I'd like to do this now before the transfer instead of after the transfer. In any event, in the coming weeks, the rest of the library staff and I will be holding a meeting to discuss this and other library matters: layout, operations, procedures, organization, etc. Thank you again for the suggestion. I must ask one question: does anyone know whether or not 952$i has to be unique? -- -- 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.

2 1

Looking for example reports - overdue fines paid, lost items returned
by Joelle Hannert 04 Dec '19

04 Dec '19

I'm trying to use the reports library to find a report that will list all fines that were in excess of $10 that were paid/forgiven yesterday. I'm looking to get a list of patrons who were over our fine threshold who have paid up. I'm having trouble getting any of the similar reports in the Koha reports library to work even to show me fines of any amount paid yesterday. I'm also looking for a report that would list items that had been marked as lost that have been returned yesterday. If anyone has reports like this - even remotely similar - that you'd be willing to share I'd be most appreciative! Thanks, Joelle -- Joelle Hannert Library Technical Services Coordinator Northwestern Michigan College (231) 995-1684 Work days: M, W, Th, F

1 0

Software error after install
by Paweł Niedźwiadek 04 Dec '19

04 Dec '19

Hi everybody, after install newest version of Koha, when I try to log into staff interface, I get Software error: DBIx::Class::Storage::DBI::_dbh_execute(): Table 'koha_wwsi.discharges' doesn't exist at /usr/share/koha/lib/Koha/Patron/Discharge.pm line 31. After reading that http://koha.1045719.n5.nabble.com/Software-error-td5980011.html I did koha-upgrade-schema and zebra rebuild. Unfortunately, it does not work. In version 18.05 everyfhing was OK. Could anyone help? Paweł Niedźwiadek tel. 502 180 409 pawel(a)ictprojekt.pl<mailto:pawel@ictprojekt.pl>

2 1

GDPR - Statistics and anonymization
by Jonathan Druart 03 Dec '19

03 Dec '19

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

3 5

Koha 19.11.00 Released
by Renvoize, Martin 03 Dec '19

03 Dec '19

Hello everyone, It is my great pleasure to be able to announce the release and immediate availability of Koha 19.11, a major release of the Koha open source integrated library system. The release includes 7 security fixes, 20 new features, 146 enhancements and 367 bugfixes. Please see the release notes for further details: https://koha-community.org/koha-19-11-release/ It is the work of many librarians, developers and community members who have donated a huge number of hours to keep the project moving forward. My thanks go out to all who contributed. This is my first release as a release manager and I'd like to extend my personal thanks to those who preceded me and helped guide me. I am hugely grateful to have had the support of such a team. Special thanks go out to Mason James, for stepping in at the last minute and taking on the packaging of the release for the community repositories. As noted above, this release includes 7 security fixes, which have all also been included in the stable and old-stable branches and so it would be wise to upgrade as soon as possible to your respective versions. Debian packages, for both this version and the prior versions, are available now. If you are following a suite you will automatically upgrade to the next branch with this release, more info here: https://wiki.koha-community.org/wiki/Koha_on_Debian#Follow_a_suite:_stable.… Many thanks to you all, *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

3 2

Creating additional superlibrarian
by Christos Hayward 02 Dec '19

02 Dec '19

How, with create_superlibrarian.pl or other tools, can I create a superlibrarian that will be recognized by the webinstaller? Are --branchcode and --category code pulled from tables in MariaDB? Is a cardnumber of 1 permissible, or pulled from MariaDB, or something else? Many Thanks, -- Christos Hayward

3 4