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, <[email protected]> wrote: > Send Open-ils-general mailing list submissions to > [email protected] > > 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 > [email protected] > > You can reach the person managing the list at > [email protected] > > 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 <[email protected]> > Subject: Re: [OPEN-ILS-GENERAL] Generating Report based on MARC data > fields > To: Evergreen Discussion Group > <[email protected]> > Message-ID: <[email protected]> > 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 <[email protected]> > 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 > ************************************************ >
