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

[Bug 8380] New: Can not set indicators to required
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8380 Priority: P5 - low Change sponsored?: --- Bug ID: 8380 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: Can not set indicators to required Severity: enhancement Classification: Unclassified OS: All Reporter: steven_jeffery(a)fmi.com Hardware: All Status: NEW Version: rel_3_8 Component: Cataloging Product: Koha It is not currently possible to set the two indicators used throughout MARC to required. An example of where this could be extremely useful would be the two indicators for the 245 field. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7149] New: authorized values for indicators don't work
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7149 Bug #: 7149 Summary: authorized values for indicators don't work Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal 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 In the frameworks if you click 'edit' to the right of a tag (not a subfield) the last option says "(if you select a value here, the indicators will be limited to the authorized value list)" but they don't seem to work. I tried this and the indicators were still just text boxes, not pull downs. Did this ever work? If so, is there a trick? Or is this just a 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 8457] New: No results found on term/phrase click in scan index results list .
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8457 Priority: P5 - low Change sponsored?: --- Bug ID: 8457 Assignee: gmcharlt(a)gmail.com Summary: No results found on term/phrase click in scan index results list . Severity: major Classification: Unclassified OS: Linux Reporter: hend.eleraky(a)bibalex.org Hardware: All Status: NEW Version: rel_3_6 Component: Searching Product: Koha When i try to click on any any term/phrase in scan index results list i get "No results found " but this happens only when " QueryAutoTruncate " preference is set to "only if * is added" . If this preference is set to "automatically" i could get results . Koha version 3.6.5 -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 8591] New: show sum of any outstanding fines for patron on the issue slip
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8591 Priority: P5 - low Change sponsored?: --- Bug ID: 8591 Assignee: koha-bugs(a)lists.koha-community.org Summary: show sum of any outstanding fines for patron on the issue slip Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_8 Component: Notices Product: Koha We would like to show a sum of any outstanding fines for a particular patron at the bottom of the issue slip. Would this require adding some fields from the accountlines table as available fields to be used in a notice? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 6946] New: Import Batches _update_batch_record_counts has inefficient SQL
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6946 Bug #: 6946 Summary: Import Batches _update_batch_record_counts has inefficient SQL Classification: Unclassified Change sponsored?: --- Product: Koha Version: Rel_3_8 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org The queries to update the number of biblios and the number of items for any given import batch are much slower than they need to be. UPDATE import_batches SET num_biblios = (SELECT COUNT(*) FROM import_records WHERE import_batch_id = import_batches.import_batch_id AND record_type = 'biblio') WHERE import_batch_id = ? UPDATE import_batches SET num_items = (SELECT COUNT(*) FROM import_records JOIN import_items USING (import_record_id) WHERE import_batch_id = import_batches.import_batch_id AND record_type = 'biblio') WHERE import_batch_id = ?") The "AND record_type = 'biblio'" lines are unnecesary; every record within the same import_batch_id will have the same record_type, and more importantly, 'biblio' is currently the only supported type. Removing the line changes the return time of the subquery from over 2 seconds down to 0.01 seconds (on my machine with 34944 items in a batch). I think this is going to be faster than adding an index on record_type. -- 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 6563] New: Default OPAC language not set properly
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6563 Bug #: 6563 Summary: Default OPAC language not set properly Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: I18N/L10N AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org For libraries with multiple installed and enabled OPAC languages, the first enabled language in the list of activated languages is selected as default, not the primary language for the installation. To reproduce: 1. Install multiple OPAC languages 2. Active one that is 'higher' on the list than your native install language 3. Go to the OPAC, and see that that language, not your native language, displays Root of the problem: Line 57 of opac/opac-main.pl references "opac-main.tmpl", which no longer exists since the conversion to Template::Toolkit. Changing this to opac-main.tt fixes the issue. Patch forthcoming. -- 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 13

[Bug 6416] New: koha-remove fails when dropping user
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6416 Bug #: 6416 Summary: koha-remove fails when dropping user Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org I have MySQL running on the same machine as Apache/Koha, and have created a new library with "sudo koha-create --create-db demo". When i do "sudo koha-remove demo" I get this: Removing Koha instance demo ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_demo'@'%' When I log in to mysql as root and do this: DROP USER failed for 'koha_demo'@'%'; I get pretty much the same message. But when I replace % with localhost and do this: DROP USER failed for 'koha_demo'@'localhost'; it succeeds. -- 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 8285] New: Show OPAC suppress field (942n) for new basket items
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8285 Priority: P5 - low Change sponsored?: --- Bug ID: 8285 Assignee: koha-bugs(a)lists.koha-community.org Summary: Show OPAC suppress field (942n) for new basket items Severity: enhancement Classification: Unclassified OS: All Reporter: epietrocupo.hlhl(a)ssss.gouv.qc.ca Hardware: All Status: NEW Version: rel_3_6 Component: Acquisitions Product: Koha Would it be possible to show the OPAC suppress field when adding new catalog entry for ordering documents. The problem is that we order books, for other departments, and we do not want these entries to apprear in the catalog. So if we could simply block their display with a check box right at the entry creation, that would prevent having to search and edit each new catalog entry. You could enhance this by using a different configuration for each library. Like if you orer for library A, OPAC suppress is disabled by default, but if you order for library B, OPAC suppress is enabled by default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 6798] New: Make koha-create send email with details of created site
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6798 Bug #: 6798 Summary: Make koha-create send email with details of created site Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: magnus(a)enger.priv.no ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org The packages are so awesome, it takes way longer to tell someone you set up an instance for them, than to create the actual instance. So why not make koha-create do even more of the work? I'm thinking of adding two more options: --emailto = Make koha-create send an email to the given address that contains the URLs for OPAC and intranet, username and password. This could be someone who is going to use the instance, or yourself, for future reference or forwarding to whoever needs it. --emailtemplate = point to a custom template for the email, instead of the default one. I'm thinking both of these could be set in the configfiles, as well as on the command line. If you have two different configfiles you might want to have different email templates for each of them. The one usecase I can think of for having the email in a configfile is if you want to send the details of created instances to yourself, either just as a reminder or for forwarding to whoever else needs the information. Sending the password in an email like this might be A Bad Thing, but the passwords are supposed to be temporary anyway, right? -- 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 5851] New: SIP Slips printed in wrong circumstances -- Local hold and no hold items
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '15

06 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5851 Bug #: 5851 Summary: SIP Slips printed in wrong circumstances -- Local hold and no hold items Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Here is how we would like the check-in process to work in Koha on the SIP connection: 1) a WALKIN item type should never generate a hold slip (currently does) 2) a LOCALHOLD type should only generate a hold slip if there is an unfilled hold for a local patron (currently does for any hold) 3) If a hold slip is generated for any valid circumstances... a) the item processed should be tied to the patron on the slip b) the item should be in the proper status (hold should be confirmed and put in transit if necessary) In summary, when a hold slip is generated we should be able to place the slip in the item and put it in the courier or on our hold shelf. -- 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