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

[Bug 5534] New: koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 16 May '15

16 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 Summary: koha does not ignore punctuation when searching Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When you're doing a search for a title like "Harrison's Internal Medicine" you can find it if you search for "harrison" or "harrison's" but not "harrisons" - the punctuation is required. This seems a bit odd since most search engines don't require that you enter the punctuation. -- 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 16

[Bug 4960] New: No way to enter custom purchase order number
by bugzilla-daemon＠bugs.koha-community.org 16 May '15

16 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4960 Summary: No way to enter custom purchase order number Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 There needs to be a way on order to enter a purchase order number that will then print on the PDF receipt. Most organizations do not have purchase orders that are sequential for book orders only (the library may have sequential POs for all their orders - supplies, books, etc) and the ID generated by the DB won't work for them. -- 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 5463] New: limit to available shows on hold items
by bugzilla-daemon＠bugs.koha-community.org 15 May '15

15 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5463 Summary: limit to available shows on hold items Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2796 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2796 on hold when limited to available See attached. When in the opac and limiting to available only items it shows me items that are available but also those that are on hold - which technically are 'unavailable' -- 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 4856] New: problem with NSB/NSE chars
by bugzilla-daemon＠bugs.koha-community.org 04 May '15

04 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4856 Summary: problem with NSB/NSE chars Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: nahuel.angelinetti(a)biblibre.com ReportedBy: nahuel.angelinetti(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Zebra doesn't like NSB/NSE chars, they should be deleted before indexing, only in UNIMARC because it's a french problem. -- 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 9

[Bug 4857] New: aqplan.pl: consideration of Planning categories with authorised values
by bugzilla-daemon＠bugs.koha-community.org 04 May '15

04 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4857 Summary: aqplan.pl: consideration of Planning categories with authorised values Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: alex.arnaud(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 -- 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 18

[Bug 4864] New: modules required by SIP not in module list
by bugzilla-daemon＠bugs.koha-community.org 04 May '15

04 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4864 Summary: modules required by SIP not in module list Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Installation and upgrade (command-line installer) AssignedTo: gmcharlt(a)gmail.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 SIPServer.pm requires Net::Server and UNIVERSAL::require which are not in the dependencies listing -- 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 7

[Bug 5294] New: Vendor name shows with '%20'
by bugzilla-daemon＠bugs.koha-community.org 04 May '15

04 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5294 Summary: Vendor name shows with '%20' Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 To reproduce: 1) create a new subscription 2) search for a vendor who has spaces in their name 3) choose it, and note that when its name is put into the field, it has %20 where spaces should be. -- 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 17

[Bug 5704] New: bib level item type icon should display on search results
by bugzilla-daemon＠bugs.koha-community.org 01 May '15

01 May '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5704 Summary: bib level item type icon should display on search results Change sponsored?: --- Product: Koha Version: master Platform: All 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 Depends on: 4359 Estimated Hours: 0.0 Created attachment 3079 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3079 display introduced with patch for bug 4359 I talked to Owen today (chat transcript below) about the recent changes applied by the commit for bug 4359. Basically the icon shouldn't show on the search results unless the item-level_itypes pref is off. But I think we need a new pref that does not take the item-level_itypes pref into consideration to show the bib level item type icon on the search results (if the library so chooses). --------------- Owen Leonard: But if you have item-level item types turned on (and I think most people do now?) then there is no way to choose which item type to display on the results page Owen Leonard: And mightn't libraries not be setting a biblio-level item type at all? Nicole Engard: so maybe we need two prefs Nicole Engard: you are right - they may not be setting that bib level item type Owen Leonard: Hm... They don't have some copies in reference and others which circulate? Owen Leonard: That's the big use we have of the feature Nicole Engard: i would think they would Nicole Engard: basically whatever commit this was needs to be reverted cause it has too many variables that weren't considered Nicole Engard: i just can't find the report for it Nicole Engard: i think we need multiple prefs: Owen Leonard: http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=7a945dbc284… Nicole Engard: #1 show icons on the search results (yes/no) Nicole Engard: #2 use the bib level/first item level icon for display Nicole Engard: #3 show icons on the items on the bib detail Owen Leonard: I'm going to submit another patch to make display of the item type icon contingent on having item-level_itypes off Nicole Engard: i'll add my notes after you do that - cause that's too broad a condition - if you turn them off for all items and want the icon to display on the search results if you don't have attached items you can't have that Nicole Engard: i don't know if that makes sense Owen Leonard: I think at this point there is no logical way to display icons on the search results page if you have item-level itemtypes turned on. Nicole Engard: hence my suggestions for multiple prefs Owen Leonard: Displaying the first item-level item type doesn't make sense to me, I think that would be misinformation. Nicole Engard: i agree with you!! don't get my wrong - i'm just telling you what we're being asked for Nicole Engard: i'm okay with your way - but we need a pref to use the bib level item type for search results icon display if people want Nicole Engard: and that has to be regardless of the value in the item level pref Nicole Engard: who are we to tell libraries they can't share misinformation? :) hehe Owen Leonard: Fair enough. Owen Leonard: So we need a new bug report for that enhancement Nicole Engard: i'll do that and i'll relate it to the one you're fixing -- 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 6911] New: Log viewer should remember search terms
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '15

30 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6911 Bug #: 6911 Summary: Log viewer should remember search terms Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org The log viewer's search form will go back to the default values after submit. There is no way to see what you have searched for after submitting, which is quite annoying. -- 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 23

[Bug 6007] New: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '15

30 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6007 Bug #: 6007 Summary: Checking 'Display only used Tags/Subfields' on MARC framework page results in unusable output Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/admin/marctagstructure.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 3531 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3531 Screenshot of the problematic display When looking at tags for a particular MARC framework, if you check the 'Display only used Tags/Subfields' the page automatically reloads and the table redisplays in a way that is unusable. The table columns no longer match the header and there are no longer links for editing, deleting, etc. -- 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 17