Zebra search for "lost" / "onloan" items gives up a ERROR 114
Hi yall, In continuing effort to complete an install of Koha/3.0.1 and get the OPAC search working, we've run into a snag. All query stemming, fuzzines, etc has been turned off. We can do a simple search for "drame" and see 50 results. When we refine the search to a branch, it works - smaller result set. But when we refine the search to "items available" we get nothing in the result set and zebrasrv reports an ERROR 114. Here is the query as emitted by Koha: drame and (( ( allrecords,AlwaysMatches='' not onloan,AlwaysMatches='') and (lost,st-numeric=0) )) And here is the query as interpreted by zebrasrv: ERROR 114 1 1+0 RPN @attrset Bib-1 @and drame @and @not @attr "1=_ALLRECORDS" @attr 2=103 '' @attr 1=8024 @attr 2=103 '' @attr 1=8002 @attr 4=109 @attr 2=3 0 Finally, here are the two relevant lines from record.abs: melm 952$q onloan:n,onloan:w melm 952$x lost,lost:n I am told by those in the know that the ERROR 114 refers to an unknown / unmapped MARC field. We are positive the above two fields are in the MARC. Any ideas why this query is returning an ERROR 114? TIA rickw -- _________________________________ Rick Welykochy || Praxis Services A lie can travel halfway around the world while the truth is putting on its shoes. -- Mark Twain
Hi Rick, If you donot have any lost or onloan item, then the /zebra /index wil not be created, thus the ERROR 114. Sorry for your tribulations. -- Henri-Damien LAURENT Rick Welykochy wrote:
Hi yall,
In continuing effort to complete an install of Koha/3.0.1 and get the OPAC search working, we've run into a snag.
All query stemming, fuzzines, etc has been turned off.
We can do a simple search for "drame" and see 50 results. When we refine the search to a branch, it works - smaller result set. But when we refine the search to "items available" we get nothing in the result set and zebrasrv reports an ERROR 114.
Here is the query as emitted by Koha:
drame and (( ( allrecords,AlwaysMatches='' not onloan,AlwaysMatches='') and (lost,st-numeric=0) ))
And here is the query as interpreted by zebrasrv:
ERROR 114 1 1+0 RPN @attrset Bib-1 @and drame @and @not @attr "1=_ALLRECORDS" @attr 2=103 '' @attr 1=8024 @attr 2=103 '' @attr 1=8002 @attr 4=109 @attr 2=3 0
Finally, here are the two relevant lines from record.abs:
melm 952$q onloan:n,onloan:w melm 952$x lost,lost:n
I am told by those in the know that the ERROR 114 refers to an unknown / unmapped MARC field.
We are positive the above two fields are in the MARC.
Any ideas why this query is returning an ERROR 114?
On
LAURENT Henri-Damien wrote:
If you donot have any lost or onloan item, then the /zebra /index wil not be created, thus the ERROR 114. Sorry for your tribulations.
But we do have items on loan. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services A lie can travel halfway around the world while the truth is putting on its shoes. -- Mark Twain
2009/11/16 Rick Welykochy <rick@praxis.com.au>:
LAURENT Henri-Damien wrote:
If you donot have any lost or onloan item, then the /zebra /index wil not be created, thus the ERROR 114. Sorry for your tribulations.
But we do have items on loan.
Have any marked lost? Chris
Chris Cormack wrote:
But we do have items on loan.
Have any marked lost?
I don't think so. A couple of points: (1) The query I posted is asking for items NOT on loan and items NOT lost, so it should return results. (2) ERROR 114 refers to an unknown object ID (oid), i.e. something missing in the record.abs mapping Thsu, zebrasrv is saying there is a missing OID in the following expression: @attrset Bib-1 @and drame @and @not @attr "1=_ALLRECORDS" @attr 2=103 '' @attr 1=8024 @attr 2=103 '' @attr 1=8002 @attr 4=109 @attr 2=3 0 Now, I do not know where to look for attrs 8024 and 8002 to see what they refer to in record.abs. It's got me stumped. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services A lie can travel halfway around the world while the truth is putting on its shoes. -- Mark Twain
Hi Rick, On Sun, Nov 15, 2009 at 4:58 PM, Rick Welykochy <rick@praxis.com.au> wrote:
Chris Cormack wrote:
But we do have items on loan.
Have any marked lost?
I don't think so.
A couple of points:
(1) The query I posted is asking for items NOT on loan and items NOT lost, so it should return results.
(2) ERROR 114 refers to an unknown object ID (oid), i.e. something missing in the record.abs mapping
Thsu, zebrasrv is saying there is a missing OID in the following expression:
@attrset Bib-1 @and drame @and @not @attr "1=_ALLRECORDS" @attr 2=103 '' @attr 1=8024 @attr 2=103 '' @attr 1=8002 @attr 4=109 @attr 2=3 0
Now, I do not know where to look for attrs 8024 and 8002 to see what they refer to in record.abs.
attr 8002 = lost attr 8024 = onloan per bib1.att Hope this helps. Kind Regards, Chris
2009/11/16 Rick Welykochy <rick@praxis.com.au>:
Chris Cormack wrote:
But we do have items on loan.
Have any marked lost?
I don't think so.
A couple of points:
(1) The query I posted is asking for items NOT on loan and items NOT lost, so it should return results.
(2) ERROR 114 refers to an unknown object ID (oid), i.e. something missing in the record.abs mapping
Thsu, zebrasrv is saying there is a missing OID in the following expression:
I think what Henri is saying is it needs to check those 2 indexes, and if nothing is lost then that index will not exist, hence the 114 telling you it doesn't exist. Can you try marking an item lost, rebuild the index and see if it now works. Also try issuing an item also. Chris
Chris Cormack wrote:
I think what Henri is saying is it needs to check those 2 indexes, and if nothing is lost then that index will not exist, hence the 114 telling you it doesn't exist.
Can you try marking an item lost, rebuild the index and see if it now works. Also try issuing an item also.
We now have a index with onloan items and an index with lost item (one). The search still returns no results for (and get this ...) items available. It should return results for all the books from the original query less the one or two on loan. But it goes into ERROR 114. How can ERROR 114 refer to both "OID not found" and "index not found" ? Still trying! Any insights most welcome. thanks guys, rickw -- _________________________________ Rick Welykochy || Praxis Services A lie can travel halfway around the world while the truth is putting on its shoes. -- Mark Twain
Rick Welykochy wrote:
We now have a index with onloan items and an index with lost item (one).
The search still returns no results for (and get this ...) items available. It should return results for all the books from the original query less the one or two on loan. But it goes into ERROR 114.
How can ERROR 114 refer to both "OID not found" and "index not found" ?
I have had some feedback from Mike Taylor at indexdata. He informs me that the error codes returned by zebra server are Z3950 error codes (1) which surprised me. Reference: <http://www.loc.gov/z3950/agency/defns/bib1diag.html> Our remaining conundrum concerns "lost". The only difference between this item in the Koha install that does not search correctly (i.e. ERROR 114) and another Koha install that does work is this, in record.abs: record.abs:melm 952$1 lost,lost:n record.abs:melm 952$x lost,lost:n i.e. we have changed the MARC subfield tag for "lost" Can this affect the indexing? If so, how? I have done a recursive diff between the working and non-working instances in the zebra config file are in /etc and all files are identical except the above mapping. Also, the data in the non-working instance was imported from Koha/2.2.9 so there are quite a few differences in the MARC. We have ensured that the record.abs file reflects these changes. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services A lie can travel halfway around the world while the truth is putting on its shoes. -- Mark Twain
participants (4)
-
Chris Cormack -
Chris Nighswonger -
LAURENT Henri-Damien -
Rick Welykochy