Bill,

If you are talking about parsing Sirsi transaction logs specifically, it's
fairly straightforward to do so with regular expressions and a small amount
of code.  We warehouse data extracted from our logs every night.

If you're talking about working with data retrieved from Sirsi's APIs  more
generally, quite a bit of that can also be done without too much effort.

cheers,

AC

On Thu, Mar 19, 2015 at 9:39 AM, Michelle Suranofsky <[log in to unmask]>
wrote:

> Hi Bill,
>
> I have been working on parsing our logs so we can migrate all of our
> historical circ transactions into OLE.  I was recently able to use the data
> pulled out of the logs to provide circ counts to our acq department for a
> vendor provided spreadsheet of items/isbns (that we had purchased).
>
> After using the Sirsi api to pull all of the charges and renewals out of
> the logs I’ve been using java to parse through these text files and insert
> the information into a sqlite database (as a ‘staging’ database).  From
> there the transactions can be queried (and for me...prepped to migrate).
>
> I would be happy to share my code/process with you.
>
> Michelle
> [log in to unmask]
>
> On Wed, Mar 18, 2015 at 5:55 PM, William Denton <[log in to unmask]> wrote:
>
> > I'm going to analyze a whack of transaction logs from our Symphony ILS so
> > that we can dig into collection usage.  Any of you out there done this?
> > Because the system is so closed and proprietary I understand it's not
> easy
> > (perhaps impossible?) to share code (publicly?), but if you've dug into
> it
> > I'd be curious to know, not just about how you parsed the logs but then
> > what you did with it, whether you loaded bits of data into a database,
> etc.
> >
> > Looking around, I see a few examples of people using the system's API,
> but
> > that's it.
> >
> > Bill
> > --
> > William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/
>