*Jason Bengtson, MLIS, MA*
Head of Library Computing and Information Systems
Assistant Professor, Graduate College
Department of Health Sciences Library and Information Management
University of Oklahoma Health Sciences Center
405-271-2285, opt. 5
*[log in to unmask] <[log in to unmask]>*
This e-mail is intended solely for the use of the individual to whom it is
addressed and may contain information that is privileged, confidential or
otherwise exempt from disclosure. If the reader of this e-mail is not the
intended recipient or the employee or agent responsible for delivering the
message to the intended recipient, you are hereby notified that any
dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this communication in error, please
immediately notify us by replying to the original message at the listed
email address. Thank You.
<[log in to unmask]>
On Wed, May 7, 2014 at 10:02 AM, Andromeda Yelton <
[log in to unmask]> wrote:
> I'm writing a Library Technology Report for ALA TechSource on short, useful
> programs people have written (in whatever language) in libraries, so....ask
> me again in six months and I'll have a giant list for you ;)
> (In the meantime, if you've written short -- under a hundred-ish line --
> programs that do fun or useful things for your library, and ideally if
> "developer" is *not* in your job title, let's talk.)
> IMO advantages of Python include:
> * (Relative) ease of learning and reading
> * Python makes it particularly easy to write string-manipulation-type stuff
> * Tons of high-quality packages available (pymarc, written by code4libbers,
> is particularly library-relevant)
> * A large, often friendly user community that cares about outreach and
> * For me personally, it's the only programming language I know that's ever
> felt *fun* to write
> The main disadvantage in a library context is that the big open-source
> projects used in libraries tend not to be in Python. Also, if you want to
> use Python for a web app, you're going to also want to learn Django or
> Flask or something (which, mind you, are great; it just feels like a hurdle
> if you're used to embedding PHP in HTML pages).
> So if your goal is to script some part of your workflow (especially if you
> need to munch on MARC, csv, text, data...), Python is awesome. If you want
> to be hacking on Hydra or Koha or Drupal or Wordpress or something, you'll
> need a different language.
> Andromeda Yelton
> LITA Board of Directors, Director-at-Large, 2013-2016
> On Wed, May 7, 2014 at 9:13 AM, Julia <[log in to unmask]> wrote:
> > Hi All,
> > This is my first time posting to Code4Lib. Now seems like a good time.
> > I am wondering how you have applied Python in your library. What
> > have been successful? What have you heard of other libraries doing?
> > advantages or disadvantages does it have compared to other scripting
> > languages used in the library field?
> > If you have any thoughts on any of those questions, I'd love to hear from
> > you.
> > Thanks,
> > Julia
> > [log in to unmask]
> > Simmons College Library