Hi
I noticed that myself as well.
I tried expanding the date range (e.g., until=2016-01-05) and the next
page of results turns out to have only that one record for 2016-01-04,
before it starts to list records from the next day. So I suspect that
the record counters in the resumptionToken are simply not correct.
I doubt anyone actually uses those record counters, as nobody has
noticed this before :)
Regards,
Hussein Suleman
--
Hussein Suleman, PhD
Head of Department and Professor
Department of Computer Science, School of IT, University of Cape Town
www.husseinsspace.com
> (/completeListSize="4314"/ ), and only 1 thousand of them covered in the
> first request).
>
> Am I doing something incorrectly this time?
> понеділок, 10 травня 2021 р. о 16:55:34 UTC+3 hussein пише:
>
> Hi
>
> There is clearly something wrong in the code on our end; as it is
> creating mixed-resolution dates (for efficiency reasons) rather than
> consistent high-resolution dates.
>
> I will look at a fix for this when I have some time.
>
> For now, I have a quick workaround that does seem to work. Instead of
> using low-resolution dates in the initial request, use the
> second-resolution version, such as:
>
>
http://union.ndltd.org/OAI-PMH/?verb=ListRecords&metadataPrefix=oai_dc&from=2016-01-04T00:00:00Z&until=2016-01-04T23:59:59Z
>
>
> This will then return resumptionTokens such as:
> 2016-01-04T04:08:50Z!2016-01-04T23:59:59Z!!oai_dc!1564!4314!oai:union.ndltd.org:TW/092CSMU0012012
>
> and it seems those are handled properly by the server.
>
> Regards,
> Hussein Suleman
>
> --
> Hussein Suleman, PhD
> Head of Department and Professor
> Department of Computer Science, School of IT, University of Cape Town
>
www.husseinsspace.com <
http://www.husseinsspace.com>