May 2018 - Koha-bugs - lists.koha-community.org

[Bug 18110] New: Adds FR to the syspref AddressFormat
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18110 Bug ID: 18110 Summary: Adds FR to the syspref AddressFormat Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 20674] New: One off report
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20674 Bug ID: 20674 Summary: One off report Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: tlamannajr(a)chplnj.org QA Contact: testopia(a)bugs.koha-community.org Right now the only way to create and run a report is to save it to a list, but there are plenty of times I just need a one-off report and it's a bit of a pain to have to create and name a report then delete in when I'm done. This clutters up the reports list a lot. Not a massive problem, but I'm hoping we can streamline one off reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20848] New: Add the ability to batch renew or easily renew relative checkouts attached to the guarantor
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20848 Bug ID: 20848 Summary: Add the ability to batch renew or easily renew relative checkouts attached to the guarantor Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a guarantor has multiple guarantees, it is a time consuming process to go into each account and renew the guarantees items in addition the guarantor. It would be great to see the ability to easily access all the checkouts at the one time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20843] New: For fixed fields requiring computer generated data, default value or plugin?
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20843 Bug ID: 20843 Summary: For fixed fields requiring computer generated data, default value or plugin? Change sponsored?: --- Product: Koha Version: 17.05 Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emjhet(a)pa.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As of 2018, the Koha Frameworks that were on our system (set up in late 2011) were designed for different types of records but the MARC fixed fields 000, 007, and 008 did not accurately code for those materials. I am making unique Frameworks that I hope will accurately code for specific materials. I have put a default value in the 000 (despite the need for a computer generated record length in the 00-04 character position) and the 007, and as of now have left the 008 blank. I can not use a default value in the 008 because position 00-05 requires the date entered on file. I would, however, like to change the data currently in the 008 plugin. I simply do not find it helpful to have the default of position 06 be "b" (no dates given, B.C. date involved.) It is absolutely ridiculous for video recordings, yet not all my co-workers understand to edit this field. Is there a way to edit the plugin? Support told me that there can be only one plugin per field, but I was not sure based upon Bug 3013, Bug 14815, and Bug 19473. Thank you. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20842] New: Change the default Framework from Koha's default to another saved framework
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20842 Bug ID: 20842 Summary: Change the default Framework from Koha's default to another saved framework Change sponsored?: --- Product: Koha Version: 17.05 Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emjhet(a)pa.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Rather than have our system set to use the Koha Default framework as our default, we would like to use a framework we have created as our default framework for both created and imported records. I'm unaware of where/if this can be altered; Support mentioned that it was a nearly-resolved bug, but I could find no report on it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20812] New: Tag "" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2615.
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20812 Bug ID: 20812 Summary: Tag "" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2615. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: biblioteca(a)colprecentro.edu.co QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Tag "" is not a valid tag. at /usr/share/koha/lib/C4/Biblio.pm line 2615. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20802] New: Routing lists versus patron notification emails for serial issues just received.
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20802 Bug ID: 20802 Summary: Routing lists versus patron notification emails for serial issues just received. Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com If these are separate features and work independently of each other then I think the terminology relating to the two different functions is mixed up and confusing in Koha. We do not have routing lists enabled so we do not see any of that functionality in our serials module. We have most of the patron notification ‘letter’ flags in each subscription ticked, so users can (in theory) opt-in to receive email messages via the OPAC. A number of users here have, but zero emails are being sent. It appears that the Patron notification options we see when setting up a subscription refer to Routing List (Notices and Slips –RLIST). We don’t use the feature… so no emails are sent. We have 900+ subscriptions with the “opt-in tickbox enabled, but emails don’t get sent. Until we can unravel this problem we want to remove the misleading option- the suggested solution is to use jquery to hide the option on the OPAC for now. Has anyone actually got patron notification working separate from routing list functionality, and if so how? Is routing list functionality somehow intertwined with patron notification? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 20759] New: Enhace GoogleBookPreview
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20759 Bug ID: 20759 Summary: Enhace GoogleBookPreview Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org It should be nice if we could improve the google preview, now it is linking cover image with isbn, but for ancient books, the most valuable books, isbn is not available, it should be great if we can add the google book id on 024 por example and use to link to the bookcover and the google preview (usualy fulltext) -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 20704] New: Add borrower attribute types as run time parameters in reports
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20704 Bug ID: 20704 Summary: Add borrower attribute types as run time parameters in reports Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Feature request: add <<*|attribute_type>> as a run time parameter. This would list the values from borrower_attribute_types.description in a drop down, and choose the corresponding value of borrower_attribute_types.code. For example, let's say that we had the following values in borrower_attribute_types: +--------------------+----------+ | description | code | +--------------------+----------+ | Drivers License | DL | | Favourite Colour | FAVCOLOR | | PC Allowed | PC | | Previous system ID | PREVID | +--------------------+----------+ Then we could write queries like: SELECT firstname, surname, cardnumber, attribute FROM borrowers INNER JOIN borrower_attributes USING (borrowernumber) WHERE borrower_attributes.code = <<Borrower attribute type|attribute_type>> When run, the user would be prompted for 'Borrower attribute type', and would get a drop down containing +--------------------+ | Drivers License | | Favourite Colour | | PC Allowed | | Previous system ID | +--------------------+ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20560] New: Can't call method "userid" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 407.
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20560 Bug ID: 20560 Summary: Can't call method "userid" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.p l line 407. Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: ichemclibrary(a)gmail.com Can't call method "userid" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 407. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2