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

[Bug 6795] New: Branch-specific OPAC preferences
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '14

29 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6795 Bug #: 6795 Summary: Branch-specific OPAC preferences Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Database AssignedTo: gmcharlt(a)gmail.com ReportedBy: melia(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Using the Contextual Preferences Engine, this moves the following preferences out of Sysprefs and down to the per-branch level. LibraryName OPACBaseURL opaccolorstylesheet opaccredits opacheader opaclayoutstylesheet OpacMainUserBlock OpacNav OPACNoResultsFound opacsmallimage opacstylesheet OPACUserCSS opacuserjs -- 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 5

[Bug 7125] New: can't change tag in frameworks
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '14

28 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7125 Bug #: 7125 Summary: can't change tag in frameworks Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com see attached. When I go to edit a framework and change the tag number it looks like I'm able to, but when I hit save my changes aren't saved and no error message is generated. If this tag number isn't editable it shouldn't appear as if it is. -- 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 10

[Bug 7327] New: Translation script doesn't like concatenated javascript strings
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '14

26 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7327 Bug #: 7327 Summary: Translation script doesn't like concatenated javascript strings Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: ian.walls(a)bywatersolutions.com I noticed that some alerts are (no longer?) translated. Example: cat-toolbar.inc is_confirmed= alert(_('There are [ '+ count +' ] item(s) attached to this record \n You must delete all items before deleting this record.')); This string doesn't get translated at all now. Also the \n is not good because it causes problems in Pootle. The only solution to make this translatable seems to be: is_confirmed= alert(_("There are [ ") + count + _(" ] item(s) attached to this record.") + "\n" + _("You must delete all items before deleting this record." By splitting it up into several part the sentence is very hard to translate. Also small pieces like "Delete" or "There are" are difficult, because you might want to use different words for it in your translation. It would be better if we can make the translation script deal with those strings and make it put in placeholders. So you would end up with: is_confirmed= alert(_('There are [ '+ count +' ] item(s) attached to this record \n You must delete all items before deleting this record.')); Output in po-file: There are [ %s ] item(s) attached to this record. ... I think this is a bug now, because those alerts don't get translated at all. Splitting them up is one solution, but fixing the translation scripts would be much better. -- 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 6

[Bug 5145] New: Call number in XSLT availability information
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5145 Summary: Call number in XSLT availability information Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2537 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2537 screenshot of result list and availability display The availability information in OPAC's XSLT result list shows the call number only for available items. If the item is checked out, no call number is shown. Our libraries are irritated by that and asked to always show the call number. Another of our libraries has the problem, that the call number shown in availability does not match all their items. To make it worse Koha normally shows the call number of the item that is not for loan in the result list. And the items are located at different locations in the building. So it would be a good enhancement if showing the call number in the result list would be optional and controlled by a sys pref. -- 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 1

[Bug 7335] New: Allow custom parameters for sorting in sql reports
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7335 Bug #: 7335 Summary: Allow custom parameters for sorting in sql reports Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: ian.walls(a)bywatersolutions.com I was trying to find a solution to make it possible to select how a report is sorted before running it. Perhaps we could have a table sorter on tables generated by reports? I tried using the placeholders to provide a pull down with search options, but this didn't work. The replaced text is always in quotes, so the generated sql will not work: select concat(surname, ", ", firstname) as Name, cardnumber from borrowers order by 'cardnumber desc' -- 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 1

[Bug 5181] New: Add js to convert units when units are changed on label or card template form
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5181 Summary: Add js to convert units when units are changed on label or card template form Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This enhancement would add some js to automatically convert existing unit field values to the new unit selected from the Units drop-down. -- 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 1

[Bug 5938] New: Maximum number of issues across a family group
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5938 Bug #: 5938 Summary: Maximum number of issues across a family group Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: ruth(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com It has been suggested that there be a system-level setting for maxissueqty across a family "group", that is, all persons linked together by responsibility settings in the borrower record. For instance, if the system default maxissueqty for a branch is 25 items, and no other values are set, then a parent with two children could theoretically enter the library and borrower 75 items, by having the children check out 25 each. It may be desirable to set child-type patrons for a lower number, but even then, large families could check out a dramatic number of items; a system-level maximum on the entire family group would be nice to have. -- 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 6122] New: Catalogue reports exclude biblio without item
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6122 Bug #: 6122 Summary: Catalogue reports exclude biblio without item Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: sophie.meynieux(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Built in report on catalog uses an inner join in request, so biblios without items are not counted in the result, which is wrong -- 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 6859] New: autoMemberNum doesn't automatically fill fields
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6859 Bug #: 6859 Summary: autoMemberNum doesn't automatically fill fields Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: swgamer53(a)yahoo.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com In koha 3.4, autoMemberNum is set to "do," but it doesn't fill any of the card number fields for patrons. It worked previously until I updated to 3.4. -- 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 1

[Bug 5387] New: Support for NISO CORE: Cost of Resource Exchange Protocol
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '14

25 Apr '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5387 Summary: Support for NISO CORE: Cost of Resource Exchange Protocol Change sponsored?: Seeking cosponsors Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P3 Component: Acquisitions AssignedTo: mjr(a)ttllp.co.uk ReportedBy: mjr(a)ttllp.co.uk QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 http://wiki.koha-community.org/wiki/NISO_CORE_protocol CORE: Cost of Resource Exchange Protocol (NISO RP-10-2010) defines an XML schema to facilitate the exchange of financial information related to the acquisition of library resources between systems, such as from Koha to an Enterprise Resource Management System. MJR of software.coop is interested in implementing this. Good idea or not? Is anyone interested in funding it? Koha users would like to connect to: * MYOB - mind your own business In general, anyone interested in implementing the CORE Recommended Practice, joining the standing committee, or in receiving additional information should contact NISO at nisohq(a)niso.org. -- 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 1