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

[Bug 5979] New: OPAC : using OPACISBD systempreference to display link
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '15

17 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5979 Bug #: 5979 Summary: OPAC : using OPACISBD systempreference to display link Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org Blocks: 5584 The OPACISBD system preference is used in order to be able to have one ISBD for OPAC another one for intranet. But the link ISBD at OPAC was depending on the presence or absence of value in ISBD which is for intranet. This patch fixes the behaviour to depend on the correct system preference at OPAC -- 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 32

[Bug 11029] New: Marc Language Code in a list
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '15

17 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11029 Bug ID: 11029 Summary: Marc Language Code in a list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: fabreupeixoto(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When inputing a language code KOHA could have a pre-defined list of language codes from the Library of Congress Marc Language Code List. It would save time and would reduce errors in cataloguing. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 10067] New: decreaseLoanHighHolds messes with specify due date
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '15

17 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10067 Bug ID: 10067 Summary: decreaseLoanHighHolds messes with specify due date Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 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 It appears that when the criterion for the shortened loan period is met, not only does that particular item get the shortened loan period, so does any subsequent item checked out in that session. It appears that decreaseLoanHighHolds functionally affects Specify due date, and requires the staff member to click on Clear in order to make sure the correct loan period is applied for the next item(s). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 12216] New: One should be able to override zebra configuration on a per instance basis
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '15

17 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12216 Bug ID: 12216 Summary: One should be able to override zebra configuration on a per instance basis Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz One should be able to customise the Zebra configuration on a per instance basis by just over-riding the default files with custom ones added under /sites/instancename/. This should be simple to achieve during install time by adding /etc/koha/sites/instancename/ to the profilePath in the already create instancename/*.cfg files. Patch to follow -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 10056] New: Styling Issue - Div does not grow.
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '15

16 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10056 Bug ID: 10056 Summary: Styling Issue - Div does not grow. Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: gmcharlt(a)gmail.com Created attachment 17454 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=17454&action=edit Screenshot of bad styling The '.ui-tabs-panel' does not grow correctly on the Biblio and Authorities pages. When a heading is clicked, and therefore subfields are displayed, then bounding box does not grow to accommodate the enlarged content, leaving a border through the middle of a subfield; See screenshot attached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11130] New: Change pl Place-publication index for Marc21
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '15

16 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11130 Bug ID: 11130 Summary: Change pl Place-publication index for Marc21 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org According to ccl.properties, the pl Place-publication index is supposed to include 008/15-17 and 260$a. In record.abs, we have the index include all 260 fields. This patch removes the index for the whole field 260, leaving only $a (and 008/15-17). -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 7174] New: Authentication rewriting
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '15

16 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7174 Bug #: 7174 Summary: Authentication rewriting Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: paul.poulain(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Blocks: 7119 Auth.pm does too many things, it must be splitted in smaller parts. In 3.6, it does : - authentifying - checking & setting permissions - setting a lot of syspref available on each template (many of them being unused in most templates) - retrieving template How to do it is still to be discussed. This entry is low priority, once we will have plack, for example, it may be obvious to use Plack authentication tools. -- 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 45

[Bug 12872] New: Exclude limited number of fields from Zebra DOM indexing
by bugzilla-daemon＠bugs.koha-community.org 14 Nov '15

14 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12872 Bug ID: 12872 Summary: Exclude limited number of fields from Zebra DOM indexing 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 Here is another approach for excluding a limited number of fields from Zebra DOM indexing. (Check the see also reports too.) I rename index_all to index_most and add a few lines to that named template. This will not win beauty prices, but imo it is easier than adding any or anywhere to a large number of fields. What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 12768] New: Replacement cost and processing fee management
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12768 Bug ID: 12768 Summary: Replacement cost and processing fee management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Sponsored by Halland County Library RFC : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement#Replacement_… Description A default replacement cost and a processing fee will be added to the item type page. The input form and the table that displays all iten types will have these two new field/column : "Default replacement cost" "Processing fee (When lost)" Two system preferences will be added. "UseDefaultReplacementCost" to enable the use of the value set on the item type level. "ProcessingFeeNote" to set the value that will populate the note in the table "accountlines" when the processing fee are applied. These elements will be used as follows : When the "longoverdue.pl" script is run : If "UseDefaultReplacementCost" is enabled and the items.replacementcost = 0 : The value of "Default replacement cost" set up in the itemtype populate the "accountlines" table. If the value of "Processing fee (When lost)" is > 0, it is also used to populate the table "accountlines." The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. If "UseDefaultReplacementCost" is enabled and the value in items.replacementcost> 0 The default koha behavior is used. The value in items.replacementcost populate the "accountlines" table. If the value of "Processing fee (When lost)" defined in the document type is > 0, it is also used to populate the table "accountlines." The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. If "UseDefaultReplacementCost" is disabled : The default koha behavior is used. If the value of "Processing fee (When lost)" defined in the document type is > 0, it is also used to populate the "accountlines" table. The value in the system preference "ProcessingFeeNote" is used to update the note in accountlines for this item. Otherwise, no processing fees are added. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 11594] New: store both item type and document type in statistics
by bugzilla-daemon＠bugs.koha-community.org 13 Nov '15

13 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11594 Bug ID: 11594 Summary: store both item type and document type in statistics 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I copy here a comment originaly made on bug 9351 For some libraries, what is needed in statistical table is BOTH items.itype and biblioitems.itemtype, and maybe a clear indication (a 3rd column "circulation_type" ?) of which type is was used for circulation rights. Ex: In Rennes 2 we use item level for defining circulation rules. items.itype are codes for "Short Loan", "Normal Loan", "Long loan". biblioitems.itemtype are "Book", "Serial", "DVD" etc. For our annual report, we need to know the number of Books, Serials, DVD checked out, even if the type used for defining circulation rules are "Short loan", and not "Book". But other libraries may have different settings, and may have need to make stats on item level, or maybe cross stats on both level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1