Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atom API. Bug with parameter order=-updated or order=updated #95

Open
alexfromk opened this issue Oct 10, 2022 · 0 comments
Open

Atom API. Bug with parameter order=-updated or order=updated #95

alexfromk opened this issue Oct 10, 2022 · 0 comments

Comments

@alexfromk
Copy link

Hello,
we are working with National Archives API, by service Atom.
Our service run by pages of API Atom. It use request like https://caselaw.nationalarchives.gov.uk/atom.xml?page=1&order=-updated
All worked correctly up to 14:00GMT (not accurate)
After that time, requests, similar to
https://caselaw.nationalarchives.gov.uk/atom.xml?page=1&order=-updated
start retrive incorrect(empty) fields: updated,published,title,tna:contenthash.
For example:
<entry><title></title><link href="https://caselaw.nationalarchives.gov.uk/ewca/crim/2022/1062" rel="alternate"></link><published>1970-01-01T00:00:00+00:00</published><updated>1970-01-01T00:00:00+00:00</updated><author><name>HM Courts and Tribunals Service</name></author><id>https://caselaw.nationalarchives.gov.uk/ewca/crim/2022/1062&lt;/id&gt;&lt;summary type="html"></summary><tna:uri>ewca/crim/2022/1062</tna:uri><tna:contenthash></tna:contenthash></entry>

Such result we can get with any value of parameter page.
But the request similar to https://caselaw.nationalarchives.gov.uk/atom.xml?page=1&order=-date
work fine.
It looking like bug with service Atom with parameter order=-updated or order=updated
Could you fix, this problem.

With best regards. Alex Kononenko

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant