Hi Lewatle,
We recently experienced similar problems to yours, which prevented external 
harvesters from receiving our complete OAI feed. We discovered that a number of 
records caused the OAI XML to become malformed, because of “foreign” 
characters, etc. Once we have identified those records (only 9 records), we 
edited each records in DSpace. Thereafter, we executed the command “bin/dspace 
oai import”, which corrected the changed records in the OAI database and cache.

If you delete records, you may have to run the following commands to rebuild 
your OAI indexes:
bin/dspace oai clean-cache
bin/dspace oai import -c

Hope this helps!
Regards,
David
From: [email protected] <[email protected]> On 
Behalf Of Lewatle Johannes Phaladi
Sent: Tuesday, 19 February 2019 11:28 AM
To: DSpace Community <[email protected]>
Subject: [dspace-community] Re: DSpace: Harvesting Error

Hi David and Colleagues,

I have re-indexed discovery with -d, re-imported oai with -o and restarted 
tomcat then retried to harvest collection on our test server, I got error 
complaining about 
https://hdl.handle.net/10539/26028<https://protect-za.mimecast.com/s/O17gCzm4GXCKXAvNuooziw>
 , the item in question I have deleted from the system after receiving error 
and re-inxexed again but it is still coming on root cause of the oai error, is 
there any way harvester can by pass this item. I have also attached another 
error messages.

Regards,
Lewatle

On Wednesday, 13 February 2019 09:43:36 UTC+2, Lewatle Johannes Phaladi wrote:
Hi DSpace Colleagues,

When I tested my harvesting settings DSpace says settings are valid, but when 
other repositories harvesting our side tries to harvest they get error messages 
attached, on another attachment i just put screenshot of test I have done on 
our dev dspace trying to harvest collection from Prod Dspace site,   TXT 
document contains error received when running import on another dspace system 
as test. Your advise on this error is much appreciated!

Regards,
Lewatle
--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: 
https://duraspace.org/about/policies/code-of-conduct/<https://protect-za.mimecast.com/s/vHYlCAnX51ijxzMJfMYsE2>
---
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To post to this group, send email to 
[email protected]<mailto:[email protected]>.
Visit this group at 
https://groups.google.com/group/dspace-community<https://protect-za.mimecast.com/s/UkOcCBgX56fvxO3JtvQ605>.
For more options, visit 
https://groups.google.com/d/optout<https://protect-za.mimecast.com/s/nggFCDRZ58iX7kQrcBQkJ2>.
Disclaimer - University of Cape Town This email is subject to UCT policies and 
email disclaimer published on our website at 
http://www.uct.ac.za/main/email-disclaimer or obtainable from +27 21 650 9111. 
If this email is not related to the business of UCT, it is sent by the sender 
in an individual capacity. Please report security incidents or abuse via 
https://csirt.uct.ac.za/page/report-an-incident.php.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to