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

Dates and Zebra
by David Cook 06 Oct '15

06 Oct '15

Hey all: I was just adding an alternate patch for http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14861, and I started thinking a bit about date indexes in Zebra. and how we're not using them as effectively as we could. For MARC21, we only actually have one date index and that's for "Date-of-acquisition", even though we store lots of other ISO-formatted dates such as "datelastseen", "replacementpricedate", "datelastborrowed". Technically "Date/time-last-modified" is in ISO format, although we'd have to test how Zebra handles the time element of the string. and we might want to transform it into the extended ISO format (e.g. YYYY-MM-DD hh:mm:ss) which is used elsewhere. "date-entered-on-file" could also be transformed although it has the Y2K issue. That said, I don't think these fields are particularly popular. I noticed that UNIMARC indexes "items.onloan" which MARC21 refers to as 952$q. That might be an interesting one. UNIMARC indexes that as a "date index". Provided that the indexes are up-to-date, you could quickly search for all records with items due on a particular date. and after bug 14861 is pushed. you could also search for date ranges. Anyway, just a thought. I'm not sure how many people are familiar with ccl.properties, biblio-zebra-indexdefs.xsl, bib1.att, default.idx, and the rest of the Zebra configuration files, but I've included an explanation at the end of this file regarding the MARC21 Zebra configuration. -- Bib1.att defines mappings between numbers and index names. The index names are used both during indexing (and optionally during searching/retrieval). The numbers are used just for searching/retrieval. For example: att 4 Title ccl.properties creates mappings between user-defined "CCL qualifiers" and the Bib1.att "use" attribute numbers. It also can create additional aliases for "CCL qualifiers". For example: Title 1=4 ti Title In this case, "Title" is the "CCL qualifier" and "ti" is an alias for "Title". 1 stands for "Use attribute" and 4 stands for "att 4" from Bib1.att. biblio-zebra-indexdefs.xsl parses MARCXML records and transforms them into a format that Zebra uses for indexing. It uses the "index names" from the Bib1.att file for this purpose. Here's a snippet from that file for MARC21: <xslo:template mode="index_subfields" match="marc:datafield[@tag='245']"> <xslo:for-each select="marc:subfield"> <xslo:if test="contains('a', @code)"> <z:index name="Title-cover:w Title-cover:p Title-cover:s Title:w Title:p Title:s"> <xslo:value-of select="."/> </z:index> </xslo:if> </xslo:for-each> As we can see, field '245' subfield 'a' gets stored in the "Title-cover" and "Title" indexes. But they also have those ":w", ":p", and ":s" bits added. Those refer to "register types". "w" is the word register, "p" is the phrase register, and "s" is the sort register. There are others which you can find in "default.idx". There others include "n" for numeric, "d" for date, and "y" for year. These "registers" are mapped to Bib-1 "Structure" attributes. These mappings can be found at http://www.indexdata.com/zebra/doc/querymodel-zebra.html#querymodel-pqf-apt- mapping. So if you want to search the "date" register for a particular index, you'll need to form a CCL query that uses "st-date-normalized" since it's mapped to "4=5" (ie structure attribute number 5), since this is the structure that is mapped to the "date" register in Zebra. Typically, the default structure in Zebra is "phrase", although Koha uses some query building "magic" to often use the "word-list" structure, which is mapped to both the "word" and "phrase" registers. Thus, "acqdate, st-date-normalized = 2015-09-01" will search the "Date-of-acquisition" index (since "acqdate" is just an alias for the "Date-of-acquisition CCL qualifier which is mapped to the "Date-of-acquisition" index, and st-date-normalized is mapped to the "date" register). The patch for 14861 will also make it so that you can search ISO date ranges such as: "acqdate, st-date-normalized = 2015-09-01 - 2015-09-30" or "acqdate, st-date-normalized = 2014 - 2015" or even "acqdate, st-date-normalized = 2014-01 - 2014-03" . Note that the whitespace between the digital and the hyphen are significant. For more fun with Zebra, consider reading some of the content at http://wiki.koha-community.org/wiki/Troubleshooting_Zebra. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

1 0

Bootstrap 2.2.2 in the staff client
by David Cook 05 Oct '15

05 Oct '15

I was just looking to use ".text-success" in the staff client, when I noticed that it didn't appear to exist in bootstrap.min.css. even though it should. You can find it here in Bootstrap 2.2.2: https://maxcdn.bootstrapcdn.com/bootstrap/2.2.2/css/bootstrap.min.css But not in the version that we have in the staff client: http://koha:8080/intranet-tmpl/lib/bootstrap/bootstrap.min.css I'm guessing that during the integration of Bootstrap into the staff client that some things just didn't work, so the file was pared back? Perhaps Owen can speak to that one? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

4 9

found = Null in CancelReserve
by BOUIS Sonia 04 Oct '15

04 Oct '15

