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  November 2007

CODE4LIB November 2007

Subject:

Re: [Fwd: [NGC4LIB] A Thought Experiment]

From:

Deb Bergeron <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Fri, 9 Nov 2007 11:26:04 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (123 lines)

Chris, Carl, et al,

I realize I'm a bit late to the party, but here's my 2 cents.

In response to your comment:

    What will it take to break this logjam?  Is it intensive, informed outreach by people like myself to other directors?  Is it credible tech support offerings from organizations such as regional consortia for open source applications?  Is it both of these and more?

      

The very first thing needed and I do mean the very first thing is to get 
people on-board with Open Source. This requires not one-time 
information, but on-going information to keep this alternative a viable 
recognizable alternative to commercial solutions.  Directors like 
numbers.  How much is it going to save them?  And it doesn't have to 
always be in dollars, it can be in workflow, efficiency of the system, 
etc. 

How do you get that information to librarians and directors and the 
people who write the checks?  Put information on blogs, websites, invite 
Open Source vendors to speak.  Not once, but often.  Continue the 
crusade yourself. 

In Minnesota, we've had both LibLime and Evergreen present at our 
regional vendor user group meeting along with our current vendor sales 
consultants.  We've had more people attend the conferences than ever 
before.  Additionally, those people who heard about the presentations or 
were present went back to their institutions and have asked LibLime to 
come back to talk to other consortiums, institutions, and also the 
state-wide ILL user group conference (MNLink).  After these conferences, 
we built web pages that link to all the information any of the 
vendors--open source and commercial  want to share.  It's all in one 
place at the moment and growing.  I will personally be adding the 
information to my blog. 

While I'm only one person in MN with a passion about Open Source 
solutions, MN has hosted  Open Source presentations at no less than 5 
events since June 2007--that's nearly 1 per month.  It's only a matter 
of time before a MN library decides to move to Open Source.  And why 
wouldn't they?  Currently Koha (LibLime)  has nearly every module 
complete and working that is available from current commercial vendors, 
and Evergreen's (Equinox) is not far behind.  Both Koha and Evergreen 
modules appear faster and have better functionality than currently 
available commercially. 

Additionally, the philosophy and reasoning  for the Open Source ILS 
companies'  willingness to take on the commercial ILS market for the 
good of the users and not their pockets is obvious.  They are not 
'suits,' they know their product inside and out, can demo at a moment's 
notice, willing to share all their information, and the price is less 
than going commercial (based on what I've seen and heard from libs using 
or moving to OS).

And, as always, Carl's comments are dead on!


Deb



