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

[Bug 10819] New: Allow for auto filling of holds when items are checked in via SCO
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '15

24 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10819 Bug ID: 10819 Summary: Allow for auto filling of holds when items are checked in via SCO Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: cnighswonger(a)foundations.edu QA Contact: testopia(a)bugs.koha-community.org When an item with a hold on it is checked in via the SCO module (web), no further processing is done which results in the hold being overlooked unless the circulation desk workflow includes a regular run of the hold reports. The least fix for this would be to add a system pref allowing for the option of auto-filling the highest priority hold on an item checked in via the SCO module. Perhaps other options allowing for various alternate workflows might be added here as well. I'm listing this as an enhancement because depending on one's workflow, this may not be a bug. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8950] New: Patron Card Creator_Background Image and barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '15

23 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8950 Priority: P5 - low Change sponsored?: --- Bug ID: 8950 Assignee: gmcharlt(a)gmail.com Summary: Patron Card Creator_Background Image and barcode Severity: enhancement Classification: Unclassified OS: All Reporter: sophina0516(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Tools Product: Koha Our patron card design has a background image, which is the same size as the plastic card, (2" height * 3.25" width).If we prefer to locate the barcode at the front of the card, the barcode will be covered by the background image. Just wondering that ----Is there a way that we can bring the barcode to front of the background image? http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=patroncards/creat… -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 8190] New: Koha does not have a logging module
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190 Priority: P5 - low Change sponsored?: --- Bug ID: 8190 Assignee: gmcharlt(a)gmail.com Summary: Koha does not have a logging module Severity: enhancement Classification: Unclassified OS: All Reporter: jonathan.druart(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Architecture, internals, and plumbing Product: Koha I would be great to specify a log level (to differentiate production and development environment for example). -- You are receiving this mail because: You are watching all bug changes.

1 144

[Bug 10998] New: code duplication introduced by Z39.50 authority search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10998 Bug ID: 10998 Summary: code duplication introduced by Z39.50 authority search 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 10096, which introduces a feature to import authority records via Z39.50, also introduces some code duplication. To summarize the differences: - z3950_search.pl and z3950_auth_search.pl differ only in the input search attributes they accept - C4::Breeding::ImportBreeding() and C4::Breeding::ImportAuth() do mostly the same thing - the actual search logic in C4::Breeding::Z3950SearchAuth() and C4::Breeding::Z3950Search() is the same; the two routines differ only in the specific Z39.50 attributes they handle and in some details of post-retrieval record processing. Also, Z3950SearchAuth() does not reflect the work that was done for bug 10462. Consequently, there is plenty of opportunity for code consolidation, as well as adding unit tests. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8582] New: NULL issuedates with offline circ
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8582 Priority: P5 - low Change sponsored?: --- Bug ID: 8582 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: NULL issuedates with offline circ Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha We don't think offline circ works quite right with 3.8. It may be a date vs. datetime problem, perhaps? After processing offline circ files in 3.8, we have seen some NULL issues.issuedate. We discovered these after seeing the following error occur when going to the check-out screen. Software error: Can't call method "strftime" on an undefined value at /home/koha/kohaclone/Koha/DateUtils.pm line 117 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 7372] New: RoadTypes should be folded into Authorised Values
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7372 Bug #: 7372 Summary: RoadTypes should be folded into Authorised Values Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: jonathan.druart(a)biblibre.com The current data structure for Road Types is essentially the same as for Authorised Values, but it gets it's own admin page and database table. In an effort to simply both the Koha data structure, and the admin main page, I suggest moving this into Authorised Values. This development is marked as "(OUEST-PROVENCE)". Is there a reason for the separate table and admin page that I don't understand, (not being in a European library)? -- 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 29

[Bug 10866] New: Books entered in malayalam language cannot to search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10866 Bug ID: 10866 Summary: Books entered in malayalam language cannot to search Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: sameer(a)kvasu.ac.in QA Contact: testopia(a)bugs.koha-community.org Sir, Prior to install 3.12, i was using 3.2 and i could search the terms in malayalam language. Now in 3.12 I cannot search the titles in malayalam, but it is ok in English. is there any solution -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 9006] New: autoload in C4::Context is a bad idea
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9006 Priority: P5 - low Change sponsored?: --- Bug ID: 9006 Assignee: gmcharlt(a)gmail.com Summary: autoload in C4::Context is a bad idea Severity: minor Classification: Unclassified OS: All Reporter: jcamins(a)cpbibliography.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha The comment in C4/Context.pm pretty much sums it up: # AUTOLOAD # This implements C4::Config->foo, and simply returns # C4::Context->config("foo"), as described in the documentation for # &config, above. # FIXME - Perhaps this should be extended to check &config first, and # then &preference if that fails. OTOH, AUTOLOAD could lead to crappy # code, so it'd probably be best to delete it altogether so as not to # encourage people to use it. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 9164] New: Only allow kohaadmin login under special conditions
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9164 Bug ID: 9164 Summary: Only allow kohaadmin login under special conditions Classification: Unclassified 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: m.de.rooy(a)rijksmuseum.nl Would it be an idea to separate the Koha password of kohaadmin [or whatever you name it during installation] from the database password (in terms of security)? Furthermore, is it necessary that kohaadmin can login via opac? And even, could we disable staff client login via kohaadmin under normal circumstances, only allowing login under special conditions (installer, maintenance mode, or so). We could define these conditions and provide a way for system administrators to "force these conditions" without compromising security again. Will ask for some ideas in this regard on the dev list. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 9422] New: Patron picture uploader ignores patronimages syspref
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '15

20 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9422 Bug ID: 9422 Summary: Patron picture uploader ignores patronimages syspref Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: jcamins(a)cpbibliography.com Although the patronimages syspref says it sets whether or not patron images can be uploaded, in fact all it does is toggle display. The uploader should probably not be available when the feature is disabled, to prevent librarians from getting frustrated when it seems not to work. -- You are receiving this mail because: You are watching all bug changes.

1 1