Bug 3386 - Authority Search All Headings doesn't work
Summary: Authority Search All Headings doesn't work
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Authority data support (show other bugs)
Version: rel_3_2
Hardware: All All
: PATCH-Sent (DO NOT USE) normal
Assignee: Frédéric Demians
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks: 3187
  Show dependency treegraph
 
Reported: 2009-07-02 04:52 UTC by Frédéric Demians
Modified: 2012-10-25 23:04 UTC (History)
4 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Authority Search Bar (38.68 KB, image/png)
2009-07-02 16:52 UTC, Chris Cormack
Details
The form in question (8.40 KB, image/png)
2010-08-11 14:33 UTC, Owen Leonard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 01:09:53 UTC

---- Reported by frederic@tamil.fr 2009-07-02 16:52:22 ----

Created an attachment
Authority Search Bar

When an authority search is done on all headings, Zebra index 1=Any is not choose, but Heading-Main. So it's not possible to find authorities on authorities related fields.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:09 UTC  ---

This bug was previously known as _bug_ 3386 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3386
Imported an attachment (id=1270)

Actual time not defined. Setting to 0.0
The original submitter of attachment 1270 [details] is unknown.
   Reassigning to the person who moved it here: chris@bigballofwax.co.nz.

Comment 2 Owen Leonard 2010-08-11 14:31:58 UTC
Making this change to HEAD doesn't fix the problem for me *unless* I move the "Anywhere" group of form fields to the *beginning* of the form. Then it works. The form uses multiple instances of form fields with the same name. I wonder if there is something wrong with the parsing of these multiple fields?
Comment 3 Owen Leonard 2010-08-11 14:33:41 UTC
Created attachment 2505 [details]
The form in question

I'm not sure why the other screenshot was attached here, it didn't depict the form discussed here. The form at issue is the one which pops up when you click the "..." link an authority record to a bibliographic record.
Comment 4 Owen Leonard 2010-08-11 14:35:31 UTC
I also notice that if I do a search with more than one field of the form filled in the script fails:

ZOOM error 20003 "can't set prefix query" (addinfo: "@or @attr 7=1 @attr 1=Heading 0  @and  @attr 1=authtype @attr 5=100 PERSO_NAME @attr 1=Heading  @attr 5=1 @attr 4=6 "leonard" @attr 1=Heading  @attr 5=1 @attr 4=6 "leonard" @attr 1=Any  @attr 5=1 @attr 4=6 "leonard"") from diag-set 'ZOOM', referer: http://localhost:8888/cgi-bin/koha/authorities/auth_finder.pl?op=do_search&type=intranet&index=tag_100_subfield_a_753522_581029&authtypecode=PERSO_NAME&marclist=mainmainentry&and_or=and&operator=contains&marclist=mainentry&and_or=and&operator=contains&marclist=Any&and_or=and&operator=contains&value_any=leonard&orderby=HeadingAsc
Comment 5 Elaine Bradtke 2010-10-14 13:21:25 UTC
We've got the candidate release of 3.2 installed 
I had the error message come up when searching for a name authority from the MARC 100 field in a catalogue record.
The message occurs when there is a subfield d in the search box.
If the subfield d is deleted from the search box, everything works fine, even if there is a subfield d in the corresponding authority record.
Comment 6 Katrin Fischer 2010-12-13 11:36:48 UTC
This problem is still existing in current HEAD with MARC21. 

A search in all headings will not bring up results. The other tabs work.
Comment 7 Chris Cormack 2010-12-14 22:47:54 UTC
This doesnt appear to have ever been pushed, does someone want to rebase and resubmit for QA
Comment 8 Frédéric Demians 2010-12-15 05:58:37 UTC
> This doesnt appear to have ever been pushed, does someone want to rebase and
> resubmit for QA

For me it works now in 3.2.x, in MARC21, without this patch...
Comment 9 Nicole C. Engard 2011-02-17 18:54:12 UTC
Marking fixed since this seems to be resolved