koha-zebra
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Koha-zebra] Zebra and Authorities [Fwd from: [Koha-devel] switchin


From: Sebastian Hammer
Subject: Re: [Koha-zebra] Zebra and Authorities [Fwd from: [Koha-devel] switching from marc_words to zebra [LONG]]
Date: Tue, 19 Jul 2005 13:29:21 -0400

If I was doing this I would make sure the link field in the biblios was indexed and do an exact search, rather than relying on a redundant table in the relational database. Pull the records, change them, and submit an update request through the Z39.50 client API.

Btw., Adam tells me that Zebra also supports database creation and deletion through Z39.50, and thus through the YAZ/ZOOM client API.

--Sebastian

At 07:01 AM 7/18/2005 -0700, Joshua Ferraro wrote:
So although I haven't personally used it, Koha does support auto-updating
records on-the-fly when an authority record changes. So we'll need an
approach to supporting this behavior using Zebra as Paul outlines here:

>----- Forwarded message from Paul POULAIN <address@hidden> -----
>The authority problem
>=====================
>Authorities have to be linked to the biblio that uses them. Thus, when
>an authority is modified, all biblios using them are automatically
>modified (script in misc/merge_authority.pl in Koha cvs & 2.2.x)
>
>To keep trace of the link, Koha uses a $9 local subfield. In UNIMARC,
>the $3 can also be used for this. I don't know if something equivalent
>to $3 exists in MARC21 (could not find information on
>http//www.loc.gov/marc/)
>Many scripts make a heavy use of marc_subfield_table $9 data. For
>example, when you find an authority in authority module, you get the
>number of biblios using this authority. This number is calculated with a
>SQL request on $9 subfield.
>To handle this with zebra, we have 2 solutions :
>- create a table just with the link (biblionumber / authority number)
>that we could query
>- query zebra with exact $9 subfield value
>
>I don't know zebra enough to be sure of the best way to do it. Any
>suggestion/experience welcomed.
>
>The authority problem (another one...)
>======================================
>Authorities are MARC::Records too... (without items)
>So they also have auth_structure & auth_word & all the infos that are in
>biblios (except items level, as there is no "authority" items).
>so we could imagine to have 2 zebra databases : one for biblios and one
>for authorities.
>Everything previously in this mail can be copied here. That's something
>we could investigate after moving MARC biblios to zebra, as we would
>have more experience on this tool.
So what's the best way to proceed with authority support?

--
Joshua Ferraro               VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE
President, Technology       migration, training, maintenance, support
LibLime                                Featuring Koha Open-Source ILS
address@hidden |Full Demos at http://liblime.com/koha |1(888)KohaILS


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Koha-zebra mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/koha-zebra

--
Sebastian Hammer, Index Data, www.indexdata.com
Direct phone: (603) 209-6853 Fax: (603) 357-1813





reply via email to

[Prev in Thread] Current Thread [Next in Thread]