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

[Bug 8661] New: break out additional authors in opac like in staff
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8661 Priority: P5 - low Change sponsored?: --- Bug ID: 8661 Assignee: oleonard(a)myacpl.org Summary: break out additional authors in opac like in staff Severity: minor Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: OPAC Product: Koha Created attachment 11718 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=11718&action=edit staff display When XSLT is on the additional authors show next to 'by' on the OPAC and next to 'additional authors' in the staff client. They should be next to 'additional authors' in the OPAC as well. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 10518] New: Relevance option for non-Latin scripts
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10518 Bug ID: 10518 Summary: Relevance option for non-Latin scripts Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: tigran(a)flib.sci.am In Koha system (versions 3.08, 3.10, 3.12) for multi script records (e.g. titles are in Latin, in Cyrillic, in Armenian)after search, when from relevance drop down menu selecting 'Title (A-Z)' the display for non-Latin records is not in correct order. If for Latin records they are displayed in correct alphabetical order, Armenian and Cyrillic records are mixed, between the records with Armenian titles starting with the letter 'A' you can see records for which the title is starting with the letters 'M', 'H', then again 'A', then Cyrillic records are coming, and after those again records with Armenian letters. Is this a Zebra problem? Any ideas? thanks Tigran -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 10397] New: link_bibs_to_authorities.pl fails when gets to bibs linked to deleted authority records
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10397 Bug ID: 10397 Summary: link_bibs_to_authorities.pl fails when gets to bibs linked to deleted authority records Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: danielle(a)bywatersolutions.com CC: m.de.rooy(a)rijksmuseum.nl When running the link_bibs_to_authorities.pl script it fails when it encounters bibs linked to deleted authorities in subfield $9. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 7694] New: Syndetics_Editons not included
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7694 Priority: P5 - low Change sponsored?: --- Bug ID: 7694 Assignee: oleonard(a)myacpl.org Summary: Syndetics_Editons not included QA Contact: koha.sekjal(a)gmail.com Severity: minor Classification: Unclassified OS: All Reporter: ago(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_6 Component: OPAC Product: Koha Syndetics Editions is not included in blib/OPAC_CGI_DIR/opac/opac-detail.pl or opac/opac-detail.pl. get_syndetics_editions missing from use C4::External::Syndetics and my $syndetics_elements; Editions routine missing. C4::External::Syndetics is prepared for Editions -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 12857] New: Syndetics index apreciably slow page load for items without result at Syndetics
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12857 Bug ID: 12857 Summary: Syndetics index apreciably slow page load for items without result at Syndetics Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: nengard(a)gmail.com Depends on: 12420 get_syndetics_index is missing the error handling code that is present in the other routines. Thereofre, if an idnex is not found for the particular item, then XML::Simple attempts to parse the large html document that is returned. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8016] New: Items are not tie to the transaction using "global" action.
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8016 Priority: P5 - low Change sponsored?: --- Bug ID: 8016 CC: gmcharlt(a)gmail.com Assignee: kyle.m.hall(a)gmail.com Summary: Items are not tie to the transaction using "global" action. QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: anthony.laquerre(a)ccsr.qc.ca Hardware: All Status: NEW Version: rel_3_6 Component: Circulation Product: Koha Created attachment 9315 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=9315&action=edit Payments Selection Hi, We have a problem with how the process of paying fine is currently done. Look at the 2 images. In the Pay fines page. There is currently a difference between buttons Group 1 : ("Pay" + "Writeoff") Group 2 : ("Pay amount","Write off all", "Pay selected") Group 1 is done on the specific item level. Group 2 is done globally using a logic to pay the oldest fine. ( That's my understanding ... :-)) If you look at image : Payments.png, you will see the difference. The payment for 10$ is done using "Pay selected". The payment for 5$ is done using "Pay". This scenario is valid for all buttons from group 1 and group 2. The problem is really the link to the item that is currently lost when using buttons from Group 2. Staff find it really hard to talk about their account because of that. It's impossible to know what the 10$ really apply to. This is a simple example, but sometime patron will return 5 books with 5$ fines for each. You will do "Pay Selected" (group 2) the 25$ will be applied but you will never be able to know what it was apply exactly. Is it possible to still link the item to the transaction using button from Group 2 ? Let me know if you need more infos. Thanks, Anthony -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7525] New: some database fields are displayed 'as is' when they are linked to autorised values
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7525 Bug #: 7525 Summary: some database fields are displayed 'as is' when they are linked to autorised values Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: koha.sekjal(a)gmail.com We have to reuse item fields in ways they were not intended to quite often in order to respond to libraries specific demands. In some cases we will control these fields with an authorized value, but not all fields will display the authorized value description on the opac and admin interface. See: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7379 Which took care of this problem for the copynumber field. -- 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 7705] New: IE postdata issue - expiring sessions when back button is used
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7705 Priority: P5 - low Change sponsored?: --- Bug ID: 7705 Assignee: oleonard(a)myacpl.org Summary: IE postdata issue - expiring sessions when back button is used QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: shelley.gurney(a)nzica.com Hardware: All Status: NEW Version: rel_3_6 Component: OPAC Product: Koha The majority of our users are still using IE and navigate via the browser buttons. This is causing some issues with their sessions expiring when they navigate forwards and backwards several times. Is there a fix for this in Koha, to stop this from happening? Can we trick IE into not cancelling the session. (not an apparent issue in Chrome or Firefox) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7224] New: Allow patrons to pick their own preferred language
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7224 Bug #: 7224 Summary: Allow patrons to pick their own preferred language Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com Depends on: 6481 Allow patrons to select their own preferred language, individually. This can provide an extra level of personalization in multi-lingual environments, and could later be applied to more than just the OPAC or staff client templates (translated notices). The choice should be configurable in the OPAC, under Preferences, without the need to confirm with the librarian (like for contact info changes) The structural changes to Koha required for this development would pave the way for a whole bunch of other individual preference values (beyond just messaging and OPAC privacy preferences), making for more customizable ILS -- 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 1

[Bug 7343] New: search tag usability in MARC framework
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '15

07 Jan '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7343 Bug #: 7343 Summary: search tag usability in MARC framework Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com After searching for a tag in a marc framework, the list of tags is shown starting with the tag we are looking for, but pages prior to the match are not shown at all, leaving users under the impression that these tags have disappeared. My take on this is that we should either make it work as a filter and only display the match, it would then be clear for the user that he has to empty the search field in order to view the complete list of tags. Or make it work as a simple search that would take us on the page of the match (and maybe highlight the result) but without discarding the previous pages. The behaviour is the same when editing subfields: if the user uses the pagination to go edit the subfields for 995 and then clicks on the name of the framework in the breadcrumb, the page shown is the result page for a search on 995, which hides all the previous pages. This is even more problematic as the user hasn't used the searched box at this point. (In that case i think the link should take the user on the first page of the framework, which is consistent with what is written on the link he has clicked: the name of the framework.) This is the behaviour in 3.6, 3.4 and 3.2. -- 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 1