Re: [OPEN-ILS-GENERAL] Marc field change script

[Jason Stephenson]

It is personal preference.

I agree wholeheartedly on creating your own, custom schema for
nonstandard things. We've got a schema called cwmars for custom
functions, views, and tables that we use in some local processes.

I've also added a schema called backstage to use exclusively with our
quarterly bibliographic/authority updates from Backstage Library Works.

On 4/7/20 9:03 AM, Rogan Hamby wrote:
> To me, and this is personal preference I think, I don't see a big
> difference between writing something once outside the db versus in it. 
> Both approaches are fine in my mind.  It does make me think of a point I
> didn't mention though, which is I wouldn't store a function in any
> existing Evergreen schema.  If you do make your own functions for tasks
> like this create a distinct schema for them along with any tables.  I'm
> not a fan of mixing project stuff into the stock schemas.  
> 
> 
> 
> On Tue, Apr 7, 2020 at 8:45 AM Jason Stephenson  > wrote:
> 
> Glen & Rogan,
> 
> I prefer to do these things outside of the database, i.e. pull the
> record out with DBI, modify it, and then update it with DBI.
> 
> I'm not a fan of writing database functions for something that I'll use
> only once or twice.
> 
> I have some utility scripts that I've used and shared with the world
> available on Github:
> 
> https://github.com/Dyrcona/evergreen_utilities/tree/master/perl
> 
> A couple of those might prove useful as examples, possibly
> loaderecords.pl .
> 
> My pre-conference presentation last year covered getting started writing
> utility programs in Perl using the Evergreen back end. The files for it
> are also available on Github:
> 
> https://github.com/Dyrcona/evergreen2019-preconference
> 
> I hope that you find the above to be useful, and if you have more
> technical questions, the conversation should probably move to the
> development list.
> 
> Cheers,
> Jason
> 

Re: [OPEN-ILS-GENERAL] Marc field change script

[Rogan Hamby]

To me, and this is personal preference I think, I don't see a big
difference between writing something once outside the db versus in it.
Both approaches are fine in my mind.  It does make me think of a point I
didn't mention though, which is I wouldn't store a function in any existing
Evergreen schema.  If you do make your own functions for tasks like this
create a distinct schema for them along with any tables.  I'm not a fan of
mixing project stuff into the stock schemas.



On Tue, Apr 7, 2020 at 8:45 AM Jason Stephenson  wrote:

> Glen & Rogan,
>
> I prefer to do these things outside of the database, i.e. pull the
> record out with DBI, modify it, and then update it with DBI.
>
> I'm not a fan of writing database functions for something that I'll use
> only once or twice.
>
> I have some utility scripts that I've used and shared with the world
> available on Github:
>
> https://github.com/Dyrcona/evergreen_utilities/tree/master/perl
>
> A couple of those might prove useful as examples, possibly loaderecords.pl
> .
>
> My pre-conference presentation last year covered getting started writing
> utility programs in Perl using the Evergreen back end. The files for it
> are also available on Github:
>
> https://github.com/Dyrcona/evergreen2019-preconference
>
> I hope that you find the above to be useful, and if you have more
> technical questions, the conversation should probably move to the
> development list.
>
> Cheers,
> Jason
>
>

Re: [OPEN-ILS-GENERAL] Marc field change script

[Jason Stephenson]

Glen & Rogan,

I prefer to do these things outside of the database, i.e. pull the
record out with DBI, modify it, and then update it with DBI.

I'm not a fan of writing database functions for something that I'll use
only once or twice.

I have some utility scripts that I've used and shared with the world
available on Github:

https://github.com/Dyrcona/evergreen_utilities/tree/master/perl

A couple of those might prove useful as examples, possibly loaderecords.pl.

My pre-conference presentation last year covered getting started writing
utility programs in Perl using the Evergreen back end. The files for it
are also available on Github:

https://github.com/Dyrcona/evergreen2019-preconference

I hope that you find the above to be useful, and if you have more
technical questions, the conversation should probably move to the
development list.

Cheers,
Jason

Re: [OPEN-ILS-GENERAL] Marc field change script

[Rogan Hamby]

Hi Glen,

If you have someone on staff comfortable with MARC::Record this is a simple
thing to do with PLPERL as a function.  In fact I'd say this is a good
really simple one for someone to cut their teeth on if they were learning
and the kind of thing I was going to do in the preconference.  Depending on
how things work out I may still do something like it for the virtual
conference.

As always caveat auctor (writer beware) - use a test server first, test
carefully, etc...



On Mon, Apr 6, 2020 at 12:25 PM Glen Modell  wrote:

> Hello, I would like to know if anyone has a script which changes or
> eliminates a given MARC subfield for a given list of bibliographic records.
>
> In particular, we have about 10,000 records with contents in the 100-e
> subfield which we would like to eliminate.  In those cases, the 100-a ends
> in a comma, which we would like to eliminate (or change to a period) as
> well.
>
> Thanks.  --  Glen.
>
> *
> Glen Modell
> Library Automation Specialist
> Ann Arbor District Library
> mode...@aadl.org
> 734-327-8322
>

Re: [OPEN-ILS-GENERAL] Marc field change script

[Linda Jansova]

Hi Glen,

In some cases MarcEdit can be a good solution: 
https://marcedit.reeset.net/ (but it involves exporting and importing 
the records in question - if the records are already loaded in 
Evergreen; if not, then MarcEdit can be the best option).


Linda

On 4/6/20 6:20 PM, Glen Modell wrote:
Hello, I would like to know if anyone has a script which changes or 
eliminates a given MARC subfield for a given list of bibliographic 
records.


In particular, we have about 10,000 records with contents in the 100-e 
subfield which we would like to eliminate.  In those cases, the 100-a 
ends in a comma, which we would like to eliminate (or change to a 
period) as well.


Thanks.  --  Glen.

*
Glen Modell
Library Automation Specialist
Ann Arbor District Library
mode...@aadl.org
734-327-8322

[OPEN-ILS-GENERAL] Marc field change script

[Glen Modell]

Hello, I would like to know if anyone has a script which changes or eliminates 
a given MARC subfield for a given list of bibliographic records. 

In particular, we have about 10,000 records with contents in the 100-e subfield 
which we would like to eliminate. In those cases, the 100-a ends in a comma, 
which we would like to eliminate (or change to a period) as well. 

Thanks. -- Glen. 

* 
Glen Modell 
Library Automation Specialist 
Ann Arbor District Library 
mode...@aadl.org 
734-327-8322