Cool, does OAI-PMH expose a method identify deltas and deletions?
With OAI-PMH you can request items that have been modified in a date
range. The deletes in OAI-PMH will require some kind of a transformer
anyway because they appear as normal records with most of the metadata
missing.
Just a thought, would adding a deltaUrl confuse users because most
APIs do
not support delta? Another option (for your use-case) could be to add
another root entity specific for delta import only. DIH supports
indexing
one or more root entities independently of others.
Maybe there should be a different name for it, but I think it should
be fairly easy to explain that not all API's would support it.
Public methods come with a baggage because changes have to be
back-compatible across releases. But we can make methods public
which can be
useful to a large number of use-cases.
I wasn't thinking of public methods, but protected. It would be the
responsibility of the developer extending the class to keep their code
up to date with the latest API.
As mentioned in another e-mail. I may be trying to hard. I'm not sure,
but I just had a realization that I may be able to include the
parameters for the 'delta' in the baseUrl of an HttpDataSource and
that would solve all of my problems.
Benjamin Liles
Lead Software App Developer
Texas A&M University General Libraries
PH 979.862.4948 ex 122
bli...@library.tamu.edu
