[OPEN-ILS-DEV] Metabib Keyword Indexing Issue

[James Fournie]

Hi Doug,

> Sure, I'll file a bug with bib.  It would be great if you or somebody else
> with the knowledge could provide an overview of the  ingest/metabib creation
> process and programs.  For example, I'm wondering if the metabib tables are
> all populated from the MODS transform?, is mfr done first and tables like

The metabib tables are populated from the MODS transform by default,
but you can configure it to populate from MARC if you wish, by adding
xpath statements in the postgres config.metabib_field table.  The
default setting for keyword uses this xpath:

//mods32:mods/*[not(local-name()='originInfo')]

> What code reading I've got done thus far leads me to think that if it was a
> MODS transform problem I would see the problem in various metabib tables for
> the record in question, but the same data is correct everywhere but mkfe.

I'd suggest you try using SuperCat to diagnose your problem.  Find the
record id of a record that has this problem, and then put it in a
supercat url like this:

http://catalogue.bclibraries.ca/opac/extras/supercat/retrieve/marcxml/record/135265

This will give you the record in raw MARCXML.  You can see the result
of the MODS transform by changing marcxml to MODS:

http://catalogue.bclibraries.ca/opac/extras/supercat/retrieve/mods/record/135265

You might see an obvious problem area in the mods where the text is
getting squished together.  You can also try using Oxygen or another
XML tool to apply the above xpath to the mods xml to see the result.

~James Fournie
BC SITKA


>
> Doug Kyle
> Grand Rapids Public Library
>