- Koha-devel - lists.koha-community.org

Koha users wiki page outdated, use HEA
by Paul Poulain 24 Aug '18

24 Aug '18

Hello, someone pointed me the https://wiki.koha-community.org/wiki/KohaUsers page. The French libraries you can see here are so outdated that it's funny: most libraries are supposed to be in version 2.x, supported by me (not BibLibre. So more than 10 years old data...) Other pages are also highly outdated, almost nothing with the current version numbering schema. And now we have HEA (available since 3.18 IIRC) I propose to: * drop an email to all contacts saying "you're the contact for the wiki page https://wiki.koha-community.org/wiki/KohaUsers, the information here is outdated, please activate HEA (<<some explanations about hea>>)" * update the wiki pages to add a big warn on top of each, saying "this page is outdated, see hea.koha-community.org") Any objection ? -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

6 12

KohaCon18 social stuff
by Paul Poulain 23 Aug '18

23 Aug '18

Hello, Just for those who are not following wiki closely : https://wiki.koha-community.org/wiki/Kohacon18/Social => you can register here your arrival & departure infos => you can see some ideas trip trip/beer/fun/... -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

4 3

Requesting feedback on changing the default behavior for loading the OPAC cart popup
by Alex Buckley 22 Aug '18

22 Aug '18

Hi all I am writing in regards to bug 21174 (Sysprefs to enable the opening of OPAC cart in one click - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21174) In my commit on this bug report I implement a syspref which when enabled allows OPAC users to click on the cart icon once and the cart pop-up is loaded. Katrin, Owen and myself would like to know: does anyone really love the way the cart popup currently loads? That is you click on the cart icon a dropdown box appears saying 'Items in your cart: ...' and you have to click on that dropdown option to load the cart popup. We would like to know the opinion on the community for making clicking on the cart icon once and loading the cart popup the default behavior. i.e. make this updated interaction the default. The dropdown box saying 'Items in your cart: ...' probably isn't necessary because in the commits on the aforementioned bug report show the number of items in the cart to the right of the cart icon - so the user knows how many items are in their cart. Please let us know your thoughts on the bug report 21174. Many thanks, Alex

3 2

test mail
by Paul Poulain 21 Aug '18

21 Aug '18

Hello, We (BibLibre) are doing some changes on our mail system, this is a mail for testing. No need to reply, thx -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Call for News: August 2018 Newsletter
by kohanews 14 Aug '18

14 Aug '18

I'm collecting news for the August newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Storing non-MARC data in biblio_metadata
by David Cook 13 Aug '18

13 Aug '18

Hi all, How do people feel about storing non-MARC metadata in the biblio_metadata table? Typically, the "format" column contains the string "marcxml" and the "metadata" column contains the MARCXML text, but it seems like someone could put in "RDF/XML" and RDFXML text instead? The one barrier to that is the "marcflavour" column which is a "NOT NULL" column. I mean. that could be an empty string. but I wonder if there's a way of de-MARCing that column? I'm trying to think of analogs for other scenarios. I mean in the case of RDF. you might have RDF/XML or JSON-LD. which are separate formats but they're both "RDF". I wonder if "marcflavour" could be better known as "schema", or "model", or "standard", or something else? I know choosing wording is hard. For instance, MARC::File::XML (https://metacpan.org/pod/MARC::File::XML) refers to UNIMARC and MARC21 as formats. Dublin Core and MODS are often referred to as schemas. MARC21 is often called a standard. According to http://www.loc.gov/marc/unimarctomarc21.html, UNIMARC and MARC21 are formats. RDF gets called a data model with different data serialization formats. I know it would probably be a lot of work to change "marcflavour" to something else, especially since we've all been familiar with "marcflavour" for many years now, but I'm thinking maybe it's time we change that name. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

Asking for an easy sign off
by David Cook 10 Aug '18

10 Aug '18

Hi all, If anyone is looking for an easy sign off, please consider "Bug 21005 - Missing row/column defaults cause unexpected results in report wizards" (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21005) It's something that I've been meaning to fix for a long time, but finally sat down and wrote the patch. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Centralize and move to gitlab
by Jonathan Druart 08 Aug '18

08 Aug '18

Hi devs, (Spoiler: I am not talking about a move from bugzilla to gitlab for the Koha git repo) Just a quick comment: gitlab has the ability to move projects with all the issues. >From the export page of a project, they say: """ The following items will be exported: Project and wiki repositories Project uploads Project configuration including web hooks and services Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities """ So that will be easy to move (already discussed with Chris, will do in May) * koha-community-devs-users/kohadocs to koha-community/kohadocs * https://gitlab.com/koha-dashboard/koha-dashboard to koha-community/koha-dashboard And the ones from github too: * joubu/koha-misc4dev to koha-community/koha-misc4dev * Koha-Community/qa-test-tools to koha-community/qa-test-tools Then, maybe: koha-testing-docker koha-release-notes kohadevbox koha-howto The idea is to centralize our things in one place, ease the PRs and the ability to clone/fork keeping the visibility on what is the reference (account 'koha-community'). I would also like to generate a CI configuration for some of them. CI file for Koha: https://tree.taiga.io/project/joubu-koha-rm-1711/us/146 (I am going to submit that on bugzilla soon) CI file for the manual: https://gitlab.com/koha-community-devs-users/kohadocs/blob/master/.gitlab-c… Any pros/cons? Cheers, Jonathan (No troll please)

11 16

Koha Community Newsletter: July 2018
by Koha Newsletter 02 Aug '18

02 Aug '18

The Koha Community Newsletter for July 2018 is here: https://koha-community.org/koha-community-newsletter-july-2018/ 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. PS: please excuse the delay -- we had a baby the 20th of this month! Healthy baby girl. Thanks!

1 0

Batch cleanup to the catalog
by Cab Vinton 01 Aug '18

01 Aug '18

Hi, All -- Koha's Batch Record Modification (BRM) tool makes it very easy to make large-scale changes to the catalog. And we know that many catalogers like to have their records just so :-) Is there a cost in overhead, however, to making such changes? For example, if a catalog of 150,000 records contains 75,000 unwanted MARC fields, would you delete them, even if they're not displayed in the OPAC or otherwise interfering w/ functionality? In particular, I'm wondering whether using the BRM tool involves the creation of new data so that there's no real net gain w/ respect to the goal of having a "cleaner" database. (In our case, we've turned off the CataloguingLog system preference.) Along the same lines, are there any advantages to doing large-scale batch process via the backend instead, i.e., as opposed to w/ the built-in staff tools such as BRM? (I'm assuming there's no issue w/ using such tools to work w/ much smaller subsets of records.) Thanks in advance for any guidance. All best, Cab Vinton, Director Plaistow Public Library Plaistow, NH

2 2