October 2014 - Koha-bugs - lists.koha-community.org

[Bug 5592] New: circ rule cloning can be dangerous
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5592 Summary: circ rule cloning can be dangerous Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 The clone circ rules widget on the circ rules page unconditionally deletes the target library's existing rules and replaces them with copies of the rules from the source library. Consequently, if the clone rule button is accidentally clicked, a lot of configuration work can be destroyed in an instant. To avoid this: * there should *always* be a required confirmation step, whether the clone-rules.pl script is accessed directly or via the smart-rules.pl page * even better, a backup copy of the previous version of the target library's rules could be made The library who ran into this bug had tried cloning the rules form a different library because they thought that would be a way to copy over that library's rules and add them to the rules that the target library had previously entered -- that kind of cloning-via-merge feature also seems like a good idea, in fact. -- 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 4

[Bug 7817] New: Items Permanent location (shelving location) is set to NULL when item is edited
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7817 Priority: P5 - low Change sponsored?: --- Bug ID: 7817 Assignee: gmcharlt(a)gmail.com Summary: Items Permanent location (shelving location) is set to NULL when item is edited QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: joy(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_6 Component: Cataloging Product: Koha When an item is edited, the field items.permanent_location is set to NULL. This causes significant problems when a library is utilizing the CART and PROC system preferences to assign CART and PROC shelving locations. If items.permanent_location is NULL then there is no way to restore the original shelving location for these items. This results in significant data loss for libraries. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 10633] New: Table suggestions needs some work
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10633 Bug ID: 10633 Summary: Table suggestions needs some work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The table suggestions is missing FK constraints and cascades to ensure a suggestion is anonymized when the borrower who suggested it gets deleted. The current table definition is: 2077 DROP TABLE IF EXISTS `suggestions`; 2078 CREATE TABLE `suggestions` ( -- purchase suggestions 2079 `suggestionid` int(8) NOT NULL auto_increment, -- unique identifier assigned automatically by Koha 2080 `suggestedby` int(11) NOT NULL default 0, -- borrowernumber for the person making the suggestion, foreign key linking to the borrowers table 2081 `suggesteddate` date NOT NULL default 0, -- date the suggestion was submitted 2082 `managedby` int(11) default NULL, -- borrowernumber for the librarian managing the suggestion, foreign key linking to the borrowers table 2083 `manageddate` date default NULL, -- date the suggestion was updated 2084 acceptedby INT(11) default NULL, -- borrowernumber for the librarian who accepted the suggestion, foreign key linking to the borrowers table 2085 accepteddate date default NULL, -- date the suggestion was marked as accepted 2086 rejectedby INT(11) default NULL, -- borrowernumber for the librarian who rejected the suggestion, foreign key linking to the borrowers table 2087 rejecteddate date default NULL, -- date the suggestion was marked as rejected 2088 `STATUS` varchar(10) NOT NULL default '', -- suggestion status (ASKED, CHECKED, ACCEPTED, or REJECTED) 2089 `note` mediumtext, -- note entered on the suggestion 2090 `author` varchar(80) default NULL, -- author of the suggested item 2091 `title` varchar(255) default NULL, -- title of the suggested item 2092 `copyrightdate` smallint(6) default NULL, -- copyright date of the suggested item 2093 `publishercode` varchar(255) default NULL, -- publisher of the suggested item 2094 `date` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, -- date and time the suggestion was updated 2095 `volumedesc` varchar(255) default NULL, 2096 `publicationyear` smallint(6) default 0, 2097 `place` varchar(255) default NULL, -- publication place of the suggested item 2098 `isbn` varchar(30) default NULL, -- isbn of the suggested item 2099 `mailoverseeing` smallint(1) default 0, 2100 `biblionumber` int(11) default NULL, -- foreign key linking the suggestion to the biblio table after the suggestion has been ordered 2101 `reason` text, -- reason for accepting or rejecting the suggestion 2102 `patronreason` text, -- reason for making the suggestion 2103 budgetid INT(11), -- foreign key linking the suggested budget to the aqbudgets table 2104 branchcode VARCHAR(10) default NULL, -- foreign key linking the suggested branch to the branches table 2105 collectiontitle text default NULL, -- collection name for the suggested item 2106 itemtype VARCHAR(30) default NULL, -- suggested item type 2107 quantity SMALLINT(6) default NULL, -- suggested quantity to be purchased 2108 currency VARCHAR(3) default NULL, -- suggested currency for the suggested price 2109 price DECIMAL(28,6) default NULL, -- suggested price 2110 total DECIMAL(28,6) default NULL, -- suggested total cost (price*quantity updated for currency) 2111 PRIMARY KEY (`suggestionid`), 2112 KEY `suggestedby` (`suggestedby`), 2113 KEY `managedby` (`managedby`) 2114 ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 10631] New: Table alert should have a FK on borrowernumber and entries be deleted with the referenced borrower
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10631 Bug ID: 10631 Summary: Table alert should have a FK on borrowernumber and entries be deleted with the referenced borrower Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The table alert is currently used to store information about email subscriptons for new serial issues. The current table defnition is: 2682 DROP TABLE IF EXISTS `alert`; 2683 CREATE TABLE `alert` ( 2684 `alertid` int(11) NOT NULL auto_increment, 2685 `borrowernumber` int(11) NOT NULL default 0, 2686 `type` varchar(10) NOT NULL default '', 2687 `externalid` varchar(20) NOT NULL default '', 2688 PRIMARY KEY (`alertid`), 2689 KEY `borrowernumber` (`borrowernumber`), 2690 KEY `type` (`type`,`externalid`) 2691 ) ENGINE=InnoDB DEFAULT CHARSET=utf8; 2692 As I see it borrowernumber should be a FK and we are missing some cascades to make sure the table is cleaned up when a borrower is deleted. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 12078] New: z3950_search.pl parser error when viewing card
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '15

