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  May 2010

CODE4LIB May 2010

Subject:

Re: Buy, Borrow, or Build

From:

Adam Wead <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 7 May 2010 11:47:11 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (56 lines)

This pretty much sums up exactly where we are at right now.  We're opening a brand-spanking-new library and archive and we're looking at "buying, borrowing or building" each system we need: ils, archival management system, digital asset management system, digitization processing/workflow, and more.

The issues I've encountered so far is that buying often entails a significant financial commitment, and that if you don't know exactly what to ask for, you may have to end up paying extra for it down the road.  This has been a huge issue for us, namely because we can't articulate all our needs yet. Right now, we have very little content or data: We have no cataloged books, so no MARC data, we've only just begun to create finding aids for our archival collections, we haven't started digitizing anything, and what's more, we have no users yet because we haven't even opened our doors!

It's a tough situation to be in because you have to guesstimate a lot, and we worry that we'll either end up paying $$$ for a fantastic system that is way too much for our needs, or we'll underestimate and after committing to a vendor we'll have to pay more for functionality that we didn't negotiate up front.

This makes the build option attractive because you have a lot of flexibility to scale things up or down, or add new services.  However, there are costs in terms of human power.  I'm the only tech guy, so I'd be doing all the programming work.  I've floated the idea of hiring programmers for certain things, but it's hard to say whether paying a vendor for a system would be more or less expensive that building your own with the costs of human resources like programmers and the like.  If you do build your own, you're usually not tied to any contractual agreement, but it's usually those agreements that provide support for your product when things go wrong.  In the "build-your-own" scenario, you are your own support, which is another cost addition that's hard to quantify.  In the end, however, if you build it, it's yours to keep and share with others should you choose.

This brings me to the borrow option, which may prove to be the best solution for us, depending on the system.  For example, we're looking at partnering with another institution for our MARC and ILS needs.  There are tons of consortial organizations that offer similar services, but it tends to be a "one-size fits all" kind of thing.  For basic services, this isn't such a big deal.  ILS-es are fairly straight-forward.  Yes, they're complicated, but they've been around for a while and I don't see much point in building your own one of those since there are so many choices out there, open-source or otherwise.

As we look at choosing systems for our own institution-specific needs, we're finding fewer "buy" options that fit the bill.  This means building some systems from scratch.  Building will take a lot of my time, so it's important to use the buy and borrow options for things that I'm confident will not require lots of additional work maintaining.  Buying and borrowing are ideal here because there's already some kind of support and maintenance framework, which should (ideally!) give you more time to code.

So, I guess I'd break it down like this:

Buy:
 - great for specific needs with lots of known variables
 - best used for "well worn" solutions
 - should always have good support
 - be prepared for real costs of subscriptions and additional functionality

Borrow:
 - ideal when your needs align with the needs of another that already has a solution
 - great for collaboration
 - contractual agreements may be needed
 - can have good support, but not always
 - should continue to work so long as everyone's needs are the same

Build:
 - great for unique requirements or solutions with a lot of unknowns
 - use collaboration if you can
 - you can take it home with you
 - be prepared for human costs (coding, testing, etc.)
 - scalability, maintainability, and flexibility are the big issues

I should add that you can combine these in different ways such as purchasing or borrowing components that your build into one solution.  We're also trying to plan ahead as much as possible and build-in flexibility so that if we need to switch to something else, either go from build to buy, or buy to borrow, etc. when we find our needs changing, we can do that without hurting ourselves too much.

These are just my thoughts from what's happened to us so far... feel free to disagree/agree/chime-in

...adam



-----Original Message-----
From: Code for Libraries on behalf of Frumkin, Jeremy
Sent: Thu 5/6/2010 2:32 PM
To: [log in to unmask]
Subject: [CODE4LIB] Buy, Borrow, or Build
 
Hi all -

One of the interesting tasks on my plate this year is to devise a document that reflects a strategy around "Buy, Borrow, or Build" as relates to technology approaches here at the University of Arizona Libraries. Below is the text of this "reference architecture", and I am particularly interested to hear comments from the community regarding this document. 

 
Rock & Roll: (noun) African American slang dating back to the early 20th Century. In the early 1950s, the term came to be used to describe a new form of music, steeped in the blues, rhythm & blues, country and gospel. Today, it refers to a wide variety of popular music -- frequently music with an edge and attitude, music with a good beat and --- often --- loud guitars.© 2005 Rock and Roll Hall of Fame and Museum.
 
This communication is a confidential and proprietary business communication. It is intended solely for the use of the designated recipient(s). If this communication is received in error, please contact the sender and delete this communication.

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