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

[Bug 7843] New: RSS for OPAC news
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '15

17 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7843 Priority: P5 - low Change sponsored?: --- Bug ID: 7843 Assignee: oleonard(a)myacpl.org Summary: RSS for OPAC news QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: magnus(a)enger.priv.no Hardware: All Status: NEW Version: master Component: OPAC Product: Koha We have news items in the OPAC - why not create an RSS stream for them? -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 9394] New: Use reserve_id where possible
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9394 Bug ID: 9394 Summary: Use reserve_id where possible Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com CC: gmcharlt(a)gmail.com This patch switches from using a combination of biblionumber/borrowernumber to using reserve_id where possible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 8835] New: Two indexes on biblioitems.issn
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8835 Priority: P5 - low Change sponsored?: --- Bug ID: 8835 Assignee: gmcharlt(a)gmail.com Summary: Two indexes on biblioitems.issn Severity: minor Classification: Unclassified OS: All Reporter: fridolyn.somers(a)biblibre.com Hardware: All Status: NEW Version: master Component: Database Product: Koha In update database script : 3.01.00.006 adds an index called 'issn' on biblioitems.issn. 3.01.00.093 also adds an index on biblioitems.issn, called 'issn_idx'. In kohastructure, only 'issn' index exists for biblioitems. So udpate 3.01.00.093 is useless. Can it be removed ? -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10906] New: Reimported records into Koha are imported only as DEFAULT frameworks, not what they were originally
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10906 Bug ID: 10906 Summary: Reimported records into Koha are imported only as DEFAULT frameworks, not what they were originally Change sponsored?: --- Product: Koha Version: 3.10 Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: ceciloh(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org Our bibliographic records have differing frameworks for the various formats. We do NOT use the default framework. We then use MarcEdit to add all those nifty RDA fields to our records. We catalog our records and then export them to MarcEdit. MarcEdit does its stuff and then we reimport the records back into Koha. This is where the problem lies. They get reimported back into Koha with the DEFAULT framework. This did NOT happen when we were on 3.8 but it is happening now in 3.10 and it looks like it also happens in 3.12. They match just fine on the control number but the framework changes. This adds much time and steps to our cataloging process. Is this a bug or an enhancement request? I've been informed that this is how it is supposed to work. Cecil Hillyard Washoe County Library Reno, Nevada -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 8369] New: default_branch_circ_rule and default_circ_rules tables useless
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8369 Priority: P5 - low Change sponsored?: --- Bug ID: 8369 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Blocks: 8362 Summary: default_branch_circ_rule and default_circ_rules tables useless Severity: normal Classification: Unclassified OS: All Reporter: paul.poulain(a)biblibre.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha Issuingrules uses '*' as a wildcard to say "default". The branch_borrower_circ_rules and default_branch_circ_rules could use the same method to define the default behaviour. It means the tables default_branch_circ_rule and default_circ_rules would become useless and the behaviour more consistent -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 7684] New: inventory : datatable fix actions etc.
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7684 Priority: P5 - low Change sponsored?: --- Bug ID: 7684 Assignee: gmcharlt(a)gmail.com Summary: inventory : datatable fix actions etc. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: stephane.delaye(a)biblibre.com Hardware: All Status: NEW Version: rel_3_8 Component: Tools Product: Koha Check that the inventory tool operates in the mode explained below. The Inventory Tool can create a report after each load of barcodes. Reports back the "mistakes" as follows: * The poorly-sorted copies: copies read through inventory then they should not have to be read as "out of scope" of the inventory. Example: a copy with a item call number 400 was loaded while the inventory concerned the copies with a item call number range 500 ↔ 600. * To modify the copies: copies read through inventory then they should not have to be read because they are status (notforloan): "In Control", "Lost" ... etc.. Or because they were borrowed. When the last load of barcode inventory, the final report states an additional anomaly: * Missing items to the inventory: the items that should have been read and which are missing inside files that were loaded. Then the library to check the shelves if the copies are actually missing. If this happens, the library change the item status in "Missing inventory". The steps to understand the tools : Step 1: Read barcodes with a shower without file that stores the bar code in a file of type txt. Step 2: Load the file listing the barcodes of copies. Indicate : branch, location and item call number of the items inside the file. Field "Items Statuses" check only the status that will be read during the inventory At the bottom , in the second field named "Inventory Date" enter the current date only in two cases: (1) the file to be processed is the only file on the inventory of a location / slice dimensions, (2) the file to be processed is not the last file to load (you have cut inventory into multiple files). When loading the last file "Inventory Date" you indicate the date of loading the first file that was loaded (start date of the inventory) Check marked 'Skip copies on loan': don't report books borrowed missing inventory. Check the words 'Export CSV' if you want to save the report of the inventory in a spreadsheet. Notes : exported in the csv file labels codes and not codes only. Check 'Compare barcodes list to results' only when loading the last file in the inventory. Option to control during the "closing" of the inventory if there are copies missing from the inventory. Step 3: Final Report of the inventory when loading the copies are modified : the field 'view for the last time' (items.datelastseen) retrieves the current date / time of loading. Step 4: Go check the shelves documents marked as "missing" and / or poorly-sorted. Updated code "state" of copies. Warning :When reports displaying the results data in many screens, check the paging the results to see the all the screens results -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 10591] New: Why do we allow holds on restricted items (952$5=Use restrictions)? Place a hold for reference?
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '15

