Hello. Please could you help me how to identify strange characters, in my dspace the same thing is happening to me and I want to debug the characters? How can I filter and identify the errors? and if it is by database or by the same dspace system?
El miércoles, 27 de febrero de 2019 a las 6:58:15 UTC-5, [email protected] escribió: > Hi David, > > I have I found unknown characters in description and abstract field where > our submitters copied and pasted metadata from word document to Dspace, I > have corrected one by one item running bin/dspace oai clean-cache, > bin/dspace oai import -c after cleaning individual item and harvesting to > dev site when getting harvest error i clicked link inside and find > identifier which direct me to item that has characters then i correct the > item and save updates then run the commands again and harvest again aftyer > deleting test community, at the end all 44 items found and cleared. I have > received confirmationfrom external harvester that they managed to harvest > all collection. > > Thank you very much for sharing solution. > > Regards, > Lewatle > > > On Wednesday, 20 February 2019 16:13:09 UTC+2, Lewatle Johannes Phaladi > wrote: >> >> Hi David, >> >> Thanks very much, I am now identifying many items with characters in the >> abstract where users copied and pasted to Dspace. I am busy removing them >> while harvesting on development and number of harvested items are >> increasing from 100 to 4574, I am hoping all will go well, i will let you >> know once all is completed or if there is new error. >> >> Regards, >> Lewatle >> >> On Tuesday, 19 February 2019 12:01:22 UTC+2, david.delacroes wrote: >>> >>> 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]. >>> To post to this group, send email to [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 <+27%2021%20650%209111>. 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 Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/3993f82f-8bc6-41ac-a6c2-ed88c81c71a8n%40googlegroups.com.
