[Fim4l] Fwd: GetFTR

[Lisa Hinchliffe]

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.

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.

Lisa

___

Lisa Janicke Hinchliffe
lisalibrarian at gmail.com





On Wed, Dec 4, 2019 at 3:58 PM Bernd Oberknapp <bo at ub.uni-freiburg.de>
wrote:

> Using just the entitlement information from the publishers' websites
> isn't sufficient, since many full texts are licensed on other platforms,
> especially aggregators like EBSCO or ProQuest. So unless aggregators
> take part (which seems very unlikely for EBSCO and ProQuest since they
> have their own discovery platforms) or link resolvers are integrated,
> users won't have access to large parts of the licensed content via
> GetFTR. Google Scholar covers lots of publishers, also provides access
> to free versions and integrates link resolvers, so I'm wondering why
> users should switch from Google Scholar (or a discovery tool provided by
> the library) to GetFTR?
>
> Best regards,
> Bernd
>
>
> On 04.12.19 16:51, Lisa Hinchliffe wrote:
> > Riger Schonfeld has a great piece on this in SK yesterday ....
> >
> https://scholarlykitchen.sspnet.org/2019/12/03/publishers-announce-plug-leakage/
> >
> > I'd love to see a demo. Its hard to conceptualize from just text!
> >
> > Lisa Janicke Hinchliffe
> > lisalibrarian at gmail.com
> >
> > On Wed, Dec 4, 2019, 9:15 AM Jiri Pavlik <jiri.pavlik at mzk.cz> wrote:
> >
> >> Dear all,
> >>
> >> you may like to check Get Full Text Research (GetFTR) -
> >>      https://www.getfulltextresearch.com/
> >>
> >> It seems that American Chemical Society, Elsevier, Taylor & Francis and
> >> Wiley
> >> are going to rollout Seamless access sign in button and WAYF soon.
> >> Springer Nature
> >> already implemented it at Nature.com platform.
> >>
> >> Would you like to share comment on that, Chris? :-)
> >>
> >> Best regards
> >>
> >>                       Jiri
> >> _______________________________________________
> >> FIM4L mailing list
> >> FIM4L at lists.daasi.de
> >> http://lists.daasi.de/listinfo/fim4l
> >>
> >
> >
> > _______________________________________________
> > FIM4L mailing list
> > FIM4L at lists.daasi.de
> > http://lists.daasi.de/listinfo/fim4l
> >
>
>
> --
> Bernd Oberknapp
> Gesamtleitung ReDI
>
> Albert-Ludwigs-Universität Freiburg
> Universitätsbibliothek
> Platz der Universität 2 | Postfach 1629
> D-79098 Freiburg        | D-79016 Freiburg
>
> Telefon:  +49 761 203-3852
> Telefax:  +49 761 203-3987
> E-Mail:   bo at ub.uni-freiburg.de
> Internet: www.ub.uni-freiburg.de
>
> _______________________________________________
> FIM4L mailing list
> FIM4L at lists.daasi.de
> http://lists.daasi.de/listinfo/fim4l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.daasi.de/pipermail/fim4l/attachments/20191204/f4ee501a/attachment.html>