Our recent report by John Cox (http://www.alpsp.org/publications/pub9.htm)
may also be of interest (only the executive summary is freely available, I'm
afraid!)

 Sally

Sally Morris, Chief Executive
Association of Learned and Professional Society Publishers
South House, The Street, Clapham, Worthing, West Sussex BN13 3UU, UK

Phone:  +44 (0)1903 871686 Fax:  +44 (0)1903 871457
E-mail:  sally.morris@alpsp.org
ALPSP Website  http://www.alpsp.org

ALPSP Learned Journals Collection (in partnership with Swets)
awarded Best STM Information Product for 2004
(http://www.alpsp.org/ALJC/default.htm)
----- Original Message -----
> From: "Bogdanski, Elizabeth" <Elizabeth.Bogdanski@IL.PROQUEST.COM>
> To: <SERIALST@LIST.UVM.EDU>
> Sent: Thursday, March 03, 2005 6:33 PM
> Subject: Re: [SERIALST] full text access to journals through databases
>
>
>>I recently did some research on this subject and my bibliography is
>> below.  I think you will find it very helpful.
>>
>> Albanese, A. R. (2002). An LJ Round Table with the Aggregators, 127 (5).
>> Retrieved January 24, 2005, from WilsonWeb.
>>
>> Blosser, J., Lightman, H., McHugh, W.A., Ren, A. (2001).  Aggregator
>> Services Evaluation: Not and Easy Comparison, 41(1).  Retrieved January
>> 24, 2005, from Hawthorn Press Journals.
>>
>> Chambers, M.B., So, S. (2004).  Full-Text Aggregator Database Vendors
>> and Journal Publishers: A Study of a Complex Relationship, 30, 183-193.
>> Retrieved January 24, 2005, from ScienceDirect.
>>
>> Cummings, J. (2003).  Full-Text Aggregation: An Examination of Metadata
>> Accuracy and Implications for Resource Sharing, 29, 11-15.  Retrieved
>> January 24, 2005, from ScienceDirect.
>>
>> Rupp-Serrano, K., Robbins, S., Cain, D. (2002).  Canceling Print Serials
>> in Favor of Electronic: Criteria for Decision Making, 26, 369-378.
>> Retrieved January 24, 2005, from ScienceDirect.
>>
>> Tenopir, C. (2002).  Disappearing Databases, 127(20).  Retrieved January
>> 24, 2005, from WilsonWeb.
>>
>>
>> Beth Bogdanski
>> Library Holdings Consultant
>> ProQuest Information & Learning, UMI Division
>> 300 N. Zeeb Rd.
>> Ann Arbor, MI  48106
>> (734) 761-4700 x 3819
>> elizabeth.bogdanski@il.proquest.com
>> www.umi.com
>>
>>
>> -----Original Message-----
>> From: SERIALST: Serials in Libraries Discussion Forum
>> [mailto:SERIALST@LIST.UVM.EDU] On Behalf Of Mark L. Ferguson
>> Sent: Thursday, March 03, 2005 9:51 AM
>> To: SERIALST@LIST.UVM.EDU
>> Subject: [SERIALST] full text access to journals through databases
>>
>>
>> Dear serials listers:
>>
>>
>>
>> I have a question which I am sure someone out there has the answer to.
>> Has anyone done a study of how stable the lists of  journals that allow
>> full text access through our leasing arrangements with databases are?
>> Do these full text titles continue to come and go, or is there a stable
>> core that remains available making up the bulk of the offerings provided
>> by these databases?
>>
>>
>>
>> It is common knowledge that we only lease access to these titles, we
>> don't actually own them and there have been cases where publishers have
>> discontinued full text access to journal titles (Sage publishers is
>> probably the most notable in recent memory).  But I have never seen a
>> study documenting how often full journals are pulled from databases,
>> discontinuing full text access to these publications.
>>
>>
>>
>> My sense is that once a journal is included in a database's collection
>> of full text titles it generally stays there and that the lists of full
>> text journals available through various databases are much more stable
>> than are given credit for.  If anything, I would think these lists tend
>> to expand rather than shrink in terms of title coverage.   I have yet to
>> see or hear of any real documentation regarding this.  Does anyone know
>> of any recent studies on this?
>>
>>
>>
>> Mark
>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email
>> ______________________________________________________________________
>
>