<div dir="ltr">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. <div>
<br></div><div>A key part for any OCLC member is :</div><div><br></div><div><p style="margin:0px 0px 18px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;font-family:Helvetica,Arial,'Arial Unicode MS',sans-serif;line-height:21px;color:rgb(0,0,0)">
The WorldCat Rights and Responsibilities policy outlines OCLC members' rights to:</p><ul style="margin:0px 0px 18px 25px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;color:rgb(0,0,0);font-family:Helvetica,Arial,'Arial Unicode MS',sans-serif;line-height:21px">
<li style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background-color:transparent;list-style:disc outside">Transfer their data to individual scholars for their personal, academic or scientific research or study;</li>
<li style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background-color:transparent;list-style:disc outside">Transfer their data to library consortia and public agencies working on behalf of libraries;</li>
<li style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background-color:transparent;list-style:disc outside">Transfer their data to other libraries and educational, cultural or scholarly institutions, whether these institutions are members of OCLC or nonmembers;</li>
<li style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background-color:transparent;list-style:disc outside">Transfer their data to agents acting on their behalf.</li></ul><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="font-size:14px;line-height:21px"><br>
</span></font></div></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px">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."</span></font></div>
<div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br></span></font></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px">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.</span></font></div>
<div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br></span></font></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px">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. </span></font></div>
<div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br></span></font></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br>
</span></font></div><div><br></div><div><br></div><div><br></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br></span></font></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="line-height:21px"><br>
</span></font></div><div><font color="#000000" face="Helvetica, Arial, Arial Unicode MS, sans-serif"><span style="font-size:14px;line-height:21px"><br></span></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, May 12, 2014 at 4:56 PM, Yamil Suarez <span dir="ltr"><<a href="mailto:ysuarez@berklee.edu" target="_blank">ysuarez@berklee.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
This is a topic I briefly mentioned right before the April board<br>
meeting, that I was unable to attend. I was discussing new RDA OPAC<br>
functionality on Launchpad[1] with other community members. During<br>
this discussion the topic of sharing OCLC RDA records came up once<br>
again. since to correctly write RDA code for EG we need to have access<br>
to good RDA records. I wondered if we could somehow involve the SFC to<br>
helps us sort out what our are choices as a community to properly<br>
share OCLC records with each other for testing/development purposes.<br>
Thankfully in the meantime there are developers looking into getting<br>
locally made RDA records or from the the US library of congress, for<br>
developers to use for testing.<br>
<br>
Since my library is an OCLC customer, a couple of weeks ago, I put in<br>
a ticket asking if we could share a few dozen RDA MARC records with<br>
developers in the EG community. They responded with...<br>
<br>
"....<br>
There is a discussion of WorldCat record use at<br>
<a href="http://www.oclc.org/worldcat/community/record-use.en.html" target="_blank">http://www.oclc.org/worldcat/community/record-use.en.html</a> and the<br>
associated links,<br>
especially <a href="http://www.oclc.org/worldcat/community/record-use/policy/questions.en.html" target="_blank">http://www.oclc.org/worldcat/community/record-use/policy/questions.en.html</a>.<br>
If that information and<br>
the links don't address your question, please use the email link on<br>
that page to email <a href="mailto:recorduse@oclc.org">recorduse@oclc.org</a> with further questions.<br>
..."<br>
<br>
So perhaps before we discuss this at a meeting, I was wondering if<br>
someone could help me make sense of these links, with or without the<br>
SFC, to see what we can legally do with OCLC records.<br>
<br>
Thanks,<br>
Yamil<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Thanks,<br>
Yamil<br>
<br>
<br>
[1] <a href="https://bugs.launchpad.net/evergreen/+bug/1304462" target="_blank">https://bugs.launchpad.net/evergreen/+bug/1304462</a><br>
_______________________________________________<br>
eg-oversight-board mailing list<br>
<a href="mailto:eg-oversight-board@list.evergreen-ils.org">eg-oversight-board@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a><br>
</blockquote></div><br></div>