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 2011

CODE4LIB May 2011

Subject:

Re: Seth Godin on The future of the library

From:

graham <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 19 May 2011 16:01:07 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (183 lines)

Replying to Jonathan's mail rather at random, since several people are
saying similar things.

1. 'Free resources can vanish any time.' But so can commercial ones,
which is why LOCKSS was created. This isn't an insoluble issue or one
unique to free resources.

2. 'Managing 100s of paid resources is difficult, managing 1000s of free
ones would be impossible'. But why on earth would you try? There are
many specialized free resources, only a few of which are likely to
provide material your particular library wants in its collection. Surely
you would select the ones you want, not least on grounds of reliability.
And on those grounds (longevity and reliability) you would end up using
Gutenberg in preference to any commercial supplier (not that I'm
suggesting you should)). Selection of commercial resources is done at
least in part by cost; selection of free ones can be done on more
appropriate grounds.

3. 'There is no such thing as a free lunch'. Who said there was? But
resources which can be used freely have advantages over ones that can't.


Graham

On 05/19/11 15:44, Jonathan Rochkind wrote:
> Another problem with free online resources not just 'collection
> selection', but maintenance/support once selected. A resource hosted
> elsewhere can stop working at any time, which is a management challenge.
> 
> The present environment is ALREADY a management challenge, of course.
> But consider the present environment: You subscribe to anywhere from a
> handful to around 100 seperate vendor 'platforms'.  Each one can change
> it's interface at any time, or go down at any time, breaking your
> integration or access to it.  When it does, you've got to notice (a hard
> problem in itself), and then file a support incident with the vendor. 
> This is already a mess we have trouble keeping straight. But.
> 
> Compare to the idea of hundreds or thousands or more different suppliers
> hosting free content, each one of which can change it's interface or go
> down at any time, and when you notice (still a hard problem, now even
> harder because you have more content from more hosts)... what do you do?
> 
> One solution to this would be free content aggregators which hosted LOTS
> of free content on one platform (cutting down your number of sources to
> keep track of make sure they're working), and additionally, presumably
> for a fee, offered support services.
> 
> Another direction would be not relying on remote platforms to host
> content, but hosting it internally. Which may be more 'business case'
> feasible with free content than with pay content -- the owners/providers
> dont' want to let us host the pay content locally.  But hosting content
> locally comes with it's own expenses, the library needs to invest
> resources in developing/maintaining or purchasing the software (and
> hardware) to do that, as well as respond to maintenance issues with the
> local hosting.
> 
> In the end, there's no such thing as a free lunch, as usual. "Free"
> content still isn't free for libraries to integrate with local
> interfaces and support well, whether that cost comes from internal
> staffing and other budgetting, or from paying a third party to help.  Of
> course, some solutions are more cost efficient than others, not all are
> equal.
> 
> Jonathan
> 
> On 5/19/2011 9:31 AM, Bill Dueber wrote:
>> My short answer: It's too damn expensive to check out everything that's
>> available for free to see if it's worth selecting for inclusion, and
>> library's (at least as I see them) are supposed to be curated, not
>> comprehensive.
>>
>> My long answer:
>>
>> The most obvious issue is that the OPAC is traditionally a listing of
>> "holdings," and free ebooks aren't "held" in any sense that helps
>> disambiguate them from any other random text on the Internet.
>> Certainly the
>> fact that someone bothered to transform it into ebook form isn't
>> indicative
>> of anything. Not everything that's available can be cataloged. I see
>> "stuff
>> we paid for" not as an arbitrary bias, but simply as a very, very
>> useful way
>> to define the borders of the library.
>>
>> "Free" is a very recent phenomenon, but it just adds more complexity
>> to the
>> existing problem of deciding what publications are within the library's
>> scope. Library collections are curated, and that curation mission is not
>> simply a side effect of limited funds. The filtering process that goes
>> into
>> deciding what a library will hold is itself an incredibly valuable
>> aspect of
>> the collection.
>>
>> Up until very recently, the most important pre-purchase filter was the
>> fact
>> that some publisher thought she could make some money by printing text on
>> paper, and by doing so also allocated resources to edit/typeset/etc.
>> For a
>> traditionally-published work, we know that real person(s), with
>> relatively
>> transparent goals, has already read it and decided it was worth the
>> gamble
>> to sink some fixed costs into the project. It certainly wasn't a perfect
>> filter, but anyone who claims it didn't add enormous information to the
>> system is being disingenuous.
>>
>> Now that (e)publishing and (e)printing costs have nosedived toward $0.00,
>> that filter is breaking. Even print-on-paper costs have been reduced
>> enormously. But going through the slush pile, doing market research,
>> filtering, editing, marketing -- these things all cost money, and for the
>> moment the traditional publishing houses still do them better and more
>> efficiently than anyone else. And they expect to be paid for their
>> work, and
>> they should.
>>
>> There's a tendency in the library world, I think, to dismiss the value of
>> non-academic professionals and assume random people or librarians can
>> just
>> do the work (see also: web-site development, usability studies, graphic
>> design, instructional design and development), but successful
>> publishers are
>> incredibly good at what they do, and the value they add shouldn't be
>> dismissed (although their business practices should certainly be under
>> scrutiny).
>>
>> Of course, I'm not differentiating free (no money) and free (CC0). One
>> can
>> imagine models where the functions of the publishing house move to a
>> work-for-hire model and the final content is released CC0, but it's not
>> clear who's going to pay them for their time.
>>
>>
>>    -Bill-
>>
>>
>>
>> On Thu, May 19, 2011 at 8:04 AM, Andreas Orphanides<
>> [log in to unmask]>  wrote:
>>
>>> On 5/19/2011 7:36 AM, Mike Taylor wrote:
>>>
>>>> I dunno.  How do you assess the whole realm of proprietary stuff?
>>>> Wouldn't the same approach work for free stuff?
>>>>
>>>> -- Mike.
>>>>
>>> A fair question. I think there's maybe at least two parts: marketing and
>>> bundling.
>>>
>>> Marketing is of course not ideal, and likely counterproductive on a
>>> number
>>> of measures, but at least when a product is marketed you get sales
>>> demos.
>>> Even if they are designed to make a product or collection look as
>>> good as
>>> possible, it still gives you some sense of scale, quality, content, etc.
>>>
>>> I think bundling is probably more important. It's a challenge in the
>>> free-stuff realm, but for open access products where there is
>>> bundling (for
>>> instance, Directory of Open Access Journals) I think you are likely
>>> to see
>>> wider adoption.
>>>
>>> Bundling can of course be both good (lower management cost) and bad
>>> (potentially diluting collection quality for your target audience).
>>> But when
>>> there isn't any bundling, which is true for a whole lot of free stuff,
>>> you've got to locally gather a million little bits into a collection.
>>>
>>> I guess what's really happening in the bundling case, at least for free
>>> content, is that collection and quality management activities are being
>>> "outsourced" to a third party. This is probably why DOAJ gets decent
>>> adoption. But of course, this still requires SOME group to be willing to
>>> perform these activities, and for the content/package to remain free,
>>> they
>>> either have to get some kind of outside funding (e.g., donations) or be
>>> willing to volunteer their services.
>>>
>>
>>

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