Hello all,

as the subject implies, I'm trying to put dspace's harvester feature
to good use (actually aggregate from various OAI-PMH Data Providers).

In version 4.0, I was affected by bugs DS-1445 and DS-1848 and it was
practically unusable.

I'm re-testing CRUD operations over OAI-PMH with version 4.1 and I can
say it successfuly handles most of the operations (no
changes/nomatchRecords, create/new and updates in metadata), but it is
not able to handle deletions. Particularly, when the harvester reads
the following OAI-PMH XML response (during ListRecords), it sets the
collection in Internal Error status and stops periodic harvest for it:

<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/
http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd";>
  <responseDate>2014-03-06T11:06:05Z</responseDate>
  <request verb="ListRecords" from="2014-03-06T11:02:48Z"
until="2014-03-06T11:05:49Z" metadataPrefix="oai_dc">myURL</request>
  <ListRecords>
    <record>
      <header status="deleted">
        <identifier>myID</identifier>
        <datestamp>2014-03-06T11:04:52Z</datestamp>
        <setSpec>mySpec</setSpec>
      </header>
    </record>
  </ListRecords>
</OAI-PMH>

(the timestamps are real, oai harvester runs with 1 minute frequency
and a heartBeat between 30 and 60 seconds, for testing purposes)

I think the above is a valid OAI-PMH response (using
http://validator.oaipmh.com/ for validation), however DSpace harvester
cannot handle it.

Is someone else affected by the same problem ? Is it a known issue ?
(I cannot see something relevant in JIRA when searching with "OAI
delete" keyword)

Should I report it in JIRA ?


Thank you in advance for your help.

------------------------------------------------------------------------------
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