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

[Bug 8504] New: patron import explains attributes import wrong
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8504 Priority: P5 - low Change sponsored?: --- Bug ID: 8504 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: patron import explains attributes import wrong Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Patrons Product: Koha On the Import patrons page there are notes on the right side of the screen. The fourth bullet displays incorrect information regarding the import of multiple patron type and value pairs in the patron_attributes field. If you are importing more than one patron_attribute pair then the entire comma-separated list of attribute types and value pairs must be surrounded by double quotes. I am not sure if this applies to the "second syntax" as mentioned in the last sentence in the bullet. Instead of STARTDATE:January 1 2010,TRACK:Day it should be "STARTDATE:January 1 2010,TRACK:Day" I don't know if this is a bug or a template change and I don't know about the second example given on that page yet. "STARTDATE:January 1, 2010","TRACK:Day" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8658] New: Don't display patron attributes which have been limited to another patron category
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8658 Priority: P5 - low Change sponsored?: --- Bug ID: 8658 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Don't display patron attributes which have been limited to another patron category Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Patrons Product: Koha This probably only happens if you enter some data into patron attributes and then later limit entry of that attribute by category. I have a patron who has data stored in an attribute, but that attribute has since been limited to another patron category. Even though the data exists I don't think it should display if it no longer applies to that patron category. Otherwise you can see patron attributes displayed on a record which cannot be edited because the editor honors the limitation by category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 7770] New: usage of OPACBaseURL
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7770 Priority: P5 - low Change sponsored?: --- Bug ID: 7770 CC: gmcharlt(a)gmail.com Assignee: paul.poulain(a)biblibre.com Summary: usage of OPACBaseURL QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: laurence.lefaucheur(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: System Administration Product: Koha System preferences OPACBaseURL is used at different places in koha, for instance : - CAS authentication (7745) - OAI - file upload (6874) Description of the syspref indicates that http:// will automatically be added. We tested that for oai biblio url and for CAS, it is not the case, and we have to fill http:// in the syspref. The usage of this syspref in Koha and how it should be really filled should be precised so that it is consistent everywhere -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 10654] New: Add featute: export basket in CSV, list of custom formats for various vendors
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10654 Bug ID: 10654 Summary: Add featute: export basket in CSV, list of custom formats for various vendors Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 19977 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=19977&action=edit screenshot of menu Hello, in Koha we can set custom format of CSV for basket export from OPAC. I think that very useful feature can be same option for export from basket in module acquisition. Our vendors accept import of orders in CSV in their e-shops but formats are various. Is possible to add into button "Export this basket as CSV" some pull-down list of vendors and export order in specific CSV format? Thank You. Mike -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 9120] New: Typing the ENTER key when submitting a tag from search results reloads the page
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9120 Bug ID: 9120 Summary: Typing the ENTER key when submitting a tag from search results reloads the page Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org If you have TagsInputOnList enabled and you are entering tags from the OPAC search results page, typing ENTER instead of clicking the "Add" button reloads the page without submitting the tag. The tag submission operation should be triggered without affecting the page state. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 11120] New: The date option for the overdue_notices cronjob is broken
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11120 Bug ID: 11120 Summary: The date option for the overdue_notices cronjob is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 7447 introduces the --date option for overdue notices. This option has never worked: the code is waiting for a value but the option is defined as a boolean. The date should be defined as --date:s and the script should correctly manage this option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 12739] New: SendAlerts function does not take care of "html" format in letter
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12739 Bug ID: 12739 Summary: SendAlerts function does not take care of "html" format in letter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org If you want to add some html tags in your notification letters (except overdues or holds), for exemple a link on you FB page or some hilghtning, it is not taken into account. Tags are written as plain text in the email even if html is activated. That's because C4:Letters::SendAlerts function does not check letter format but always sends email with Content-Type = "text/plain" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 9227] New: items in transit can be checked out without warning
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9227 Bug ID: 9227 Summary: items in transit can be checked out without warning Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you try to check out items with different statuses (on hold for example) you get a warning, but if you try to check out an item that's in transit you don't get that warning and should. See here: http://screencast.com/t/wu3iJMdU -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 10606] New: query in GetUpcomingDueIssues
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '15

30 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10606 Bug ID: 10606 Summary: query in GetUpcomingDueIssues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The patch for bug 9362 (which I did accept into master) introduces a MySQLism: Using HAVING without GROUP BY is a MySQLism, so at some point the query will have to become: SELECT issues.*, items.itype as itemtype, items.homebranch, TO_DAYS( date_due )-TO_DAYS( NOW() ) as days_until_due, branches.branchemail FROM issues LEFT JOIN items USING (itemnumber) LEFT OUTER JOIN branches USING (branchcode) WHERE returndate is NULL AND (TO_DAYS( date_due )-TO_DAYS( NOW() )) > 0 AND (TO_DAYS( date_due )-TO_DAYS( NOW() )) < ?; This is a pity, as it would be nice to be able to use "days_until_due" as an alias to make the query more readable, but it simply isn't portable. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 10263] New: Add ability to limit which branch can edit a bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '15

30 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10263 Bug ID: 10263 Summary: Add ability to limit which branch can edit a bibliographic record Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: kyle.m.hall(a)gmail.com CC: m.de.rooy(a)rijksmuseum.nl Right now, it's possible to limit who can edit items by using IndependantBranches. However, Koha has no method of limiting who can edit bibliographic records, as they have no defined owner. -- You are receiving this mail because: You are watching all bug changes.

1 31