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

About "Problems on Due date when checking in"
by Bernardo Gonzalez Kriegel 15 Jun '12

15 Jun '12

Hi, we noted a strange behavior: if check out an item and immediately check in the item then the user is debarred. Following the code found that user is debarred if ($deltadays -$grace)->is_positive is true (_FixFineDaysOnReturn, C4/Circulation.pm) I think that $deltadays = $calendar->days_between( $dt_due, $dt_today ) needs to be negative if $dt_due > $dt_today, but is computed on Koha/Calendar.pm as my $duration = $dateend_temp->delta_days($datestart_temp); (there is a while that changes $duration but DateTime->compare( $datestart_temp, $dateend_temp ) = 1 in this case) Now, the method delta_days() *always returns a positive duration*, even if $dt_due > $dt_today If we compute $duration as my $duration = $dateend_temp->subtract_datetime($datestart_temp); and add a line on C4/Circulation.pm my $deltadays = $calendar->days_between( $dt_due, $dt_today ); +return if ( $deltadays->is_negative ); we solved our problem. Do you think that this is a real bug or we missed some configuration? (the code examples are from master but the problem is on 3.8.0, where we found it. BUG 8045 changes some of the code, but not the use of delta_days() method) Sincerely Bernardo -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com

3 2

String freeze for 3.6.6
by Jared Camins-Esakov 15 Jun '12

15 Jun '12

Good morning. On June 15 we will go into string freeze for 3.6.6, which will be released on June 23. There have not been many changes, so the translation should be pretty painless. Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 1

String freeze for 3.8.2
by Chris Cormack 15 Jun '12

15 Jun '12

We are almost one week out from the release of 3.8.2, which means that on the 15th we go into string freeze before the release. There shouldn't be a huge amount of changes from 3.8.1, but we will soon find out once the translation manager has updated the .po files. Happy translating Chris

3 2

bugzilla default assignee changes
by Paul Poulain 14 Jun '12

14 Jun '12

