<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Verdana",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        font-family:"Calibri",sans-serif;
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:147018698;
        mso-list-template-ids:2115654248;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:72.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:108.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:144.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:180.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:216.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:252.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:288.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:324.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:954091718;
        mso-list-type:hybrid;
        mso-list-template-ids:445054590 -1981512974 68354051 68354053 68354049 68354051 68354053 68354049 68354051 68354053;}
@list l1:level1
        {mso-level-start-at:0;
        mso-level-number-format:bullet;
        mso-level-text:-;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Verdana",sans-serif;
        mso-fareast-font-family:"Times New Roman";
        mso-bidi-font-family:"Times New Roman";}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Symbol;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:"Courier New";}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NL" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I do see some other flaws:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormal" style="color:#1F497D;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">If I understand this well, it will only work for publications that have a doi. Unfortunately
 that is not the case for every e-publication, and not every discovery layer has got the doi for each publication in its meta data<o:p></o:p></span></li><li class="MsoNormal" style="color:#1F497D;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">It only works for publishers and integrators that support federated authentication and
 will join the common GFTR environment. Harder to implement for small publishers<o:p></o:p></span></li><li class="MsoNormal" style="color:#1F497D;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">It only seems to work in discovery layers that themselves support Federated authentication,
 since they have tp provide the user affiliation to the GFTR API’s. I do not think that Google Scholar will give up authenticating by google over authenticating by distributed Identity providers.<o:p></o:p></span></li><li class="MsoNormal" style="color:#1F497D;mso-list:l1 level1 lfo3"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">Will it be easy to join the GFTR environment ? Not only for aggregators and small publishers
 but also for libraries to for example offer links to content in their repositories for example<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">     
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black">Drs. P.J.C. van Boheemen</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">    
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">MDT Library<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">     FB – Information Technology
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">     Wageningen University & Research<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">    
</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">tel. +31 317 48 25 17<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">     FORUM, building 102
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D">     Droevendaalseseteeg 2, 6708 PB, Wageningen<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">    </span><span lang="EN-GB" style="color:#1F497D"><img width="260" height="57" style="width:2.7083in;height:.5937in" id="Picture_x0020_1" src="cid:image001.png@01D5AB57.FB01EED0" alt="cid:image001.png@01D3315D.FE77CCE0"></span><span lang="EN-GB" style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> FIM4L <fim4l-bounces@lists.daasi.de>
<b>On Behalf Of </b>Lisa Hinchliffe<br>
<b>Sent:</b> donderdag 5 december 2019 12:53<br>
<b>To:</b> Bernd Oberknapp <bo@ub.uni-freiburg.de><br>
<b>Cc:</b> fim4l@lists.daasi.de<br>
<b>Subject:</b> Re: [Fim4l] Fwd: GetFTR<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">As I understand it, GetFTR is not a user facing tool. A user won't have any control over whether there are GFTR links in the tool they are using any more than they control any other aspects of what an interface presents
 to them.  From what I read, any discovery layer (what GFTR is calling a technology integration partner) will eventually be able to turn on GFTR links using the APIs. So, beyond Dimensions, Mendeley, etc. in the early pilot, GFTR links could eventually appear
 in Google Scholar (if Google wanted them to), in library subscribed databases (beyond Dimensions), in A&I services, in citation management tools, on ResearchGate, etc. <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">The issue of aggregator content and GFTR is not whether the aggregators might turn on GFTR links (which they may) but that aggregator hosted content is currently not able to be a target for a GFTR link. So, if the library
 doesn't have the content from the publisher directly, the GFTR link will convey to the user that the library does not have it ... even if it does on an aggregator. Some of us suspect that while libraries will see this as a flaw in GFTR, the publishers will
 see this as a feature and so this "limitation" (to use Roger's term in the SK post) is likely to persist.<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Lisa<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">___<br>
<br>
Lisa Janicke Hinchliffe<br>
</span><a href="mailto:lisalibrarian@gmail.com" target="_blank"><span lang="EN-US">lisalibrarian@gmail.com</span></a><span lang="EN-US"><br>
<br>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">On Wed, Dec 4, 2019 at 3:58 PM Bernd Oberknapp <</span><a href="mailto:bo@ub.uni-freiburg.de"><span lang="EN-US">bo@ub.uni-freiburg.de</span></a><span lang="EN-US">> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Using just the entitlement information from the publishers' websites
<br>
isn't sufficient, since many full texts are licensed on other platforms, <br>
especially aggregators like EBSCO or ProQuest. So unless aggregators <br>
take part (which seems very unlikely for EBSCO and ProQuest since they <br>
have their own discovery platforms) or link resolvers are integrated, <br>
users won't have access to large parts of the licensed content via <br>
GetFTR. Google Scholar covers lots of publishers, also provides access <br>
to free versions and integrates link resolvers, so I'm wondering why <br>
users should switch from Google Scholar (or a discovery tool provided by <br>
the library) to GetFTR?<br>
<br>
Best regards,<br>
Bernd<br>
<br>
<br>
On 04.12.19 16:51, Lisa Hinchliffe wrote:<br>
> Riger Schonfeld has a great piece on this in SK yesterday ....<br>
> </span><a href="https://scholarlykitchen.sspnet.org/2019/12/03/publishers-announce-plug-leakage/" target="_blank"><span lang="EN-US">https://scholarlykitchen.sspnet.org/2019/12/03/publishers-announce-plug-leakage/</span></a><span lang="EN-US"><br>
> <br>
> I'd love to see a demo. Its hard to conceptualize from just text!<br>
> <br>
> Lisa Janicke Hinchliffe<br>
> </span><a href="mailto:lisalibrarian@gmail.com" target="_blank"><span lang="EN-US">lisalibrarian@gmail.com</span></a><span lang="EN-US"><br>
> <br>
> On Wed, Dec 4, 2019, 9:15 AM Jiri Pavlik <</span><a href="mailto:jiri.pavlik@mzk.cz" target="_blank"><span lang="EN-US">jiri.pavlik@mzk.cz</span></a><span lang="EN-US">> wrote:<br>
> <br>
>> Dear all,<br>
>><br>
>> you may like to check Get Full Text Research (GetFTR) -<br>
>>      </span><a href="https://www.getfulltextresearch.com/" target="_blank"><span lang="EN-US">https://www.getfulltextresearch.com/</span></a><span lang="EN-US"><br>
>><br>
>> It seems that American Chemical Society, Elsevier, Taylor & Francis and<br>
>> Wiley<br>
>> are going to rollout Seamless access sign in button and WAYF soon.<br>
>> Springer Nature<br>
>> already implemented it at Nature.com platform.<br>
>><br>
>> Would you like to share comment on that, Chris? :-)<br>
>><br>
>> Best regards<br>
>><br>
>>                       Jiri<br>
>> _______________________________________________<br>
>> FIM4L mailing list<br>
>> </span><a href="mailto:FIM4L@lists.daasi.de" target="_blank"><span lang="EN-US">FIM4L@lists.daasi.de</span></a><span lang="EN-US"><br>
>> </span><a href="http://lists.daasi.de/listinfo/fim4l" target="_blank"><span lang="EN-US">http://lists.daasi.de/listinfo/fim4l</span></a><span lang="EN-US"><br>
>><br>
> <br>
> <br>
> _______________________________________________<br>
> FIM4L mailing list<br>
> </span><a href="mailto:FIM4L@lists.daasi.de" target="_blank"><span lang="EN-US">FIM4L@lists.daasi.de</span></a><span lang="EN-US"><br>
> </span><a href="http://lists.daasi.de/listinfo/fim4l" target="_blank"><span lang="EN-US">http://lists.daasi.de/listinfo/fim4l</span></a><span lang="EN-US"><br>
> <br>
<br>
<br>
-- <br>
Bernd Oberknapp<br>
Gesamtleitung ReDI<br>
<br>
Albert-Ludwigs-Universität Freiburg<br>
Universitätsbibliothek<br>
Platz der Universität 2 | Postfach 1629<br>
D-79098 Freiburg        | D-79016 Freiburg<br>
<br>
Telefon:  +49 761 203-3852<br>
Telefax:  +49 761 203-3987<br>
E-Mail:   </span><a href="mailto:bo@ub.uni-freiburg.de" target="_blank"><span lang="EN-US">bo@ub.uni-freiburg.de</span></a><span lang="EN-US"><br>
Internet: </span><a href="http://www.ub.uni-freiburg.de" target="_blank"><span lang="EN-US">www.ub.uni-freiburg.de</span></a><span lang="EN-US"><br>
<br>
_______________________________________________<br>
FIM4L mailing list<br>
</span><a href="mailto:FIM4L@lists.daasi.de" target="_blank"><span lang="EN-US">FIM4L@lists.daasi.de</span></a><span lang="EN-US"><br>
</span><a href="http://lists.daasi.de/listinfo/fim4l" target="_blank"><span lang="EN-US">http://lists.daasi.de/listinfo/fim4l</span></a><span lang="EN-US"><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</body>
</html>