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

[Bug 8147] New: suggestions management forgets branch info
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '15

05 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8147 Priority: P5 - low Change sponsored?: --- Bug ID: 8147 Assignee: henridamien(a)koha-fr.org Summary: suggestions management forgets branch info Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Acquisitions Product: Koha I'm on the suggestion management page and I choose to filter to see ANY library. I then accept a suggestion from another library and when it shows me the Accepted tab I see nothing because the filter has changed back to be just my library. The filter should remember my selection after accepting, rejecting or checking a suggestion. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 13789] New: facets with accented utf-8 characters generate double encoded links
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '15

05 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13789 Bug ID: 13789 Summary: facets with accented utf-8 characters generate double encoded links 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: dpavlin(a)rot13.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 5456] New: Create a link to opac-ics.pl
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '15

05 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5456 Summary: Create a link to opac-ics.pl Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Koha has a script called opac-ics.pl which can export the due dates for a logged in user in iCalendar/.ics format, but there does not seem to be a link to this script anywhere in the patron user interface. [09:26] chris: i think i wrote it in 2006, and it mostly still works [09:28] magnus: is there a link to it anywhere in the opac interface, or do you have to know the url? [09:28] chris: there used to be [09:28] chris: not sure when it got removed, we should test it all works well, fix it if it doesnt and put the link back [09:31] magnus: hm, i get to download a calendar file - guess that means users have to remember to do it every so often... would it be possible to have an interface that e.g. iCal could "subscribe" to? [09:31] magnus: guess that would mean making obscure URLs or putting username/password in the url... [09:34] chris: magnus: yeah, that was my next plan an md5 hash -- 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 3

[Bug 7804] New: Add Koha Plugin System
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '15

04 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7804 Priority: P5 - low Change sponsored?: --- Bug ID: 7804 Assignee: gmcharlt(a)gmail.com Summary: Add Koha Plugin System QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: kyle.m.hall(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: Tools Product: Koha In the long run, I imagine a system where Koha users can upload plugins to a koha community plugin site and then search for, install and update plugins from within Koha itself, much like Wordpress can. -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 12756] New: Koha to MARC mapping 264$a, $b, and, $c
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '15

03 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12756 Bug ID: 12756 Summary: Koha to MARC mapping 264$a, $b, and, $c Change sponsored?: --- Product: Koha Version: 3.16 Hardware: All OS: All Status: NEW Keywords: rel_3_16_candidate Severity: new feature Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hector.hecaxmmx(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This enhances it's for introduce new fields into the biblio and biblioitems tables for the new field 264 and the respective subfields. This imply to add, first, three new fields like 260$c biblio.copyright, 260$a biblioitems.place, and 260$b biblioitems.publishercode. Second mapping with the respective field 264 in all MARC frameworks. Important. According to the online help, you can not map more than one MARC field to a Koha field. http://manual.koha-community.org/3.16/en/catadmin.html#kohamarcmapping This will enable to use in all modules that are needed for display, for example, acquisition, serial, cataloging module, etc. Since new RDA MARC fields have been added to the database will not be necessary to do so. Likewise, XSLT for display in Intranet and OPAC Bootstrap has been corrected and signed off in the following bugs: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12724 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12725 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12726 Next to this there will be a hard work to research all the modules where the field 264 can be displayed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 9011] New: Add the ability to store the last patron to return an item
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9011 Priority: P5 - low Change sponsored?: --- Bug ID: 9011 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Add the ability to store the last patron to return an item Severity: enhancement Classification: Unclassified OS: All Reporter: kyle(a)bywatersolutions.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha Currently if the AnonymousPatron system preference is in use, all patron data is anonymized. Some libraries would like to be able to see the last patron who returned out an item ( in case of damage ) but still keep all other patrons anonymized. * Add the field items.last_borrower, foreign key to borrowers.borrowernumber * Add new system preference StoreLastBorrower * If StoreLastBorrower is enabled, upon checkin have Koha set this new field to the patron who last returned this item. * If this new field has a value, link to the patron from the item details page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 177

[Bug 14494] New: Terribly slow checkout caused by DateTime->new in far future
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14494 Bug ID: 14494 Summary: Terribly slow checkout caused by DateTime->new in far future Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org An expiry date of 9999-12-31 for organizations was a nice idea :) But checking out an item to that patron takes 1 minute or longer ! The cause? The following lines in CanBookBeIssued seem to be the main cause: my $expiry_dt = DateTime->new( year => $y, month => $m, day => $d, time_zone => C4::Context->tz, ); This call takes forever with 9999-12-31 when the timezone is not 'floating' or 'UTC', but e.g. Europe/Amsterdam. If the timezone is UTC, it takes 0.0002 seconds. DateTime gives the following advices: === Do not try to use named time zones (like "America/Chicago") with dates very far in the future (thousands of years). The current implementation of DateTime::TimeZone will use a huge amount of memory calculating all the DST changes from now until the future date. Use UTC or the floating time zone and you will be safe. •use UTC for all calculations If you do care about time zones (particularly DST) or leap seconds, try to use non-UTC time zones for presentation and user input only. Convert to UTC immediately and convert back to the local time zone for presentation The results DateTime.pm produces are predictable and correct, and mostly intuitive, but datetime math gets very ugly when time zones are involved ... === We are not doing that currently. We use in C4::Context: DateTime::TimeZone->new(name => 'local') Could we implement the calculation/presentation advice of DateTime in Koha somehow? -- You are receiving this mail because: You are watching all bug changes.

1 50

[Bug 13452] New: Average checkout report always uses biblioitems.itemtype
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13452 Bug ID: 13452 Summary: Average checkout report always uses biblioitems.itemtype Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The average checkout report reports/issues_avg_stats.pl always uses biblioitems.itemtype, regardless to item-level_itypes system preference. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 7045] New: Default-value substitution inconsistent
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7045 Bug #: 7045 Summary: Default-value substitution inconsistent Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: ruth(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com If you supply a default value in a framework field, you may include YYYY, MM, DD, and user, to substitute for the year, month, day, and currently-logged-in username, respectively. The downside of this is that the word "user" cannot be used in a default value for a note! Patch coming shortly, to change the substitution to require USER, and to allow the use of YY to insert the last two digits of the year. -- 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 25

[Bug 10294] New: when the word "user" is included in default in framework, surname of login creating record inserted
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '15

02 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10294 Bug ID: 10294 Summary: when the word "user" is included in default in framework, surname of login creating record inserted Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: drnoe(a)bywatersolutions.com CC: m.de.rooy(a)rijksmuseum.nl When the word "user" is included in a default value in a MARC subfield structure of a tag in a framework, the surname of he user login creating record is inserted in the place of the word "user." Create the deafualt value in the framework -In MARC frameworks. -Select a MARC structure of any framework to edit. -Select the subfields to edit. -Select the Edit Subfields button. -Select Display more constraints of any subfield tab. -Include "user" in the default value. (make sure hidden is st to 0). -Save Changes. Create a new record -In Cataloging, select New Record with the edited framework -Go to the tag with the default value. -The surname of the user with which you create the new record will be in the tag in the place of user. -- You are receiving this mail because: You are watching all bug changes.

1 5