[OPEN-ILS-DEV] import data from voyager - wiki documentation

[Wilkening, Chris]

Documentation is the Evergreen Achilles' heel, but they're always
looking for people to help with documentation!

Christopher Wilkening

Web/Application Developer

Brodart Co.

570-326-2461 x6496


-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org
[mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of
Jason Zou
Sent: Thursday, May 24, 2007 1:21 PM
To: open-ils-dev at list.georgialibraries.org
Subject: Re: [OPEN-ILS-DEV] import data from voyager

Dan Scott wrote:
> On 24/05/07, Mike Rylander <mrylander at gmail.com> wrote:
>> On 5/24/07, Jason Zou <qzou at lakeheadu.ca> wrote:
>> > Hi everyone,
>> >
>> > By using scripts in the Open-ILS/src/extra/import/, I imported
about
>> > 11,000 MARC records. Although the process was very slow, it seems
that
>> > it is working. And records have been added into the following
tables:
>> >           biblio.record_entry
>> >           metabib.rec_descriptor
>> >           metabib.full_rec
>> >           metabib.title_field_entry
>> >           metabib.author_field_entry
>> >           metabib.subject_field_entry
>> >           metabib.keyword_field_entry
>> >           metabib.series_field_entry
>> >
>> > But when I tried to use OPAC to find some records, I always got 
>> nothing.
>> > I am wondering whether there are something that I missed out.
>> >
>> > Any suggestions are highly appreciated.
>>
>> By default, records are required to have items attached in order to
be
>> visible in the public opac -- though they will show up inside the
>> Staff Client with shading to indicate that they aren't publicly
>> visible.  If that's of no concern in this case, you can run the
>> following directly against the database:
>>
>> evergreen# UPDATE biblio.record_entry SET source = 3;
>> evergreen# VACUUM ANALYZE biblio.record_entry;
>>
>> The second statement isn't strictly required, but it's a good idea.
>> In fact, if you haven't already, you probably want to just go ahead
>> and run
>>
>> evergreen# VACUUM ANALYZE VERBOSE;
>>
>> to clean up everything.
>>
>> Anyway, what the UPDATE does it make the records as "transcendent" so
>> they will show up in every location, with or without holdings
>> attached.  The main use case is for globally available electronic
>> materials, and the functionality will probably end up being extended
>> to be location-specific.
>>
>> --miker
>>
>> >
>> > Jason
>> >
>> > Lakehead University
>> >
>> >
>>
>
> Just to break this down a little further (mostly for my own memory
> assistance, but maybe it will be interesting to someone else), the
> reason UPDATE biblio.record_entry SET source = 3; works is because the
> value '3' is the corresponding identifier in the config.bib_source
> table that represents "Project Gutenberg" sources.
>
> I included a copy of the MARC records for Project Gutenberg texts in
> the /root directory in the Gentoo VMWare image, so if you're playing
> along at home, the steps to get 14449 records visible in your Gentoo
> VMWare image Evergreen catalogue are:
>
> # su - opensrf
> $ cd /root/ILS/Open-ILS/src/extras/import/
> $ perl marc2bre.pl /root/gutenberg.marc > ~/gutenberg.bre
> $ perl direct_ingest.pl ~/gutenberg.bre > ~/gutenberg.ingest
> $ perl pg_loader.pl -or bre -or mrd -or mfr -or mtfe -or mafe -or msfe
> -or mkfe -or msefe -a mrd -a mfr -a mtfe -a mafe -a msfe -a mkfe -a
> msefe < ~/gutenberg.ingest > ~/gutenberg.sql
> $ psql -U postgres openils
> # \i ~/gutenberg.sql
> # UPDATE biblio.record_entry SET source = 3;
> # VACUUM ANALYZE biblio.record_entry;
> # \q
>
> I'll write this up in more detail in the wiki. Hopefully people will
> be able to adapt these instructions for importing their own MARC
> records, then we can flesh out the steps for actually attaching copies
> to the bib records rather than just "cheating" by making the records
> transcendant :)
>
Thanks Dan.

I have done almost the same thing you mentioned above, although I do not

understand what is 'bre', 'mrd', ... .
It is always good to document in more detail in the wiki. It seems to me

that Evergreen does not have good documentation. In the wiki,
lots of content have not been created yet. For new users like me, it is 
frustrating to dig out information from the wiki and this list.

Jason

Lakehead University