<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi John,<div class=""><br class=""></div><div class="">Thanks for the link to this article. I like your suggestions. Something that publishers can do in this area was articulated at the Researcher 2 Reader conference:</div><div class=""><span style="color: rgb(20, 20, 18); font-family: 'PT Sans', Helvetica, sans-serif; font-size: 16px; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="color: rgb(20, 20, 18); font-family: 'PT Sans', Helvetica, sans-serif; font-size: 16px; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class="">"This comment was responded with</span><strong style="box-sizing: border-box; color: rgb(20, 20, 18); font-family: 'PT Sans', Helvetica, sans-serif; font-size: 16px; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""> a call out to publishers to make the information about sharing more accessible to authors through <a href="http://www.howcanishareit.com/" style="box-sizing: border-box; color: rgb(188, 54, 10); text-decoration: none;" class="">How Can I Share It</a></strong><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font color="#141412" face="PT Sans, Helvetica, sans-serif" size="3" class="">?” </font></span></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font color="#141412" face="PT Sans, Helvetica, sans-serif" size="3" class=""><br class=""></font></span></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font color="#141412" face="PT Sans, Helvetica, sans-serif" size="3" class="">The link to How Can I Share It? is - </font></span><a href="http://www.howcanishareit.com/" class="">http://www.howcanishareit.com/</a></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font color="#141412" face="PT Sans, Helvetica, sans-serif" size="3" class="">The link to the blog post I wrote about the conference is here - </font></span><a href="https://unlockingresearch.blog.lib.cam.ac.uk/?p=1316" class="">https://unlockingresearch.blog.lib.cam.ac.uk/?p=1316</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">On a related note, Jason Priem posted the below to the SCHOL COMM list this morning:</div><div class=""><br class=""></div><div class="">Hi all,<br class="">Our nonprofit is pre-releasing a sweet open-source OA tool, and thought the<br class="">list might be interested:<br class=""><br class="">It's called Unpaywall, and it links you to legal, open-access fulltext as you<br class="">browse research articles, letting you bypass paywalls. It draws from an index<br class="">of 10M+ OA articles [1] harvested from IRs, preprint repositories, OA<br class="">journals, and so on.<br class=""><br class="">The idea is quite similar to the very cool Open Access Button, but with a UI<br class="">that's aimed at a broader audience. We've had good luck so far with that:<br class="">we've passed 1500 installations in our first four days, and the announcement<br class="">tweet has more than 500 retweets.<br class=""><br class="">Using Unpaywall, readers in many fields can now find fulltext on a majority of<br class="">scholarly articles, even with zero subscription access. For instance, we [2]<br class="">looked at news stories published in 2016 with “cancer” in their headlines that<br class="">contained a link to a research article. Of the 11k articles examined, nearly<br class="">half were available using Unpaywall--despite most of them being paywalled.<br class=""><br class="">We hope that getting this extension out to people can be a major step forward<br class="">for Open Access, by inserting OA directly at the point of need--bridging the<br class="">gap between the IR and user's workflow.<br class=""><br class="">We'd love to hear your thoughts! Check it out here: <a href="http://unpaywall.org" class="">http://unpaywall.org</a><br class="">Best,<br class="">Jason<br class=""><br class="">[1] we'll be releasing all of these as an open dataset later this month<br class="">[2] together with Juan Alperin from Simon Fraser University.<br class=""><div><blockquote type="cite" class=""><div class="">On 15 Mar 2017, at 12:00, <a href="mailto:goal-request@eprints.org" class="">goal-request@eprints.org</a> wrote:</div><br class="Apple-interchange-newline"><div class="">Send GOAL mailing list submissions to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:goal@eprints.org" class="">goal@eprints.org</a><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal<br class="">or, via email, send a message with subject or body 'help' to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>goal-request@eprints.org<br class=""><br class="">You can reach the person managing the list at<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>goal-owner@eprints.org<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of GOAL digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. Facilitating Discovery of Open Content (John G. Dove)<br class=""> 2. Re: Facilitating Discovery of Open Content (John G. Dove)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Tue, 14 Mar 2017 16:14:56 -0400<br class="">From: "John G. Dove" <johngdove@gmail.com><br class="">Subject: [GOAL] Facilitating Discovery of Open Content<br class="">To: "Global Open Access List (Successor of AmSci)" <goal@eprints.org><br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CABLCZ9kc5BrrK4su2dvRix9VEkQk1ehx7bM-_GvaJ=yHmv9bbQ@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">All,<br class=""> *Learned Publishing*, the journal of the Association of Learned and<br class="">Professional Society Publishers, devoted their January Issue to the topic<br class="">of Discovery.<br class=""> The publisher has now opened up that issue well before the usual<br class="">embargo period would have dictated. So now everyone care read any of the<br class="">articles in that issue. The Table of Contents is at:<br class=""><br class="">Learned Publishing January 2017 issue on "Discovery"<br class=""><http://onlinelibrary.wiley.com/doi/10.1002/leap.2017.30.issue-1/issuetoc><br class=""><br class=""> I thought readers of G.O.A.L. might be interested in the opinion piece<br class="">I was invited to write on Discovery Issues as it relates to Open Content.<br class="">I based my piece on work that the NISO Discovery to Delivery Topic<br class="">Committee has been doing to identify unnecessary friction between someone's<br class="">desire to share content with the world (an author, a publisher, an<br class="">institution) and all the various ways in which users seek out information<br class="">and would be glad to discover such shared content.<br class=""><br class=""> Full discovery: What is the publisher's role?<br class=""><http://onlinelibrary.wiley.com/doi/10.1002/leap.1086/full><br class=""><br class=""> Since this journal is for publishers I focused on things that<br class="">publishers could do to facilitate access to various forms of shared<br class="">content. In particular, I propose the development of what I call an<br class="">"OA-smart-link" not unlike the Link-Resolvers which facilitate access to<br class="">licensed content in libraries. Such a link could be provided after<br class="">citations and give the reader one or two click access to the most<br class="">accessible version of that article for that user.<br class=""><br class=""> I'll be most interested in thoughts, ideas, reactions.<br class=""><br class="">-john dove<br class="">_________________<br class="">John G. Dove, personal e-mail<br class="">JohnGDove@gmail.com<br class=""><br class="">Check out my post from 2015 on LinkedIn: Ways to systematically message<br class="">scholars and researchers about Open Access<br class=""><https://www.linkedin.com/pulse/accelerating-open-access-adoption-john-dove?published=t><br class="">-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: http://mailman.ecs.soton.ac.uk/pipermail/goal/attachments/20170314/ef143c9f/attachment-0001.html <br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Tue, 14 Mar 2017 16:35:32 -0400<br class="">From: "John G. Dove" <johngdove@gmail.com><br class="">Subject: Re: [GOAL] Facilitating Discovery of Open Content<br class="">To: "Global Open Access List (Successor of AmSci)" <goal@eprints.org><br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CABLCZ9m7EgyT6Z_9PfZ47wikTJur7nym2phAxi6A8ngRniXnTA@mail.gmail.com><br class="">Content-Type: text/plain; charset="utf-8"<br class=""><br class="">Sorry, just noticed a typo.<br class=""><br class="">"now everyone care read" should be "now everyone can read".<br class=""><br class="">-john<br class=""><br class="">_________________<br class="">John G. Dove, personal e-mail<br class="">JohnGDove@gmail.com<br class=""><br class="">Check out my latest post on LinkedIn: Not all Open Content is fully<br class="">Discoverable<br class=""><https://www.linkedin.com/pulse/all-open-content-discoverable-john-dove?><br class=""><br class="">On Tue, Mar 14, 2017 at 4:14 PM, John G. Dove <johngdove@gmail.com> wrote:<br class=""><br class=""><blockquote type="cite" class="">All,<br class=""> *Learned Publishing*, the journal of the Association of Learned and<br class="">Professional Society Publishers, devoted their January Issue to the topic<br class="">of Discovery.<br class=""> The publisher has now opened up that issue well before the usual<br class="">embargo period would have dictated. So now everyone care read any of the<br class="">articles in that issue. The Table of Contents is at:<br class=""><br class="">Learned Publishing January 2017 issue on "Discovery"<br class=""><http://onlinelibrary.wiley.com/doi/10.1002/leap.2017.30.issue-1/issuetoc><br class=""><br class=""> I thought readers of G.O.A.L. might be interested in the opinion piece<br class="">I was invited to write on Discovery Issues as it relates to Open Content.<br class="">I based my piece on work that the NISO Discovery to Delivery Topic<br class="">Committee has been doing to identify unnecessary friction between someone's<br class="">desire to share content with the world (an author, a publisher, an<br class="">institution) and all the various ways in which users seek out information<br class="">and would be glad to discover such shared content.<br class=""><br class=""> Full discovery: What is the publisher's role?<br class=""><http://onlinelibrary.wiley.com/doi/10.1002/leap.1086/full><br class=""><br class=""> Since this journal is for publishers I focused on things that<br class="">publishers could do to facilitate access to various forms of shared<br class="">content. In particular, I propose the development of what I call an<br class="">"OA-smart-link" not unlike the Link-Resolvers which facilitate access to<br class="">licensed content in libraries. Such a link could be provided after<br class="">citations and give the reader one or two click access to the most<br class="">accessible version of that article for that user.<br class=""><br class=""> I'll be most interested in thoughts, ideas, reactions.<br class=""><br class="">-john dove<br class="">_________________<br class="">John G. Dove, personal e-mail<br class="">JohnGDove@gmail.com<br class=""><br class="">Check out my post from 2015 on LinkedIn: Ways to systematically message<br class="">scholars and researchers about Open Access<br class=""><https://www.linkedin.com/pulse/accelerating-open-access-adoption-john-dove?published=t><br class=""><br class=""></blockquote>-------------- next part --------------<br class="">An HTML attachment was scrubbed...<br class="">URL: http://mailman.ecs.soton.ac.uk/pipermail/goal/attachments/20170314/4999ef31/attachment-0001.html <br class=""><br class="">------------------------------<br class=""><br class="">_______________________________________________<br class="">GOAL mailing list<br class="">GOAL@eprints.org<br class="">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal<br class=""><br class=""><br class="">End of GOAL Digest, Vol 64, Issue 11<br class="">************************************<br class=""></div></blockquote></div><br class=""><div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><br class="">Dr Danny Kingsley<br class="">Head, Office of Scholarly Communication<br class="">Cambridge University Library<br class="">West Road, Cambridge CB39DR<br class="">P: +44 (0) 1223 747 437<br class="">M: +44 (0) 7711 500 564<br class="">E: <a href="mailto:dak45@cam.ac.uk" class="">dak45@cam.ac.uk</a><br class="">T: @dannykay68<br class="">B: <a href="https://unlockingresearch.blog.lib.cam.ac.uk/" class="">https://unlockingresearch.blog.lib.cam.ac.uk/</a><br class="">S: <a href="http://www.slideshare.net/DannyKingsley" class="">http://www.slideshare.net/DannyKingsley</a><br class="">ORCID iD: 0000-0002-3636-5939</div><br class="Apple-interchange-newline"></div><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><img height="152" width="600" apple-inline="yes" id="FDF36B99-C410-4461-BC35-9F0D230D529D" apple-width="yes" apple-height="yes" src="cid:22F510D9-E4C1-4E38-B4B3-10556FD2ACD8" class=""></span>
</span></span></div>
<br class=""></div></body></html>