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  October 2017

CODE4LIB October 2017

Subject:

Re: [EXT] Re: [CODE4LIB] Sorting LC call numbers in MySQL

From:

"Thomale, Jason" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 26 Oct 2017 12:41:20 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (126 lines)

I'm late to the party here, but one more potential option for you:

https://github.com/unt-libraries/pycallnumber

Another python package for dealing with call numbers, but in this case it may be helpful if you find your call number data is a bit messy. I wrote it after having to deal with large sets of call numbers from our catalog that either weren't actually what they said they were (SuDoc numbers in LC fields, for instance, where I had to handle them correctly regardless) or had unpredictable localizations that threw off attempts at sorting (particularly things like dates and other free-text or semi-structured edition/volume/copy information). Good luck!

Jason


-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Will Martin
Sent: Wednesday, October 25, 2017 4:38 PM
To: [log in to unmask]
Subject: [EXT] Re: [CODE4LIB] Sorting LC call numbers in MySQL

Wow, options popping out of the woodwork left and right! We'll probably 
try out several of these and see which suits best.

Thanks a lot, everyone!

Will

On 2017-10-25 16:31, Ray Voelker wrote:
> Figured I'd chime in with something I spent entirely way too much time 
> on
> (probably). A JavaScript class to normalize and sort LC call numbers
> 
> https://github.com/rayvoelker/js-loc-callnumbers
> 
> Not sure if that helps you in your particular situation, but it might 
> give
> you a place to start along with the other suggestions given!
> 
> Good luck!
> 
> --Ray
> 
> On Oct 25, 2017 5:16 PM, "Craig Dietrich" <[log in to unmask]> 
> wrote:
> 
>> If you're using PHP you could use natsort() on the result,
>> 
>> http://php.net/manual/en/function.natsort.php
>> 
>> Alternatively, you could try ordering by the length of the VARCHAR 
>> field
>> first,
>> 
>> ORDER BY LENGTH(field), field
>> 
>> Sent from mobile
>> 
>> > On Oct 25, 2017, at 2:11 PM, Jodie Gambill <[log in to unmask]>
>> wrote:
>> >
>> > Hi Will -
>> > I had a similar task a few years ago on a small project, though we only
>> > used the classMark and classNum (from your example) parts of the call
>> > number for what we needed. I implemented it as you outlined above, with
>> two
>> > separate fields to enable proper sorting -- classMark as varchar and
>> > classNum as float. I look forward to hearing if anyone else has done it
>> > more efficiently!
>> > -Jodie
>> >
>> >> On Wed, Oct 25, 2017 at 3:55 PM, Will Martin <[log in to unmask]>
>> wrote:
>> >>
>> >> We have a small web app with a MySQL backend, containing lists of books
>> >> that have been reported lost and tracking our efforts at locating them.
>> >> Access Services requested that the list of currently missing books be
>> >> sorted according to LC call number.  So we did, but the results are
>> ordered
>> >> in that uniquely digital "1000 comes before 2" way.  For example, human
>> >> logic would sort these seven call numbers like so:
>> >>
>> >>        HM132 .A343
>> >>        HM251 .M2 1960
>> >>        HM278 .S37 1990
>> >>        HM281 .C6713 1985
>> >>        HM281 .H6 1958
>> >>        HM1126 .F56 2011
>> >>        HM1261 .K64 1978
>> >>
>> >> But MySQL sorts them like so:
>> >>
>> >>        HM1126 .F56 2011
>> >>        HM1261 .K64 1978
>> >>        HM132 .A343
>> >>        HM251 .M2 1960
>> >>        HM278 .S37 1990
>> >>        HM281 .C6713 1985
>> >>        HM281 .H6 1958
>> >>
>> >> Currently, these are stored in a VARCHAR column in the MySQL table.  The
>> >> research that I've done suggests that there is no way just sort that
>> column
>> >> using ORDER BY, and that we'll have to split out the call number into
>> >> separate columns for its component parts:
>> >>
>> >>        HM = classMark
>> >>        251 = classNum
>> >>        .M2 = cutter
>> >>        1960 = pubYear
>> >>
>> >> ... and then do something like "ORDER BY classMark, classNum, cutter,
>> >> pubYear".
>> >>
>> >> This database is unlikely to grow beyond a few hundred active records at
>> >> most, so I'm not too concerned about the computational overhead of doing
>> >> all that sorting.  But it's going to be a fair bit of work to modify the
>> >> table definition and then rejigger all the associated SQL queries in the
>> >> app.
>> >>
>> >> Does anyone have a better solution for sorting LC call numbers in MySQL
>> >> results?
>> >>
>> >> Thanks.
>> >>
>> >> Will Martin
>> >>
>> >> Head of Digital Initiatives, Systems & Services
>> >> Chester Fritz Library
>> >> University of North Dakota
>> >>
>> 

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

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