[OPEN-ILS-GENERAL] Open-ils-general Digest, Vol 94, Issue 69

[max stalnaker]

A few dumb questions:

One of your mission goals is secure.  What have been your exposures to
heartbleed?

One of your mission goals is scalable.  You are dependent there on LBS.  I
fear to look further there but do you have PaaS alternatives?

Max


On Apr 27, 2014 9:00 AM, <open-ils-general-request at list.georgialibraries.org>
wrote:

> Send Open-ils-general mailing list submissions to
>         open-ils-general at list.georgialibraries.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general
> or, via email, send a message with subject or body 'help' to
>         open-ils-general-request at list.georgialibraries.org
>
> You can reach the person managing the list at
>         open-ils-general-owner at list.georgialibraries.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Open-ils-general digest..."
>
>
> Today's Topics:
>
>    1. Re: Generating Report based on MARC data fields (Yamil Suarez)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 27 Apr 2014 10:53:41 -0400
> From: Yamil Suarez <ysuarez at berklee.edu>
> Subject: Re: [OPEN-ILS-GENERAL] Generating Report based on MARC data
>         fields
> To: Evergreen Discussion Group
>         <open-ils-general at list.georgialibraries.org>
> Message-ID: <A9E3B407-E3A2-485C-AA86-E5A5F100F6D7 at berklee.edu>
> Content-Type: text/plain;       charset=us-ascii
>
> Jayaraj,
>
> I have never used Kathy's approach of using "Flattened MARC Fields," but I
> want to learn for the future. Though when I have to make reports similar to
> yours I use SQL to run queries on the "metabib.full_rec" table when looking
> for bib MARC data, and I use the "authority.full_rec" table when looking
> for authority MARC data. Perhaps using "Flattened MARC Fields" is a better
> approach, but I wanted to share it with the list just in case it is helpful
> to others.
>
> For the record, the metabib.full_rec table has multiple rows for a single
> bib record. One row for each tag and a each individual subfield, if the tag
> uses more than one subfield. So a 245 tag with subfield "a" and "b," will
> be stored as two separate table rows.
>
> So this SQL (if memory serves me correctly) will list all 100 tags, with
> their bib number (record), and the text (value) store in subfield "a"
>
>
> select record, tag, subfield, value
> from metabib.full_rec
> where tag = '100' and subfield = 'a'
> order by value
>
> Regretfully, because each subfield of a tag get its own row, your search
> for "245 a b c" will require using a SQL technique called "table aliases."
>
> Hope this helps a bit,
> Yamil
>
>
>
>
> > On Apr 26, 2014, at 10:56 AM, Kathy Lussier <klussier at masslnc.org>
> wrote:
> >
> > Hi Jayaraj,
> >
> > I don't do much with reports, but this very question came up in IRC
> yesterday. The suggestion there that came from Michele Morgan at NOBLE was
> to use the "Flattened MARC Fields" source in reports.
> >
> > I hope this helps!
> >
> > Kathy
> >
>
>
> End of Open-ils-general Digest, Vol 94, Issue 69
> ************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20140427/071069a1/attachment.htm>