08 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12078 Bug ID: 12078 Summary: z3950_search.pl parser error when viewing card Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Similar to http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9668, we get an error in z3950_search.pl when we click on the card link in 3.12. It produces the following software error: :241: parser error : PCDATA invalid Char value 28 <subfield code="h"></subfield> Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 12912] New: trouble with opachiddenitems
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12912 Bug ID: 12912 Summary: trouble with opachiddenitems Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org I have trouble with sys pref opachiddenitems with 3.12. I put location:[CODE] but items of the location are still displayed. I tried homebranch, itype but it make the same. anyone having trouble with opachiddenitems since 3.12. With 3.8 it worked. Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 6780] New: Log duplicate card issuance
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6780 Bug #: 6780 Summary: Log duplicate card issuance Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com If patron related logging is turned on, log duplicate card issuance -- 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 6760] New: Generate new card number on renewals and duplicate card issuance
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6760 Bug #: 6760 Summary: Generate new card number on renewals and duplicate card issuance Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Some libraries need a new card to be generated on membership renewal and duplicate card issuance. A new sys pref will be created for this purpose. -- 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 2

[Bug 8601] New: Allow more pictures on Patron Cards
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8601 Priority: P5 - low Change sponsored?: --- Bug ID: 8601 Assignee: cnighswonger(a)foundations.edu Summary: Allow more pictures on Patron Cards Severity: enhancement Classification: Unclassified OS: All Reporter: derrynj(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Label printing Product: Koha Currently there is only 2 pictures allowed on patron card. This is acceptable, however it would be nice to be able to add more with an "add another image" button or something along those lines. At the very least, could we free up a custom image by making the patron image a separate component? I've tried adding extra images to the XML code in the database, and it seems to work just by incrementing the image number value. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 7569] New: Add Google Transliteration tool to fields during cataloging and in advanced search in OPAC
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7569 Bug #: 7569 Summary: Add Google Transliteration tool to fields during cataloging and in advanced search in OPAC Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha.sekjal(a)gmail.com Google's transliteration tool can be turned on for basic search in OPAC's masthead. Attemt to add this tool to: 1. Cataloging pages especially addbooks.pl: this will allow users to catalog items in other languages efficiently 2. Advanced search fields in the OPAC -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2