December 2015 - Koha-bugs - lists.koha-community.org

[Bug 15108] New: OAI-PMH provider improvements
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15108 Bug ID: 15108 Summary: OAI-PMH provider improvements Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org - Fixed date handling to use UTC as specs require. - Added support for deleted records. - Added support for second precision in time stamps. - Added support for marc21 metadata prefix as recommended in the guidelines (synonym for marcxml). - ListIdentifiers and ListRecords always return records in biblionumber order. - Improved performance of database queries especially for large collections. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 13432] New: SIP Server does not respect timeout setting
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13432 Bug ID: 13432 Summary: SIP Server does not respect timeout setting Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Koha's SIP server accepts timeout parameters, but those parameters are only used for the login portion of a telnet transport session. Other than that, they are ignored, and as long as whatever opened the connection keeps it open, it will stay open indefinitely. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 7012] New: limit to available not limiting anymore
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Bug #: 7012 Summary: limit to available not limiting anymore Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When I limit to only available items in the OPAC it doesn't appear to be limiting anymore. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 6

[Bug 15305] New: KOHA SIP2 checkout doesn't update of the item holding status
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15305 Bug ID: 15305 Summary: KOHA SIP2 checkout doesn't update of the item holding status Change sponsored?: --- Product: Koha Version: 3.20 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridayjune(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 45410 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=45410&action=edit KOHA_SIP2_Checkout I am using KOHA version 3.20 and I am able to check out the item, but the item status is always showing Available. 1) This is my checkout message: 11NN20151202 08062920151227 030629AOmylib|AAthida|ABB1246857|AC| 2) This is my institution policy in SIPconfig.xml. <institution id="mylib" implementation="ILS" parms=""> <policy checkin="true" renewal="true" checkout="true" status_update="true" offline="false" timeout="100" retries="5"/> </institution> 3) The first item is checked out by using SIP2 in the following screenshot. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 14049] New: Personalized OPAC purchase suggestion fields
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14049 Bug ID: 14049 Summary: Personalized OPAC purchase suggestion fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Before using Koha we were using a local develop for purchase suggestion requests («desiderata»). Now I'm trying to extend/add suggestion fields to add some data we were asking in the form and Koha doesn't include, something like what ExtendedPatronAttributes syspref does with patron fields. First I naively tried to add to opac-suggestions.tt <li><label for="newField">Extrafield:</label><input type="text" id="newfield" name="newfield" maxlength="40" /></li> and on submit: onsubmit="this.note.value=this.note.value+' - '+this.newfield.value; return true;" to concatenate extended fields (yeah, dirty) but it seems Suggestions.pm do a foreach walk over form ids: Software error: DBIx::Class::ResultSet::create(): No such column alum on Koha::Schema::Result::Suggestion at /usr/share/koha/lib/C4/Suggestions.pm line 450 Koha should let staff user to extend suggestions fields, maybe with a ExtendedSuggestionFields sysfref. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 15352] New: a way not to show the full url in the holdings
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15352 Bug ID: 15352 Summary: a way not to show the full url in the holdings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 45578 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=45578&action=edit item with a url See the image. I would love a way to define text to display for the url in an item instead of showing the big long ugly url. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11311] New: Browse selected authorities
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11311 Bug ID: 11311 Summary: Browse selected authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 14395] New: Two different ways to calculate 'No renewal before' (days or hours)
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14395 Bug ID: 14395 Summary: Two different ways to calculate 'No renewal before' (days or hours) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: h.meissner.82(a)web.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The 'No renewal before' setting is based on the exact DateTime of the due date. This can be confusing when the loan period is measured in days, because Koha sets the time for the due date to 23:59. So with 'No renewal before' set to one day (exactly 24 hours) the loan will be renewable on the next day, but not before 23:59 when there is only one minute left of the day. There should be a syspref to ignore the exact time and only check the date. So that an item issued with 1 day 'No renewal before' will be renewable any time on the next day. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 13805] New: Installer does not work under Plack
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13805 Bug ID: 13805 Summary: Installer does not work under Plack Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)biblibre.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When going to the installer (without the DB structure), you have to log twice before starting the installation. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 13068] New: New feature for DB update and sandbox
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13068 Bug ID: 13068 Summary: New feature for DB update and sandbox Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.poulain(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Most patches with a DB update cannot be applied automatically on sandboxes, because they have a conflict in updatedatabase.pl I propose to have a new directory (say dev_update), that will be used during the development process. * when you submit a patch with a db update, you developer must put the DB update part into the dev_update/ directory, NOT in updatedatabase.pl * the updatedatabase.pl, at the end of the update process, checks if there is something in the dev_update. If there is, what's here is applied. * when the patch is pushed by the Release Manager, the DB update is moved out from the dev_update directory, and included into updatedatabase.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 152