Hi, We are working on hold stuff at the moment and we have a lot of questions ! We want to provide statistics on canceled holds to know if they haven't been picked-up as waiting for the borrower or if the expiration_date on hold have been passed. But if we can see if a hold is waiting in found column of reserves table, this information disappeared from old_reserves table. In C4/Reserves.pm, there's this SQL request in CancelReserve : UPDATE reserves SET cancellationdate = now(), found = Null, priority = 0 WHERE reserve_id = ? I'm not a specialist, but I wonder why found is set to Null when cancelling and why we can't keep this information in old_reserves ? Thanks in advance for any explanation. Cheers, Sonia BOUIS Responsable du Système intégré de gestion des bibliothèques bIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 - 69355 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

2 1

Cataloguer's info in MARC field
by akafortes 02 Oct '15

02 Oct '15

Hello, is it possible to get the username of the logged in user and use it in a MARC field? I would like to add a field where I keep info about who catalogued a record. -- View this message in context: http://koha.1045719.n5.nabble.com/Cataloguer-s-info-in-MARC-field-tp5854171… Sent from the Koha-devel mailing list archive at Nabble.com.

7 12

Add rule for no subroutines in PL scripts
by David Cook 02 Oct '15

02 Oct '15

Hi again: I also noticed there's no rule forbidding subroutine definitions in PL scripts. I thought that we had a rule against that as well. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: David Cook [mailto:dcook@prosentient.com.au] Sent: Tuesday, 29 September 2015 12:27 PM To: 'koha-devel(a)lists.koha-community.org' <koha-devel(a)lists.koha-community.org> Subject: Add rule for experimental features in coding guidelines Hi all: I just noticed that we don't actually have a rule against using experimental features (e.g. smartmatch ~~, given/when) in the coding guidelines. We impose this rule during the testing/QA process, but it's not actually documented. What do we need to do to add a rule? Bring this up at a meeting? http://wiki.koha-community.org/wiki/Coding_Guidelines David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

9 20

Add rule for experimental features in coding guidelines
by David Cook 01 Oct '15

01 Oct '15

Hi all: I just noticed that we don't actually have a rule against using experimental features (e.g. smartmatch ~~, given/when) in the coding guidelines. We impose this rule during the testing/QA process, but it's not actually documented. What do we need to do to add a rule? Bring this up at a meeting? http://wiki.koha-community.org/wiki/Coding_Guidelines David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

3 3

Issue tracker for koha-qa.pl tool
by Mason James 30 Sep '15

30 Sep '15

Hi Folks Jonathan and I are planning to use an bug/issue tracker for the koha-qa.pl tool We thought it would be a good idea to get some opinions from other Koha developers, on which tracker to use here is the list we currently have... 1/ use github.com 2/ use gitlab.com 3/ use a KC.org gitlab server (can someone provide a 2gig server?) 4/ use current KC.org bugzilla 6/ something else...? any opinions? Mason

8 8

Koha Community Newsletter: September 2015
by kohanews 30 Sep '15

30 Sep '15

Fellow Koha users: The Koha Community Newsletter for September 2015 is here: http://koha-community.org/koha-community-newsletter-september-2015/ 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. Thanks! Chad Roseburg Editor, Koha Community Newsletter

2 2

Kohadevbox for testing Packages+Plack
by Tomas Cohen Arazi 27 Sep '15

27 Sep '15

Hi everyone, I hope you had a great weekend :-D We have pushed a new branch to the kohadevbox repository. The branch is called 'ansible' and relies on that tool (Ansible) to load a full packages environment, suitable for testing Plack on packages. I already use it for my RM duties, daily. To try/use it, you need to: (1) Install the latest vagrant: https://www.vagrantup.com/downloads.html (2) Install the latest ansible: http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via… (3) Install nfs-kernel-server (for re-using your host machine cloned repo) $ sudo apt-get install nfs-kernel-server (4) Clone the kohadevbox repo https://github.com/digibib/kohadevbox.git (5) Checkout the 'ansible' branch. (6) Dive into the directory, uncomment the lines you would like to tweak in vars/user.yml (email, name, bz configuration, etc) (7) Set an env variable pointing to your local koha clone (for example) $ export SYNC_REPO=/home/katrina/kohaclone (8) Launch kohadevbox for the desired distribution: $ vagrant up trusty or $ vagrant up wheezy or $ vagrant up jessie Once you have your vagrant environment up and running, you will have access to Koha like this: - OPAC: http://localhost:8080 - Staff: http://localhost:8081 After this, you can enable Plack from within the VM by running: $ vagrant ssh <os> # to get into $ sudo -s # gain root access $ koha-plack --enable kohadev $ koha-plack --start kohadev $ service apache2 restart Once you have it running and figure how easy is to destroy your environment and re-create it, you will really love this (+10000 to Magnus!). So, this is a pledge to all of you, to use it so we properly test Plack on packages for the next release. Thanks in advance! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

4 9

Change orientation of label printing
by akafortes 24 Sep '15

24 Sep '15

Hello everyone, I'd like to ask if there is a way to change the orientation of the text when you print labels. I want the spine labels to be printed with vertical text -- View this message in context: http://koha.1045719.n5.nabble.com/Change-orientation-of-label-printing-tp58… Sent from the Koha-devel mailing list archive at Nabble.com.

3 4