On Thu, Mar 6, 2014 at 1:55 PM, helix84 <[email protected]> wrote:
> On Thu, Mar 6, 2014 at 12:43 PM, Thanos Kyritsis <[email protected]> wrote:
>> In version 4.0, I was affected by bugs DS-1445 and DS-1848 and it was
>> practically unusable.
>
> Hi Thanos, these are OAI provider (server) bugs, not OAI harvester (client).

Thanks for the quick response helix,

you are probably right, however the problem under 4.0 was that
whenever the harvester received the noRecordsMatch response, it set
the collection to Internal Errors and refused to further harvest. I
was about to report that problem to this mailing list, but 4.1 was
already out, I performed my tests all over and that problem is
apparently gone.

> The provider and the harvester are actually separate and probably
> independent pieces of code in the DSpace codebase. The rest of the
> email implies that you're attempting to use the harvester, correct?

That is correct.

> Can you provide an example URL of a small OAI set which contains
> deleted items for testing?

There it is: http://eclass30-test.gunet.gr/modules/oai/oai2.php?verb=Identify

It is staged for 3 different datestamps:

- before 2014-03-06T12:42:41Z, 4 items are already present on the Data provider
- at 2014-03-06T12:42:41Z, 1 item is added (item 5) and 1 item is
updated/title renamed (item 3)
- at 2014-03-06T12:44:17Z, 1 item is deleted (item 2)


My tests include having the harvester rolling and trying to feed it:

- with noRecordsMatch (meaning nothing is changed on the Data
Provider, this is the one that failed in 4.0, but no longer fails)
- with additional/newly added records
- with updated records (changing the metadata and looking for proper
updating in dspace)
(up to this point dspace 4.1 fully succeeds)

- with deleted records (currently fails)

when the above test works :-), the next (and final) test will be:
- make some deleted records re-appear

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to