Chris Barr wrote:
> Hi Code4Libers,
>
> I am forwarding a post on NGC4Lib from Joe Lucia of Villanova University
> (my boss) that I think might provoke some discussion here.
>
> Now back to work on that Code4Lib proposal...
>
> Cheers,
> Chris Barr
> Villanova University
>
> ------------------------------------------------------------------------
>
> Subject:
> [NGC4LIB] A Thought Experiment
> From:
> Joseph Lucia <[log in to unmask]>
> Date:
> Tue, 06 Nov 2007 17:01:12 -0500
> To:
> "[log in to unmask]" <[log in to unmask]>
>
> To:
> "[log in to unmask]" <[log in to unmask]>
>
>
>   My reply to Eric's message has spurred me on to share a few other thoughts that have been kicking around in my head about the success prospects for open source applications in libraries.  What most frustrates me in a general sense is the degree to which in libraries our human capital and our financial resources are tied into commercial software that rarely meets our needs well.  That is old news.  The issue is how to break free of the inertia that keeps us in a technologically paralyzed state.
>
>   I have initiated a number of conversations within the mid-Atlantic region about the very real potential for a shift of those investments from commercial software support (and staff technical support for commercial products) to a collaborative support environment for open source applications facilitated by our regional network (in this case Palinet, where, in the interest of full disclosure, I currently serve as board president).
>
>    It is frightening for many to contemplate the leap to open source, but if there were a clear process and well-defined path, with technical partners able to provide assistance through the regional networks, I suspect some of the hesitancy to make this move, even among smaller libraries, might dissipate quickly.  Within Palinet, for instance, we have a small regional public library system that has successfully made the transition to Koha and has been able to re-direct funds that used to go into software support to local initiatives.  There's also a publlic library that has transitioned its public computing environment to Linux, at considerable savings and with reduced support & acquisition costs for technology.  The success models are there and developing best practice frameworks and implementation support methods that will scale will not be rocket science.
>
>    These are small test cases but I think they prove the concept.  Evergreen is clearly a project on a much larger scale that is working. And it seems to be driven by the same economies I am trying to describe here. I look  at my own technology budget and think about how much we expend annually for inferior commercial software.  Then I ask myself what if I could find even just a handful of regional partners to pool funds and initiate a support & development consortium for Evergreen (as one obvious choice).  I can easily envision a collaborative group of academic libraries identifying a million dollars of "liberated" software support funds within a year.
>
>    What will it take to break this logjam?  Is it intensive, informed outreach by people like myself to other directors?  Is it credible tech support offerings from organizations such as regional consortia for open source applications?  Is it both of these and more?
>
>    If we look beyond money to personnel, the option looks even better.  Let me suggest some numbers.  What if, in the U.S., 50 ARL libraries, 20 large public libraries, 20 medium-sized academic libraries, and 20 Oberlin group libraries anted up one full-time technology position for collaborative open source development. That's 110 developers working on library applications with robust, quickly-implemented current Web technology -- not legacy stuff.  There is not a company in the industry that I know of which has put that much technical effort into product development. With such a cohort of developers working in libraries on library technology needs -- and in light of the creativity and thoughtfulness evident on forums like this one -- I think we would quickly see radical change in the library technology arena. Instead of being technology followers, I venture to say that libraries might once again become leaders.  Let's add to the pool some talent from beyond the U.S. -- say !
>  
>
>  20 libraries in Canada, 10 in Australia, and 10 in the U.K. put staff into the pool.  We've now  got 150 developers in this little start-up.  Then we begin pouring our current software support funds into regional collaboratives.  Within a year or two, we could be re-directing 10s of millions of dollars into regional technology development partnerships sponsored by and housed within the regional consortia, supporting and extending the work of libraries.  The potential for innovation and rapid deployment of new tools boggles the mind.  The resources at our disposal in this scenario dwarf what any software vendor in our small application space is ever going to support. And, as is implicit in all I've said, the NGC is just the tip of the iceberg.
>
>    Yes, we'd need to establish sound open source management protocols and we'd have to guard against forks and splintering of effort that might undermine the best possible outcomes.  But I keep thinking about how successful Linux has been, with developers around the world.  Surely librarians and library technologists could evolve a collaborative environment where we'd "play nice" and produce good results for all.
>
>    Let me add one more point.  Libraries are committed to the notion of the "commons."  Libraries are in fact one of the last best hopes for the preservation of the intellectual commons.  That value system should extend to the intellectual work we do on our access systems.  We should reclaim the domain of library technology from the commercial and proprietary realms and actualize is as part of our vision of the commons. I think there's a clear path to that end.  We are also congenital collaborators.  Can you think of any other group of institions that share their stuff the way we do through ILL?  So how can we marshal the courage to make open source technology happen in more than a few isolated library environments?
>
>   BTW, we at Villanova are looking seriously at migration module by module over the next year from commercial applications to open source solutions in every area where this is a viable option.  I intend to put my money where my mouth is.  VuFind is the first (necessary) step.
>
> *********
> Joe Lucia
> University Librarian
> Villanova University
> 610-519-4290
>
>   

-- 

Deb Bergeron <mailto:[log in to unmask]> System Admin: User Support
CLIC Consortium <http://clic.edu>
1619 Dayton Avenue, Suite 204A
Saint Paul, MN 55104
O:*651.644.3878* C:*651.487.7609* F:651.644.6258

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

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
https://lists.clir.org/cgi-bin/wa?A2=ind0711&L=CODE4LIB&D=0&P=28580
lists.clir.org
CC-MAIN-2024-18
67537
application/http; msgtype=response
sha1:IYW62OASN2EA3KBUOIDGA7FRTV6PQANV
<urn:uuid:9f5bf257-dd24-4364-8991-af0c4a2f9b2e>
2024-04-19T23:01:03Z
66.175.211.245
text/html
sha1:CP2DZFICEWKVORQ2D46KCVPPB42SWGDC
<urn:uuid:2156aa0b-b283-4b86-ae4f-0c91b1f8b042>
https://lists.clir.org/cgi-bin/wa?A2=ind0711&L=CODE4LIB&D=0&P=28580
response
<urn:uuid:02dac1c3-6f3e-4ee1-9a61-1f5bc4e35935>
isPartOf: CC-MAIN-2024-18
publisher: Common Crawl
description: Wide crawl of the web for April 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-82
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/