In the wiki, it has that Howard County Library was proposing an RFC to allow searching on the 001. http://wiki.koha-community.org/wiki/Advanced_cataloging_search_RFC In the old documentation that is on LibLime's site, it says "field 001 is a special field that you cannot map data to in Koha" We need to be able to link to that number. Does anyone have any ideas about how to do so, since we cannot seem to keep our current id's when migrating to Koha 3.2? Thanks. -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Hi Linda, not sure I understand your questions correctly, but I hope this is helpful for you: There is a search option for 001 field in z39.50 search in cataloging called 'Control number'. This will be available in acquisitions in 3.4 too. You can also search for the 001 fields in simple search in staff and opac, using following syntax: 'Control-number:'. Please note it has to be a big C. I think you could also add a search option in the pull down using some jQuery. You can also construct links to your OPAC using 001: http://hfjs.bsz-bw.de/cgi-bin/koha/opac-search.pl?q=Control-number: 005288320 Not being able to map means probably that you can't map it to biblio or biblioitems table. But you don't need that to make it searchable :) Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Linda Culberson Sent: Friday, January 14, 2011 3:53 PM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Koha - Advanced cataloging search RFC on 001
In the wiki, it has that Howard County Library was proposing an RFC to allow searching on the 001. http://wiki.koha-community.org/wiki/Advanced_cataloging_search_RFC In the old documentation that is on LibLime's site, it says "field 001 is a special field that you cannot map data to in Koha" We need to be able to link to that number. Does anyone have any ideas about how to do so, since we cannot seem to keep our current id's when migrating to Koha 3.2? Thanks.
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Katrin, That was a huge help. I had read about the "control-number" but note that I was reading it with a lowercase "C" Thanks! On 1/14/2011 9:09 AM, Fischer, Katrin wrote:
Hi Linda,
not sure I understand your questions correctly, but I hope this is helpful for you:
There is a search option for 001 field in z39.50 search in cataloging called 'Control number'. This will be available in acquisitions in 3.4 too.
You can also search for the 001 fields in simple search in staff and opac, using following syntax: 'Control-number:'. Please note it has to be a big C.
I think you could also add a search option in the pull down using some jQuery.
You can also construct links to your OPAC using 001: http://hfjs.bsz-bw.de/cgi-bin/koha/opac-search.pl?q=Control-number: 005288320
Not being able to map means probably that you can't map it to biblio or biblioitems table. But you don't need that to make it searchable :)
Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Linda Culberson Sent: Friday, January 14, 2011 3:53 PM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Koha - Advanced cataloging search RFC on 001
In the wiki, it has that Howard County Library was proposing an RFC to allow searching on the 001. http://wiki.koha-community.org/wiki/Advanced_cataloging_search_RFC In the old documentation that is on LibLime's site, it says "field 001 is a special field that you cannot map data to in Koha" We need to be able to link to that number. Does anyone have any ideas about how to do so, since we cannot seem to keep our current id's when migrating to Koha 3.2? Thanks.
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Katrin and others, I'm not sure I understand this, but the search Katrin gave worked the first time I tried it, but I am not able to get it to work consistently. Most often I got a 404:Page not found error, Looking at the log file I see: opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 213., referer: http://koha.mdah.state.ms.us/koha/opac-search.pl?q=Control-number:000000073 So I looked up line 213 in XSLT.pm and it deals with items: my $homebranch = xml_escape($branches->{$item->{homebranch}}->{'branchname'}); my $itemcallnumber = xml_escape($item->{itemcallnumber}); $xml.= "<item><homebranch>$homebranch</homebranch>". "<status>$status</status>". "<itemcallnumber>".$itemcallnumber."</itemcallnumber>" . "</item>"; I discovered that this error seems to happen with records will lots of items. http://koha.mdah.state.ms.us/koha/opac-search.pl?q=Control-number:000036801 which has only one item worked once and then generated an error: opac-MARCdetail.pl: Use of uninitialized value in string ne at /usr/share/koha/opac/cgi-bin/opac/opac-MARCdetail.pl line 144., referer: http://koha.mdah.state.ms.us/cgi-bin/koha/opac-detail.pl?biblionumber=36083 Just typing in http://koha.mdah.state.ms.us/cgi-bin/koha/opac-detail.pl?biblionumber=36083 does give the right record though, so the index is working, it just doesn't consistently pull up the record Has anyone else noticed this behavior? We are on Koha version 3.02.02 On 1/14/2011 9:19 AM, Linda Culberson wrote:
Katrin, That was a huge help. I had read about the "control-number" but note that I was reading it with a lowercase "C" Thanks!
On 1/14/2011 9:09 AM, Fischer, Katrin wrote:
Hi Linda,
not sure I understand your questions correctly, but I hope this is helpful for you:
There is a search option for 001 field in z39.50 search in cataloging called 'Control number'. This will be available in acquisitions in 3.4 too.
You can also search for the 001 fields in simple search in staff and opac, using following syntax: 'Control-number:'. Please note it has to be a big C.
I think you could also add a search option in the pull down using some jQuery.
You can also construct links to your OPAC using 001: http://hfjs.bsz-bw.de/cgi-bin/koha/opac-search.pl?q=Control-number: 005288320
Not being able to map means probably that you can't map it to biblio or biblioitems table. But you don't need that to make it searchable :)
Katrin
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Linda Culberson Sent: Friday, January 14, 2011 3:53 PM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Koha - Advanced cataloging search RFC on 001
In the wiki, it has that Howard County Library was proposing an RFC to allow searching on the 001. http://wiki.koha-community.org/wiki/Advanced_cataloging_search_RFC In the old documentation that is on LibLime's site, it says "field 001 is a special field that you cannot map data to in Koha" We need to be able to link to that number. Does anyone have any ideas about how to do so, since we cannot seem to keep our current id's when migrating to Koha 3.2? Thanks.
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
On Fri, Jan 14, 2011 at 12:05 PM, Linda Culberson <lculber@mdah.state.ms.us> wrote:
Katrin and others, I'm not sure I understand this, but the search Katrin gave worked the first time I tried it, but I am not able to get it to work consistently. Most often I got a 404:Page not found error, Looking at the log file I see: opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 213., referer: http://koha.mdah.state.ms.us/koha/opac-search.pl?q=Control-number:000000073
So I looked up line 213 in XSLT.pm and it deals with items: my $homebranch = xml_escape($branches->{$item->{homebranch}}->{'branchname'});
Is it possible that some of your items are missing a homebranch assignment? Kind Regards, Chris
This is interesting, I did find some that had the homebranch missing although they were not the ones I was testing. I fixed them anyway. Now my error message is: script not found or unable to stat: /usr/share/koha/opac/cgi-bin/opac/opac-query However, I've been experimenting and at least sometimes (it hasn't broken yet) the following works: http://koha.mdah.state.ms.us/cgi-bin/koha/opac-search.pl?idx=Control-number&q=000000073 On 1/14/2011 11:30 AM, Chris Nighswonger wrote:
On Fri, Jan 14, 2011 at 12:05 PM, Linda Culberson <lculber@mdah.state.ms.us> wrote:
 Katrin and others, I'm not sure I understand this, but the search Katrin gave worked the first time I tried it, but I am not able to get it to work consistently. Most often I got a  404:Page not found error, Looking at the log file I see:  opac-search.pl: Use of uninitialized value in hash element at /usr/share/koha/lib/C4/XSLT.pm line 213., referer: http://koha.mdah.state.ms.us/koha/opac-search.pl?q=Control-number:000000073
So I looked up line 213 in XSLT.pm and it deals with items: my $homebranch = xml_escape($branches->{$item->{homebranch}}->{'branchname'}); Is it possible that some of your items are missing a homebranch assignment?
Kind Regards, Chris
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
participants (3)
-
Chris Nighswonger -
Fischer, Katrin -
Linda Culberson