16 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10591 Bug ID: 10591 Summary: Why do we allow holds on restricted items (952$5=Use restrictions)? Place a hold for reference? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, it is possible to place a hold on an item marked as Restricted with 952 $5. And you can also confirm the hold, setting it to Waiting status. The code in Circulation.pm (CanBookBeIssued) checks before issuing if an item is restricted and will not permit checkout. So actually, the book is not for loan. It may be available for reference in the library? This may be just unintentional. But if we would have the intention to provide a mechanism to place holds for reference in the library, we probably should deal with the remaining workflow too. How do we registrate that the user received the book for reference, and when do we remove the waiting hold? Do we count these kind of references? Note also that we could have a library building workflow on this possibility, and another developer that some day makes it impossible to reserve restricted items not knowing that. What do you think? Setting this report to In Discussion, hoping for some more feedback. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 10874] New: Incremental fine system for various types of documents and patron categories
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '15

15 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10874 Bug ID: 10874 Summary: Incremental fine system for various types of documents and patron categories Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: library.ltce(a)ltjss.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 6873 (16 Sept 2011) is similar but not resolved till date. our library use this rules for fines and circulation: Circulation periods: books period: 30 days with 2 renewals max journals period: 14 days with 2 renewals max Fines: 1. fine after period, price A 2. fine 30th day after 1. fine, price B 3. fine 14th day after 2. fine, price C (2x price B) 4. fine 14th day after 3. fine, price D (3x price B) 5. next fines we count per day and item. Fine rates varies for patron categories as well as type of documnet. also bug 8776 and 10027 need to be solved as they are related to fine calculation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 8685] New: Inventory tool fails in timeout with large CB files
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '15

12 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8685 Priority: P5 - low Change sponsored?: --- Bug ID: 8685 Assignee: gmcharlt(a)gmail.com Summary: Inventory tool fails in timeout with large CB files Severity: normal Classification: Unclassified OS: All Reporter: sophie.meynieux(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Tools Product: Koha Inventory tool fails with a timeout if the CB file to process is too large. In fact it doesn't really fails, CB are properly processed, but the user can't see the result because of the timeout occuring before the end of processing. One solution could be to implement background job like in MARC import (BZ1531) Another one could be to add scheduler to plan inventory process like in reports -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 9314] New: Messaging preferences not updated to category defaults on patron edit
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '15

12 Jun '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9314 Bug ID: 9314 Summary: Messaging preferences not updated to category defaults on patron edit Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: rolando.isidoro(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the patron edit form, under the "Patron messaging preferences" there's a message stating: "If no preferences are selected, the default preferences for the category chosen will be applied on save, otherwise your selection here is saved" When no preferences are selected the default preferences for the chose category are not being applied on save. As an enhancement a button could be added to reset the messaging preferences to default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16