For the record, I've clarified this with OCLC itself. It's exactly as Terry
Weese says.

Karen G. Schneider


> >>  Isn't sharing such records a no-no?
> No, OCLC's guidelines for transfer
> (http://www.oclc.org/support/documentation/worldcat/records/guidelines/def
> ault.htm) specifically give unrestricted transfer rights to libraries and
> non-commercial entities.  The Open Library is both.  It's a registered
> library in California and a non-profit.  So in either situtation, it's not
> a  problem.
>
> --TR
>
> *******************************************
> Terry Reese
> Cataloger for Networked Resources
> Digital Production Unit Head
> Oregon State University Libraries
> Corvallis, OR  97331
> tel: 541-737-6384
> email: [EMAIL PROTECTED]
> http: http://oregonstate.edu/~reeset
> *******************************************
>
> ________________________________
>
> From: Code for Libraries on behalf of Peter Murray
> Sent: Wed 2/6/2008 2:50 PM
> To: CODE4LIB@listserv.nd.edu
> Subject: Re: [CODE4LIB] Records for Open Library
>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Feb 5, 2008, at 12:11 PM, K.G. Schneider wrote:
> > Has your library considered contributing records to Open Library (
> > http://www.openlibrary.org/ )? If so I'd like to hear from you on or
> > off
> > list.
>
>
> How would that work?  Most of the records in OhioLINK are probably
> derived from OCLC Worldcat.  Isn't sharing such records a no-no?
>
>
> Peter
> - --
> Peter Murray                            http://www.pandc.org/peter/work/
> Assistant Director, New Service Development  tel:+1-614-728-3600;ext=338
> OhioLINK: the Ohio Library and Information Network        Columbus, Ohio
> The Disruptive Library Technology Jester                http://dltj.org/
> Attrib-Noncomm-Share   http://creativecommons.org/licenses/by-nc-sa/2.5/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFHqjmq4+t4qSfPIHIRAqggAKDGoUmRO/7tcmdTn7f8YEnaBTbhQQCfYSBy
> yJU+FrMcWRUGURJk29iDx5w=
> =CEg4
> -----END PGP SIGNATURE-----

Reply via email to