March 2012 - Koha-bugs - lists.koha-community.org

[Bug 6382] New: Automatic Status Changing on Check In
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6382 Bug #: 6382 Summary: Automatic Status Changing on Check In Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Submitted on behalf of Henry Bankhead in search of feedback: We are used to being able to change at items "status" w/ horizon by just checking it in. Think of the not for loan status for example. So, if it was in mending or workroom and was checked in it would become available. Also if it was in receives status, it would move to cataloging and then to in if you checked it in twice. Originally I though Koha did this because the not for loan "status"s have numerical values. So I assumed they would move from -1, to -1, to zero (available) but evidently this is not the case. Can you see that this would be highly desirable from a workflow standpoint? What would it take to make Koha do this? -- 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 6873] New: Incremental fine system
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6873 Bug #: 6873 Summary: Incremental fine system Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: vimal0212(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Provision for incremental fine is needed in Circulation and Fine Rules. For example, for first 10 days charge $1 per day, from 11th day charge should be $2. Many libraries follows this system. -- 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 6173] New: Cronjob to send account expiry notices
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6173 Bug #: 6173 Summary: Cronjob to send account expiry notices Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: kmkale(a)anantcorp.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 3897 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3897 cronjob file This is a cronjob hacked from advanced_notices.pl to send out emails to patrons nearing account expiry. The notice template code is hardcoded to EXP so make sure you modify only that notice template. and it can handle borrowers.borrowernumber, borrowers.title, borrowers.firstname, borrowers.surname, borrowers.dateexpiry fields in the notice. The number of days to expiry can be set with a command line switch -m The script puts the emails in Koha's default message queue so its system compatible. It can be improved in a number of ways like for create syspref for sending these reminders, and setting the days in advance. I can submit a patch if this is useful.. -- 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 7655] New: Allow for an "optional" field tag, versus the need for %
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7655 Priority: P5 - low Change sponsored?: --- Bug ID: 7655 Assignee: gmcharlt(a)gmail.com Summary: Allow for an "optional" field tag, versus the need for % QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: ssammons(a)npelem.com Hardware: All Status: NEW Version: rel_3_6 Component: Reports Product: Koha Add a second field tag (placeholder / runtime argument) similar to <<>>, but it would user a logical check for no value and would either omit the argument (harder would require something like a regex removal) or put in the "%" for the end user. I was thinking something like <{}>, <[]>, <()>. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7832] New: Server Z39.50 for Unimarc
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7832 Priority: P5 - low Change sponsored?: --- Bug ID: 7832 Assignee: gmcharlt(a)gmail.com Summary: Server Z39.50 for Unimarc QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: dubyk(a)library.lviv.ua Hardware: All Status: NEW Version: unspecified Component: Z39.50 / SRU / OpenSearch Servers Product: Koha I try to setup Z39-50 server for our library with Unimarc-records. But in result was broken a normal search. Step by step: 1) Used links as guide: * [Koha-patches] [PATCH] Bug #3087 - Improve z39.50 server Unimarc support (http://lists.koha-community.org/pipermail/koha-patches/2009-April/008573.ht…) * how to use z39.50 ? (http://koha.1045719.n5.nabble.com/how-to-use-z39-50-td3057672.html) * [Zebralist] Problems with Koha/Zebra as Z39.50 server (http://lists.indexdata.dk/pipermail/zebralist/2009-March/002138.html) * Troubleshooting Koha as a Z39.50 server (http://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_server) 2) In /etc/koha/koha-conf.xml uncomment <listen id="publicserver" >tcp:@:9998</listen> and <server id="publicserver" listenref="publicserver">. ... </server> and <serverinfo id="publicserver"> ... </serverinfo> 3) Also in file /etc/koha/koha-conf.xml replace usmarc -> unimarc 4) Create /etc/koha/zebradb/etc/unimarc.mar with content: name unimarc reference Unimarc 5) Replace in /etc/koha/zebradb/marc_defs/unimarc/biblios/record.abs as follows: name unimarc ... marc unimarc.mar 6) /etc/init.d/koha-zebra-demon restart 7) yaz-client -c /etc/koha/zebradb/ccl.properties localhost:9998/biblios Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Zebra Information Server/GFS/YAZ Version: 4.0.11 e8ca42e680c5e5a644481e5d0b75a0e57c6d3e92 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Elapsed: 0.001831 7) Look: http://koha.tntu.edu.ua:9998/biblios 8) Try to test with http://www.loc.gov/z3950/test.html (Enter Term 1: .... [Any]) If port 9998 opened in firewall, we will see something: Search Results 924 records matched your query [2005]. 9) But in OPAC we have Error: Can't call method "raw" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 460. on any search. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 7534] New: OPACAllowUserToChooseBranch and hold rules
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7534 Bug #: 7534 Summary: OPACAllowUserToChooseBranch and hold rules Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: stephane.delaye(a)biblibre.com QAContact: koha.sekjal(a)gmail.com the system preference OPACAllowUserToChooseBranch disaply all the branchs instead of display only the branchs who accept the holds. Result: a branch can be pickup location when he does not want to manage holds -- 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 4

[Bug 6262] New: overdues warning label
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6262 Bug #: 6262 Summary: overdues warning label Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: cgi-bin/koha/circ/circulation-home.pl OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org I would like to see the 'warning' on the circulation home page next to the overdues report removed. We have a preference to make this not an issue and I think it's the role of the help files and manual to warn the user about this - right now having it where it is makes it look like Koha doesn't work efficiently. I'm up for other suggestions on how to improve this, but the way it is now looks bad to me (design wise and for Koha in general). -- 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 5934] New: Manipulate titles in Borrower Preferences
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5934 Bug #: 5934 Summary: Manipulate titles in Borrower Preferences Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: peter.lorimer(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com A feature to allow librarians to crate title lists based on preferences and previous choices. This is targeted towards libraries essentially catering for the blind or partially sited where books are predominantly poseted out to the borrower. -- 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 5385] New: Correct POD errors as highlighted by podchecker
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5385 Summary: Correct POD errors as highlighted by podchecker Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Developer documentation AssignedTo: gmcharlt(a)gmail.com ReportedBy: andrew.elwell(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Ideally we'd have good accurate POD within the code for all functions, however as a starting point I made a list of all errors that 'podchecker' throws up (find . -type f | grep -v \.git/ | egrep -i '\.p[lm]$' | xargs podchecker 2>/tmp/pod.err) and started to correct them Many of these are trivial syntax / whitespace issues -- 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 6

[Bug 6197] New: Capitalized or lowercased Turkish characters are not searchable
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6197 Bug #: 6197 Summary: Capitalized or lowercased Turkish characters are not searchable Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: akif-antispam(a)dinc.org QAContact: koha-bugs(a)lists.koha-community.org When searching for Titles or Authors that contain Turkish characters, they are not found if search pattern has the opposed case. For example if the author is "Nefes Zade İbrahim" and the search pattern is "ibrahim" than the result is empty. If the search is "İbrahim" than the record matches and search delivers the good results. The characters that are forcing this problem are "ğĞ, ıI, iİ, şŞ". -- 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