Sorry, I forgot to reply to the list. Here is a forward of my answer.
-Ralf
-------- Forwarded Message --------
Subject: Re: camel-oaipmh : quirks-mode
Date: Wed, 26 Aug 2020 16:12:03 +0200
From: Ralf Claussnitzer <ralf.claussnit...@slub-dresden.de>
To: Juan Segarra <juanksegar...@gmail.com>
Hi Juan,
sorry for the late reply, but I was offline for some time.
I'm not aware of any documentation on how specific OAI server
implementations are not according to spec. However, I've seen an example
in an internal system where the handling of resumption tokens is broken
(always delivers the same token for all pages). Another example affects
the from and to parameters, which cannot handle the granularity
advertised in the identify document. I assume there are many more.
In my opinion the camel-oaipmh component should not include all of the
possible quirks as they are specific and rare at the same time. So the
main feature would be that users can provide and configure strategies
(classes) to customize protocol actions to some extend without having to
touch the original code base. Over time quirk handling code could be
included. Providing the extensibility should be the design goal here.
Regards,
Ralf
On 8/17/20 6:07 AM, Juan Segarra wrote:
Hi all.
One of the suggestions that I received in my GSoC proposal was to add a
quirks-mode to the component. However, I could not find information about
this online.
I was wondering if you have any ideas, or if you know some public servers
that need such a feature, so I can test them and figure out how to add
this
feature to the camel-oaipmh component.
Best regards
Juan
