On Mon, Jul 12, 2004 at 05:01:52PM +0300, Christoffer Landtman wrote:
> I am pretty sure that I'm behind the correct issue here, it just still
> needs some verifications. Hopefully I will be able to verify the issue
> as soon as possible.
>
> It has to do with the fact that different server have different setups
> so that e.g. LOC does not support truncation e.g. and I have forgot to
> add the server specific confs into the search_by_cn() meyhod in the
> search API.
Trying to help where I can on this (seems to be a rather esoteric issue):
I'm attaching a note I just received from the yaz list that may shed
light here (if you are already be aware, sorry for the repetition).
From what I can tell, Emilda uses the 001 as a key to retrieve a single
record from the list of records provided in the stage 1 search, if the
book_ean is blank. Makes sense to me.
However, I think the attached note means that LOC populates 001 (in the
context of on-line searches) with some other value (Voyager ID) which
cannot itself be searched from Z39.50.
Thus we have the source of the error: 12 is not supported by LOC. And
we also have no mechanism to retrieve LOC records without book_ean.
Please forgive me if any of this is not correct.
--
Encrypted Mail Preferred:
Key ID: 8527B9AF
Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF
Information: http://www.gnupg.org/
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
--- Begin Message ---
|
Subject: |
Re: [Yazlist] yaz-client search |
David,
Our Voyager server (version 2000) has a problem with Use
attribute "12" (local control number). It is possible to
retrieve a record with that search if you only perform a
single search in the Z39.50 search session, however, if
you perform additional searches in the session, all
subsequent retrievals will be copies of that same record
over and over again.
Therefore, when we implemented the YAZ Proxy (front-end)
in March, we blocked support of Use attribute "12" and
now return diagnostic "114" (unsupported Use attribute).
It is important to note, however, that the 001 in our online
database does not contain the LC control number. The 001
contains the Voyager ID for the bibliographic record. The
LC control number is in the MARC 010 field. (When we
distribute our records via the Cataloging Distribtion Service
we put the 010$a in the 001 field as well.)
Therefore, the following search will retrieve the record
in question.
>yaz-client z3950.loc.gov:7090/voyager
>find @attr 1=9 2003550511
Please let me know if you have additional questions.
Larry
On Tue, 13 Jul 2004, David Everly wrote:
> Sorry for being such a newbie...I'm having difficulty with
> yaz-client find.
>
> I can do the following:
>
> yaz-client z3950.libris.kb.se:210/libr
> find @attr 1=1032 9063207
>
> This gives me the following:
>
> Records: 1
> [LIBR]Record type: USmarc
> 001 9063207
> 003 LIBRIS
> 005 20030909102805.0
> ...
>
> However when I try to do similar with LOC, searching
> for the following, I cannot retrieve it by its "001" value:
>
> yaz-client z3950.loc.gov:7090/voyager
> find @attr 1=12 13088961
> [114] Unsupported Use attribute -- v2 addinfo '12'
> find @attr 1=9 13088961
> Number of hits: 0
> ...
>
> Here is what it should return (I was able to find it by other means):
>
> Records: 1
> [VOYAGER]Record type: USmarc
> 001 13088961
> 005 20030415110948.0
> ...
>
> I suppose what I'm asking is how to find field "001" = "13088961"
> from Library of Congress with yaz-client?
>
> find @attr 1=???? 13088961
>
> I'm attaching the full record I want to retrieve this way for
> example.
>
> Thanks for reading.
>
> --
> Encrypted Mail Preferred:
> Key ID: 8527B9AF
> Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF
> Information: http://www.gnupg.org/
>
>
> ASCII ribbon campaign:
> () against HTML email
> /\ against Microsoft attachments
> Information: http://www.expita.com/nomime.html
------------------------------------------------------------
Larry E. Dixson Internet: ldix@xxxxxxx
Network Development and MARC
Standards Office, LM639
Library of Congress Telephone: (202) 707-5807
Washington, D.C. 20540-4402 Fax: (202) 707-0115
_______________________________________________
Yazlist mailing list
Yazlist@xxxxxxxxxxxx
http://www.indexdata.dk/mailman/listinfo/yazlist
--- End Message ---
signature.asc
Description: Digital signature
|