Hello, During the hackfest, we reviewed the default assignee for all components. Some ppl that were default were at the meeting, some weren't What appears the best option to us: if you're a default assignee for a given component, it mean you accept to take care of any new bug opened on this component (even if taking care means saying you won't fix the bug). It means we think the best option is to have the koha-bugs mailing list as default assignee, as it's "anonymous". We already made the following changes on components: - removed henridamien & paul default assignee on many (10 ?) components, set to koha-bugs@ mailing list - translation component: removed chris_c as default assignee set koha-bugs@ mailing list & added Frederic Demians as cc: as he requested on this list last month - Circulation and patron: moved Kyle to cc (keeping galen as cc too), default assignee is now koha-bugs@ ML - I18N : moved Frederic to cc:, koha-bugs@ ML is default assignee - contribs, bugs, imported_bugs : removed chris_c and koha-bugs@ ML is default assignee GALEN & IAN = You're default assignee for many/some components. Do you confirm you want to take care of those bugs or should we put koha-bugs mailing list as default ? (Galen, I think you're default because you've been RM for 3.2, and no-one changes since this time) OWEN & NICOLE & LIZ & CHRIS_N We haven't changed the components you're default, because you said last month it was OK for you. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

5 5

Koha API for use in mobile app
by Robert Nay 14 Jun '12

14 Jun '12

I am looking to create an iPhone/Android app for my local library, and am wondering about the best way to go about this. Does Koha have some API that can be accessed from a third-party client (in this case, a mobile application)? Koha pages seem to have an "unapi" link in them, is this something that could be used? I am relatively new to Koha, so any help or advice would be greatly appreciated. Thanks! Robert

2 1

Kohacon12: my pics
by Matthias Meusburger 14 Jun '12

14 Jun '12

Hello ! Here are the photos I've taken (and gathered) from Kohacon12: http://pub.veggie.fr/biblibre/pics And here is a zip file: http://pub.veggie.fr/biblibre/2012_06_05-11_Kohacon_Edinburgh.zip Cheers, Matthias Meusburger

2 1

Unit tests and continuous integration with Koha
by Claire Hernandez 13 Jun '12

13 Jun '12

Hello all, One of discussed subject at kohacon12 was quality control and automated tools: Chris presented us how works unit testing in koha and what does jenkins. I tried to summurise both subjects in these two pages: http://wiki.koha-community.org/wiki/Unit_Tests http://wiki.koha-community.org/wiki/Continuous_Integration Surely incomplete and with mistakes but have a look :) Claire;

1 0

Experimental support for MARC records as a proper datatype in the PostgreSQL database
by Marc Balmer 12 Jun '12

12 Jun '12

Sitting in one of the nice pubs in Edinburgh during KohaCon, I had this idea to add MARC records as a proper datatype to the PostgreSQL database server. After a discussion with Marc Véron and Dobrica Pavlinusic about what that could mean, I decided to just try it and I have now a basic implementation (or, more a proof of concept). So here is some information on this: If MARC records are a proper datatype, that means they are stored right in the database, are backed-up, can be restored, replicated etc. just with the standard database tools. If then a function is provided to access individual fields of a MARC record, then this can be used in SQL expressions, e.g. for selects or to create views etc. As PostgreSQL supports functional indexes, you can create indexes on individual MARC fields, giving you super fast access to your data. How does it look? There is a datatype called 'marc' for now: CREATE TABLE books ( id serial, sig varchar(16), marc_record marc ); MARC records are loaded into the database as raw, binary records, encoded in hexadecimal: INSERT INTO books (sig, marc_record) VALUES ('a01b', '3030383830.....'); To access individual MARC fields, the function 'marc_field()' was created, it returns VARCHAR: SELECT id, marc_field(marc_record, '020') AS isbn FROM books WHERE sig = 'a01b'; Of course MARC fields can be used to search data: SELECT SELECT id, marc_field(marc_record, '020') AS isbn FROM books WHERE marc_field(marc_record, '245') like 'whatever%'; An index on a specific field can easily be created: CREATE INDEX books_isbn_idx ON books (marc_field(marc_record, '020')); As a syntactic sugar, the expression marc_record@'020' is equal to marc_field(marc_record, '020'). Marijana Glavica kindly let me use a MARC database of ~250'000 records to make some tests, here are some real world examples: books=# \d test_marc Table "public.test_marc" Column | Type | Modifiers --------+---------+-------------------------------------------------------- id | integer | not null default nextval('test_marc_id_seq'::regclass) marc21 | marc | books=# select count(id) from test_marc; count -------- 246727 (1 row) How many croatian books do they have? books=# select count(id) from test_marc where substring(marc_field(marc21, '008'), 37, 3) = 'hrv'; count ------- 52582 (1 row) Of course much more complex queries are possible with this, and using the right indexes it is really, really fast. One query I tested when from 8.4 seconds to 0.21 ms with the right index. That's a speedup of 40'000. Thanks to Marijana, Dobrica, and Marc for feedback, interesting discussions and ideas! Feedback and suggestions are of course more than welcome. - Marc

2 3

Error message when deleting items
by David Schuster 11 Jun '12

11 Jun '12

I was using the batch delete in 3.6.5 - by barcode and received this error: Hints as to why? -- David Schuster Plano ISD Library Technology Coordinator

2 2

Authority control - request for comments
by Jared Camins-Esakov 11 Jun '12

11 Jun '12

Good time of day! I plan to do a great deal of work on the authority module, and I wanted to request that anyone with thoughts on the matter please share them with me. The RFC is on the wiki at http://wiki.koha-community.org/wiki/C_%26_P_Authority_Control_Improvements_… I have copied the description below. Description The development is divided into 14 parts: 1. A dropdown box will be added to the authority browser in the OPAC allowing the user to choose which index to search in authorities: the keyword index, the match heading index (i.e. all heading fields), the preferred heading index, or the main entry only index. (bug 8206) 2. Because importing large authority files can result in unused authority records overwhelming used authority records in OPAC authority browse results, some libraries may want to disable the display of authorities which are not used in the bibliographic database. In order to make this possible (while still retaining the existing behavior of displaying all records in the authority file as a default), a system preference OPACShowUnusedAuthorities will be created, and a "Show all results" link added to search results when it is enabled. (bug 8205) 3. Because see also references in authority records are intended to refer to other authority records, they really ought to be turned into hyperlinks in the various authority displays. They will be made into hyperlinks (using the authid in $9 if available, or a search string otherwise) in both the OPAC and the staff client. (bug 3462) 4. At present, the only authority record view available in the OPAC is an "expanded MARC" view which is of no use to patrons, and limited use to librarians. We propose adding a user-friendly authority details view similar in design to the bib details view. (bug 8204) 5. Although the batch import functionality was originally designed with importing both bibliographic and authority records in mind, authority import was never actually implemented. This will be done quite simply, by adding an option to choose which type of record to import in the Stage MARC records tool. (bug 2060) 6. Match points will also be extended for use with authority records, again completing a feature for which stubs already existed. (bug 7475) 7. There is no way to export authority records other than via a direct SQL query, which makes it difficult for hosted libraries to get their data out of Koha without the help of their support vendors. We propose to change the "Export bibliographic/holdings" tool to the "Export data" tool, and add a tab to enable librarians with the proper permissions for the export tool to export their authority records directly from the staff client. (bug 8202) 8. Some librarians have requested the ability to save individual authority records, so a "Save authority" button will be added next to the "Edit" button when viewing authority records. (bug 8203) 9. One of the great promises of DOM indexing in Zebra (and the adoption of solr as an indexing technology) is the ability to incorporate alternate forms of headings into bib records when exporting bibs for indexing. We will add the plumbing for arbitrary record filters, and implement a filter that checks each heading in bib records for alternate forms, and includes them prior to exporting the record for indexing. (bug 7417) 10. Instead of using only textual strings for see also links, the ability to use $9 in see also fields in authority records (5xx in MARC21, NORMARC, and UNIMARC) will be added, to simplify heading disambiguation. This will enable us to create a value builder plugin using the existing thesaurus functionality that will automatically populate the see also heading control fields with metadata about the link (broader term, narrower term, etc.) (bug 8207) 11. Right now when cataloging, catalogers have only two options for adding a new authority: turn on AutoGenerateAuthorities, and later edit the authority record to justify its creation, or save the bib record they are working on, create a new authority record in the authority module, wait for the new record to be indexed, and open the bib record back up to use the authority finder plugin. We intend to add a "Create authority" button to the authority finder plugin which will allow the cataloger to create an authority in a new window and (similar to fast add in circ) automatically fill out the selected heading field in the bib record. (bug 8208) 12. At times, people may want to search for terms that are related to the one they search for. For example, someone interested in books about Feet may also be interested in all books about specific parts of feet, including books about Toes, Heels, etc. We will add three new special pseudo-CCL search prefixes which will first search the authority file for the specified heading, then search not just for that term but also for broader terms (pseudo-CCL prefix su-br:), narrower terms (pseudo-CCL prefix su-na:), or all related terms (pseudo-CCL prefix su-rl:). (bug 8211) 13. Because patrons may not always realize that they want to search for a related term instead of the term they entered, we will also add a "Did you mean?" feature to the OPAC, which suggests terms related to authorities that match the user's search. (bug 8209) 14. Although not all authority records contain useful information, many do, and depending on the type of collection, access to that information can be critical to both librarians and patrons. In order to simplify looking up authorities referred to in particular records, a link from subject headings to their related authorities will be added to the OPAC. A patch which adds this to the "normal" mode bib details display has already Passed QA (bug 5888), so unless an unsolvable problem is found with that patch, implementation will focus on the XSLT view. (bug 8210) Any questions or comments are welcome. Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 2