Thanks for the update. It sounds as though from your comments and my testing that the Quotes RSS feed is very broken and won't be available for use in production for the foreseeable future.

As per your question, the Quotes RSS Feed is currently producing the following results:

Request 1 : https://permid.org/atom/quote?access-token=XXX&format=ntriples
Response 1 :

<feed xmlns="http://www.w3.org/2005/Atom" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/">; <title>Quote Feed</title> <link rel="next" href="https://api.thomsonreuters.com/permid/atom/quote&offset=50&length=50" /> <link rel="self" href="https://api.thomsonreuters.com/permid/atom/quote&offset=0&length=50" /> <link rel="first" href="https://api.thomsonreuters.com/permid/atom/quote&offset=0&length=16" /> <link rel="last" href="https://api.thomsonreuters.com/permid/atom/quote&offset=400&length=16" /> <author> <name>Open PermID</name> <uri>http://permid.org</uri> </author> <subtitle>From date(UTC) : 2018-05-25T22:27:32.000Z, To date(UTC) : 2018-05-30T22:27:31.000Z, Window : Offset = 0, Length = 50, out of 416 results.</subtitle> <id>https://api.thomsonreuters.com/permid/atom/quote</id>; <updated>2018-05-30T22:25:40Z</updated> <opensearch:totalResults>416</opensearch:totalResults>

Notes:
- "first" link is incorrect as it should contain length=50 not length = 16
- totalResults and last link are inconsistent with following response

Request 2 : https://permid.org/atom/quote?access-token=XXX&format=ntriples&offset=50&length=50
Response 2 :

<feed xmlns="http://www.w3.org/2005/Atom" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/">; <title>Quote Feed</title> <link rel="prev" href="https://api.thomsonreuters.com/permid/atom/quote&offset=0&length=50" /> <link rel="self" href="https://api.thomsonreuters.com/permid/atom/quote&offset=50&length=36" /> <link rel="first" href="https://api.thomsonreuters.com/permid/atom/quote&offset=0&length=36" /> <link rel="last" href="https://api.thomsonreuters.com/permid/atom/quote&offset=50&length=36" /> <author> <name>Open PermID</name> <uri>http://permid.org</uri> </author> <subtitle>From date(UTC) : 2018-05-25T22:32:12.000Z, To date(UTC) : 2018-05-30T22:32:11.000Z, Window : Offset = 50, Length = 50, out of 86 results.</subtitle> <id>https://api.thomsonreuters.com/permid/atom/quote</id>; <updated>2018-05-30T16:22:05Z</updated> <opensearch:totalResults>86</opensearch:totalResults>

Notes:

- "first" link is incorrect as it should contain length=50 not length = 36

- "last" link is different to Response 1
- totalResults now 86 not 400 as per Response 2
- Due to the small amount of data, no "next" link is present so unable to verify circular reference at this moment

I am unable to replicate this issue. My issue is different.

When I request https://permid.org/atom/quote?access-token=xxx, the next link returns correctly:

 <link rel="next" href="https://api.thomsonreuters.com/permid/atom/quote&offset=50&length=50" />

Then, when I request to https://api.thomsonreuters.com/permid/atom/quote?offset=50&length=50, the next link returns correctly:

<link rel="next" href="https://api.thomsonreuters.com/permid/atom/quote&offset=100&length=50" />

However, when I request to https://api.thomsonreuters.com/permid/atom/quote?offset=100&length=50, the next link returns incorrectly:

<link rel="next" href="https://api.thomsonreuters.com/permid/atom/quote&offset=50&length=17" />

I will contact the support team to verify it.

Hi Jirapongse,
Thanks for your help with this matter. I have seen the scenario you have raised also.
Regards,
David

Hi jirapongse.phuriphanvichai,

Has the support team verified this issue? If so, do you have a timeframe when it will be fixed?
Regards,
David

@david.snowsill

The development team is unable to reproduce the circular navigation with the next link. Are you still experiencing the circular navigation with the next link? If yes, please share all requests and responses.

For the issue about the incorrect next link, this issue has been identified with the underlying queries that results in different total counts being provided when different offsets are used, which then has a consequent impact on the pagination results. This will need to be an enhancement and the team will need to consider approach, solution design and implementation. At this point in time, we still don't have an estimated time when any change will be implemented, as this will be dependent on approach/design.

I will keep you updated on its progress.