GetFTR

How backend API development helped streamline scholarly research

Harnessing API technology for entitlement checking and streamlined access to scholarly content

GetFTR (Get Full Text Research) is a backend API service developed by five scholarly publishers: American Chemical Society, Elsevier, Springer Nature, Taylor & Francis and Wiley in 2019.

Working collaboratively to address one of the largest researcher pain points, these publishers are collaborating on backend API development under the name GetFTR (Get Full Text Research), to streamline access to scholarly content from today’s wide array of discovery and collaboration services that are commonly used in the scientific research process, such as:

  1. Research Discovery Services, e.g. PubMed, Web of Science, Dimensions, SciFinder, Scopus etc.
  2. Library Discovery Systems, e.g. Primo, Alma, etc.
  3. Scholarly collaboration networks (SCNs), e.g. Mendeley, ResearchGate etc. 

When interacting with these services, researchers are often looking to find scholarly content relevant to their own research or that’s important for their collaboration with colleagues. However, finding and accessing such content is not always as easy as one might think. Some of the issues researchers have today, which GetFTR addresses, include:

  1. Time consuming authentication and access journeys to scholarly content
  2. A multitude of link options, suggesting access to full text but unclear upfront if that link will actually give them access
  3. Confusing access solutions while researcher is off campus
  4. Fully entitled users turning to pirated or outdated content, affecting the integrity of research, and negatively impacting article usage data, which is important for both publishers and librarians

To address this, the GetFTR API was developed with the goal of providing researchers with an improved user journey to scholarly content through:

  1. Streamlined Access: Signalling access, and minimising paywalls, authentication steps and “access denied” experiences for researchers accessing articles; 
  2. Collaboration and Simplified Workflow: Enabling discovery services and scholarly collaboration networks to provide streamlined access to the version of record of the article that researchers are entitled to, via their institution subscriptions;
  3. Level Playing Field: Creating a service for all publishers, discovery services and SCNs to participate in, with transparent governance;
  4. Global Standards: Accelerating global adoption of industry standards and use of common, open standards where possible.

The GetFTR initiative addressed this by asking Equal Experts to design and develop an API that functions as a direct bridge between research discovery services / collaboration networks and publisher platforms. This enables real-time subscription checking conducted by publishers, and fast links to content, removing unnecessary steps in the authentication process. 

It is the goal of the five initial founders to seek to include all scholarly and society publishers into the GetFTR ecosystem; therefore, the challenge for Equal Experts was that the infrastructure supporting the Entitlements API must be highly scalable to support end users worldwide, with a high volume of concurrent traffic. 

This case study is also available as a PDF

Download

  • 30

    partners across publishers, platforms and integrators

  • 5 billion

    entitlement checks

  • 800m

    links to high quality content

About GetFTR

GetFTR (Get Full Text Research) is a service founded by five scholarly publishers: American Chemical Society, Elsevier, Springer Nature, Taylor & Francis and Wiley. These publishers are collaborating for the purpose of streamlining access to scholarly content, reducing time taken to conduct research, and providing the researcher with up-to-date, trusted full-text, where their institution entitles them.

Harnessing API technology for entitlement checking and streamlined access to scholarly content

Researchers are increasingly using discovery services that are disconnected from publisher entitlements. This means that, when discovering articles, researchers are often unaware if their institution has provided access. This can lead to frustrating user journeys, with researchers clicking on article links, navigating publisher and aggregator websites to find out how to access content, only to be told at the very end that they do not have access.

Early research conducted by Equal Experts showed that researchers can click up to ten times before accessing an article. With GetFTR this is reduced to one click, or two if they haven’t yet signed in via their institution. When trying to read content across multiple publisher platforms, this increases the complexity as the researcher must authenticate for each platform.

Equal Experts developed a backend API that enables discovery tools to check entitlements at the article level directly with the publisher. Where the researcher’s institution subscribes, the researcher is provided with a GetFTR smartlink from within their discovery service, which takes them directly to the article. If the institution uses federated authentication, and the researcher isn’t already authenticated, they will be taken directly to their institution login page removing the need to navigate publisher websites. Additionally, they only need to authenticate once to access content from all participating publisher platforms.

Equal Experts also developed a Self-Service Portal providing a number of tools, to ensure the onboarding process was smooth for both publishers and integrators. We also developed a Demo Discovery Service to illustrate how GetFTR works, and to support Publisher and Integrator decisions on whether to come onboard.

Adopting a test and learn approach to improve through iteration

We started an initial 3 month engagement to deliver a functional prototype. GetFTR was pleased with the prototype and the contract was extended for an additional 9 months to support piloting and further development of the service.

There were some initial challenges with the distributed architecture and authentication options provided in version 1 of the API. Following the pilot, version 2 was released, which supported IP authentication alongside federated authentication. Additionally, Integrators could now send DOI entitlement requests in batches.

The service uses CloudFront Functions to operate right at the edge of the AWS network, which makes it massively scalable and highly fault-tolerant against outages affecting other parts of the AWS network. This was critical for a service that essentially acts as an intermediary between Discovery Services and Publishers with a huge volume of requests per second. CloudFront Functions operate in a severely reduced environment, with a lot of JavaScript features turned off. It also provided the reassurance of knowing there was no additional latency, as the maximum execution time of these functions is 1ms.

Demonstrating business value through scaling capacity

GetFTR now works with over 30 partners across publishers, platforms and integrators and to date has returned over 800m links to high quality content, providing researchers with streamlined access to content. GetFTR has just hit the 5 billion mark for entitlement checks.

“Today, GetFTR supports multiple use cases providing streamlined access to scholarly content on publisher platforms and aggregator platforms. It also facilitates access to syndicated content, where the publisher has agreed that content can be hosted locally.

In the last six months, GetFTR has seen an acceleration of Publishers and Integrators coming onboard, providing a valuable service to researchers and publishers, and ensuring users are provided with streamlined access to the version of record of the scholarly content they need.

Alongside further enhancing the API, demo discovery service and self-service portal, we are developing further services to meet the needs of our Integrators, including tools in the business to consumer space.”

 

Dianne Benham, who heads up product management for GetFTR, and brought in the Equal Experts team.

You might also like...

Want to know more?

Are you interested in this project? Or do you have one just like it? Get in touch. We'd love to tell you more about it.