[OPEN-ILS-GENERAL] Fields in Marc records used (and not) by Evergreen

[Dan Scott]

On Fri, May 25, 2012 at 9:20 PM, Trisha Cantwell Keene
<tcantwell at coa.edu> wrote:
> Is there a handy, one-stop table that will tell us what fields Evergreen
> uses for the public catalog display?

Hi Trisha:

The easiest answer is "No".

A harder answer is that compiling such a list depends on various factors:

1) What version of Evergreen?
2) What parts of the public catalogue? (Search results, record
details, bookbag display)
3) What flavour of the public catalogue? (JSPAC, SlimPAC, TPAC)
4) Do you include local customizations?
5) Do you include serials holdings from linked MFHD records?

Also, various parts of various displays depend on
MARC-converted-to-MODS, so in those cases one needs to work back
through the MARC2MODS stylesheet to figure out which MARC fields are
possibly populating the MODS elements that are getting drawn into the
public catalogue.

TPAC is probably the easiest to work out, as the file
"Open-ILS/src/templates/opac/parts/misc_util.tt2" drives the bulk of
the definitions through a set of XPath expressions against MARCXML.
You can pick it out from the XPath pretty quickly, I bet; here's a
sample snippet:

        args.publisher =
xml.findnodes('//*[@tag="260"]/*[@code="b"]').textContent;
        args.pubdate =
xml.findnodes('//*[@tag="260"]/*[@code="c"]').textContent;
        args.summary =
xml.findnodes('//*[@tag="520"]/*[@code="a"]').textContent;
        args.edition =
xml.findnodes('//*[@tag="250"]/*[@code="a"]').textContent ||
            xml.findnodes('//*[@tag="534"]/*[@code="b"]').textContent ||
            xml.findnodes('//*[@tag="775"]/*[@code="b"]').textContent;

args.edition is interesting because it looks in 250 $a or (that's what
the '||' symbol means) 534 $b or 775 $b.

Dan