deletes may not be handled by XPathEntityProcessor because it is
essentially a read tool. But you can of course write a transformer
which may do the delete.
On Wed, Feb 25, 2009 at 11:46 PM, Benjamin Liles
wrote:
> My interest in this is primarily in harvesting an OAI-PMH repository. I
> think I
My interest in this is primarily in harvesting an OAI-PMH repository.
I think I understand now how to have the last import date included in
the url.
What I'm still getting stuck on is how to handle the fact that the
repository will be handing back 'modified' records. This could be an
add,
On Wed, Feb 25, 2009 at 9:01 PM, Benjamin Liles wrote:
>>
>> 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 a
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.
J
you can share the details on how you were identifying deltas and what
are the methods you would like to make protected.
delta import necessarily does not need the entityprocessor to support
it. you can easily do delta-import with a full-import .
http://wiki.apache.org/solr/DataImportHandlerFaq#hea
On Wed, Feb 25, 2009 at 8:02 PM, Benjamin Liles wrote:
> I was looking at adding support to the XPathEntityProcessor for a
> DeltaImport by adding a new parameter, deltaUrl, in order to support
> harvesting from an OAI-PMH server into SOLR. I wasn't planning on bothering
> with getting commit acc
