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

[Bug 8042] New: Batch numbers aren't committed as used until an item is added
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8042 Priority: P5 - low Change sponsored?: --- Bug ID: 8042 Assignee: cnighswonger(a)foundations.edu Summary: Batch numbers aren't committed as used until an item is added Severity: normal Classification: Unclassified OS: All Reporter: shawn(a)pennmanor.net Hardware: All Status: NEW Version: rel_3_8 Component: Label printing Product: Koha We ran into an issue where 2 branches decided to create a label batch around the same time. Both had the blank batch screen up and they were the same batch number. We have found that the batch isn't actually committed as being used until the first item is added. In this case we had 2 branches adding items to the same batch number. This can be duplicated by creating a new batch in 2 separate browsers. If party 2 refreshes the screen after party 1 enters an item to the batch they are presented with a new batch but if they don't refresh (which most wouldn't) then both parties are editing the same batch. We have tested it in 3.6 and 3.8. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 5169] New: name/rename label batches
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5169 Summary: name/rename label batches Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Label printing AssignedTo: cnighswonger(a)foundations.edu ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 It would be very helpful if there was a way to name and rename batches of labels. Right now they're named in numerical order which can be confusing if you have a lot of batches. -- 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 5686] New: search in tamil
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5686 Summary: search in tamil Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: novamcccharles(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 i m using koha 3.00.06. Tamil search should be enabled for title search So kindly help be in solving this bug -- 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 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 7972] New: GUI for Crons
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972 Priority: P5 - low Change sponsored?: --- Bug ID: 7972 CC: gmcharlt(a)gmail.com Assignee: paul.poulain(a)biblibre.com Summary: GUI for Crons QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: System Administration Product: Koha It would be awesome if in the Admin area there was a way to turn on/off cron jobs and set the timing on them. I've seen GUIs like this before so I know it can be done, just not what it would take to do it. Obviously such a feature would be a permission associated with it so that not everyone could go in and screw with things. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7884] New: Ergonomics & usability omnibus
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '14

02 Nov '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7884 Priority: P5 - low Change sponsored?: --- Bug ID: 7884 Assignee: oleonard(a)myacpl.org Summary: Ergonomics & usability omnibus QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: katrin.fischer(a)bsz-bw.de Hardware: All Status: NEW Version: master Component: Templates Product: Koha This bug links to several related bugs for bigger projects related to ergonomy and usability. -- You are receiving this mail because: You are watching all bug changes.

1 6