[Eg-oversight-board] Agenda suggestion: Research if EG community can use OCLC records

[Rogan Hamby]

The document is interesting but fairly straight forward and it separates
out rights and privileges into two groups though it doesn't explicitly say
so.  One set of privileges is those of any OCLC members who may download
the records.  The rights are those of the members who create them.  Note,
I'm not arguing whether this document is right or wrong, merely how I read
it's (sometimes inferred) assertions.

A key part for any OCLC member is :

The WorldCat Rights and Responsibilities policy outlines OCLC members'
rights to:

   - Transfer their data to individual scholars for their personal,
   academic or scientific research or study;
   - Transfer their data to library consortia and public agencies working
   on behalf of libraries;
   - Transfer their data to other libraries and educational, cultural or
   scholarly institutions, whether these institutions are members of OCLC or
   nonmembers;
   - Transfer their data to agents acting on their behalf.


So, this would exclude (if enforceable, again not saying it's right, just
looking at what it says) use in Evergreen of any OCLC record.  However, and
this is a really big however, we next have the rights of the creators.
 Now, this doesn't preclude potential use but it's OCLC saying "other than
their use in OCLC and as outlined above we don't set the rules for the
records, that's up to the record creators, we don't own them."

OCLC does not say this is required but is encouraging release under an open
license, specifically the Open Data Commons by Attribution license.  A full
discussion of those responsibilities would be an email thread in it's own
right but essentially the idea is that in some non-trivial way that folks
are likely to see we could re-use OCLC records released under this license
if we attribute the source and license.  I think this could be done on a
record by record basis within the MARC.  We would need to identify those
rights grants and ownership on a case by case basis but I think of several
ways that might practically work.  We could probably leave implementation
for another discussion though.

However (again), we can not use the OCN, OCLC that consider that it's
property but that's the only part of the MARC record it's claiming
ownership of.










On Mon, May 12, 2014 at 4:56 PM, Yamil Suarez <ysuarez at berklee.edu> wrote:

> Hello,
>
> This is a topic I briefly mentioned right before the April board
> meeting, that I was unable to attend. I was discussing new RDA OPAC
> functionality on Launchpad[1] with other community members. During
> this discussion the topic of sharing OCLC RDA records came up once
> again. since to correctly write RDA code for EG we need to have access
> to good RDA records. I wondered if we could somehow involve the SFC to
> helps us sort out what our are choices as a community to properly
> share OCLC records with each other for testing/development purposes.
> Thankfully in the meantime there are developers looking into getting
> locally made RDA records or from the the US library of congress, for
> developers to use for testing.
>
> Since my library is an OCLC customer, a couple of weeks ago, I put in
> a ticket asking if we could share a few dozen RDA MARC records with
> developers in the EG community. They responded with...
>
> "....
> There is a discussion of WorldCat record use at
> http://www.oclc.org/worldcat/community/record-use.en.html and the
> associated links,
> especially
> http://www.oclc.org/worldcat/community/record-use/policy/questions.en.html
> .
>    If that information and
> the links don't address your question, please use the email link on
> that page to email recorduse at oclc.org with further questions.
> ..."
>
> So perhaps before we discuss this at a meeting, I was wondering if
> someone could help me make sense of these links, with or without the
> SFC, to see what we can legally do with OCLC records.
>
> Thanks,
> Yamil
>
>
>
>
>
>
>
>
> Thanks,
> Yamil
>
>
> [1] https://bugs.launchpad.net/evergreen/+bug/1304462
> _______________________________________________
> eg-oversight-board mailing list
> eg-oversight-board at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/eg-oversight-board/attachments/20140513/0f5eeb7f/attachment.html>