LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2018

CODE4LIB January 2018

Subject:

Re: MARC Holdings

From:

Naomi Dushay <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 25 Jan 2018 21:06:40 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

There is also java MHLD processing code in Stanford’s branch of Solrmarc:

https://github.com/sul-dlss/solrmarc-sw/blob/master/stanford-sw/src/edu/stanford/MhldDisplayUtil.java   esp towards bottom of that class.

- Naomi

On Jan 25, 2018, at 7:16 AM, Robert Haschart <[log in to unmask]<mailto:[log in to unmask]>> wrote:

There is another MARC handling library, written in Java, called marc4j  ( https://github.com/marc4j/marc4j )  it is used heavily by the Open Source project named SolrMarc, which extracts information from MARC records and builds Solr records.
One of the plug-ins for SolrMarc that our University's Library uses gathers Summary Holdings information including translating the 853 and 863 fields to text.    It even makes an attempt to collapse a series of consecutive holdings into a range for example:
  2015, no.1- 2017, no.46 (2015:Jan 5-2017:Nov 13)

Although I just found that in that case it missed a few gaps in the middle of the range.  I can make the necessary code available is anyone is interested.

-Bob Haschart
University of Virginia Library


On 1/19/2018 7:32 PM, Julie Cole wrote:
It will take me awhile to delve into this all and understand it so I can determine that the code IS indeed helpful.  But one thing I know is that as people you are all very helpful.  Thanks so much for sharing.  I love this community.
Julie.

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Spurgin, Kristina M.
Sent: Friday, January 19, 2018 8:13 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [CODE4LIB] MARC Holdings

That MFHD.pm code is so helpful! Thanks for sharing.

-Kristina

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
Mike Rylander
Sent: Thursday, January 18, 2018 5:49 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [CODE4LIB] MARC Holdings

Evergreen has Perl code for generating holdings statements from MFHD
that we use in the serials module.  The core MFHD module could
certainly be used directly (with, perhaps, a namespace change), and
the serials module code could serve as a guide for how to make use of
the MFHD module.  The latter is, of course, tied to Evergreen's data
structures and general architecture, but the specific calls made by
the serials code to use the MFHD module should be relatively
transparent to a Perl developer and you can ignore all the Evergreen
bits.  We're dealing with MARC data (MARC::Record objects) at the
point that we're calling the MFHD module, so that should be translatable to one's own code.

See MFHD.pm and the contents of the MFHD directory here:
http://git.evergreen-ils.org/?p=Evergreen.git;a=tree;f=Open-
ILS/src/perlmods/lib/OpenILS/Utils

The serials module is implemented by the code here:
http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-
ILS/src/perlmods/lib/OpenILS/Application/Serial.pm

HTH,

--
Mike Rylander
 | President
 | Equinox Open Library Initiative
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  [log in to unmask]  | web:
http://equinoxinitiative.org


On Thu, Jan 18, 2018 at 4:25 PM, Spurgin, Kristina M.
<[log in to unmask]> wrote:
The MARC libraries cited make it easy to work with MARC in general,
but
unfortunately the Perl and Ruby versions don't come with any help for
the "interesting" problem of transforming Holdings 853s and 863s into
human- readablesummary holdings statements (like you'd record in the
866 or 867). (I haven't worked with PyMARC).
We had the same sort of need you describe years ago and came up with
some Perl code that clunkily (and in some cases not quite 100%
accurately) does this. It's not publicly available to point to, but I
could send the relevant part of that code if you are interested.
There has been mild grumbling (from those who pay attention to our
serials
display) about the not-great way this works, and we are working on a
new discovery interface, so it's on my list to improve the summary
holdings generation from 853s/863s.
I did some searching for code to do this, but didn't find anything
in my first
attempt. If you find something useful that someone else has for this,
please do share!
I've been thinking through a good approach, but don't have anything
implemented yet.
best,
Kristina

-=-
Kristina M. Spurgin -- Library Data Strategist
     E-Resources & Serials Management, Davis Library
                      University of North Carolina at Chapel Hill
             CB#3938, Davis Library -- Chapel Hill, NC 27514-8890
                           919-962-3825 -- [log in to unmask]

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf
Of Andromeda Yelton
Sent: Thursday, January 18, 2018 4:01 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] MARC Holdings

Note that if perl isn't your thing there are MARC libraries in
several languages
- python and ruby at least, probably others I don't remember off
the top of my head (since I work in python and ruby, no shade to
other people's languages :). https://github.com/edsu/pymarc ,
https://github.com/ruby-marc/ruby-
marc .

On Thu, Jan 18, 2018 at 12:50 PM, Julie Cole <[log in to unmask]> wrote:

Hello all,
I'm pretty new to the world of library systems and this is my first post.

Anyone have any experience parsing MARC Holding records (853 and
863) into a more readable 866 or 867 format?
We are wanting to export our holdings from our ILS into our
Discovery Layer and trying to save some of the money that the ILS
vendor would charge us to create the records.

The parsing doesn't look fun, so I was hoping someone has some
code to use as a starting point.
Also, I'm not sure how clean our data in 853 and 863 is so any
scripts or advice on gotchas when cleaning that up would be
appreciated.
We have about 60,000 holding records.

Thanks,
Julie.


Julie Cole
Library Systems Administrator
Langara College Library
Vancouver, BC



--
Andromeda Yelton
Senior Software Engineer, MIT Libraries: https://libraries.mit.edu/
President, Library & Information Technology Association:
http://www.lita.org http://andromedayelton.com @ThatAndromeda
<http://twitter.com/ThatAndromeda>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2024
October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager