LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2008

CODE4LIB June 2008

Subject:

Re: zebraidx errors

From:

Eric Lease Morgan <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 17 Jun 2008 16:29:50 -0400

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (130 lines) , opac.pl (52 lines) , Unknown Name (4 lines) , pqf.properties (4 lines) , Unknown Name (5 lines)


On Jun 17, 2008, at 12:06 PM, siznax wrote:

> the Zebralist appears to be relatively inactive.
> anyone here have experience indexing MARC binaries
> with zebra?


I will try to outline here how to index (and search) MARC records  
using Zebra, but tweaking the indexing process is a bit trickier than  
I know how to do.

   1. Install yaz, zebra, and all of their friends. I have found that  
the "standard" make process works pretty well, but allow yaz and  
zebra to specify where it puts various configuration files. The extra  
specification is not worth the effort.

   2. Save your MARC records someplace on your file system. By  
"binary" MARC records, I suppose you mean "real" MARC records -- MARC  
records in communications format -- MARC records as the types of  
records fed to traditional integrated library systems. This is  
opposed to some flavor of XML or "tagged format" often used for display.

   3. Create a zebra.cfg file, and have it look something like this:

       # global paths
       profilePath: .:./etc:/usr/local/share/idzebra-2.0/tab
       modulePath: /usr/local/lib/idzebra-2.0/modules

       # turn ranking on
       rank: rank-1

       # define a database of marc records called opac
       opac.database: opac
       opac.recordtype: grs.marcxml.marc21
       attset: bib1.att
       attset: explain.att

   4. Index your MARC records with the following command. You should  
see lot's of great stuff sent to STDOUT.

       zebraidx -g opac update <path to MARC records>


You have now created your index. Once you get this far with indexing,  
you will want to tweak various .abs files (I think) to enhance the  
indexing process. This particular thing is not my forte. It seems  
like black magic to most of us. This is not a Zebra-specific problem;  
this is a problem with Z39.50.

Next, you need to implement the client/server end of things:

   5. Start your server. This will be a Z39.50 server -- a "kewl"  
library-centric protocol that existed before the Internet got hot:

       zebrasrv localhost:9999 &

   6. Use yaz-client to search your index:

       & yaz-client
       Z> open localhost:9999/opac
       Z> find origami
       Z> show 1
       Z> quit

Using the yaz-client almost requires a knowledge of Z39.50. Attached  
should be a Perl script that allows you to search your server in a  
bit more user-friendly way. To use it you will need to install a few  
Perl modules and then edit the constant called DATABASE.

Even though Z39.50 is/was "kewl" it is still pretty icky. SRU is  
better -- definitely a step in the right direction, and Zebra  
supports SRU out of the box. [1]

   7. Create an an SRU configuration file looking something like this:

      <yazgfs>
        <server>
          <config>zebra.cfg</config>
          <cql2rpn>pqf.properties</cql2rpn>
        </server>
      </yazgfs>

   8. Acquire a "better" pqf.properties file. PQF is about querying  
Z39.50 databases. It is ugly. It was designed in a non-Internet  
world. Instead of knowing that 1=4 means search the title field, you  
want to simply search the title. Attached is a "better"  
pqf.properties file, and it is "better" because it maps things like  
1=4 to Dublin Core equivalents. Save it in a directory called etc in  
the same directory as your zebra.cfg file. (Notice how the zebra.cfg  
file, above, denotes etc as being in zebra's path.)

   9. Kill your presently running Z39.50 server.

  10. Start up a SRU server:

       zebrasrv -f sru.cfg localhost:9999 &

  11. Use your HTTP client to search the SRU server. Queries will  
look like this (with carriage returns added for readability):

       http://localhost:9999/opac?
        operation=searchRetrieve&
        version=1.1&
        query=origami&
        maximumRecords=5

The result should be a stream of XML ready for XSLT processing.

All of the above is almost exactly what I did to create an index of  
MARC records harvested from the Library of Congress and the  
University of Michigan's OAI data repository (MBooks). [2] Take a  
look at the HTML source. Notice how the client in this regard is only  
one HTML file containing a form, one CSS file for style, and one XSL  
file for XML to HTML transformation.

HTH.

[1] SRU - http://www.loc.gov/standards/sru/
[2] Example SRU interface - http://infomotions.com/ii/

-- 
Eric Lease Morgan
Head, Digital Access and Information Architecture Department
Hesburgh Libraries, University of Notre Dame

(574) 631-8604





Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager