OAI validation Error - XML

Hello,

I’m receiving the following error when I try to index a journal at the OAI Register:
Validating OAI at BASE OAI-PMH Validator (http://oval.base-search.net/ ) gives the error below:

Also when i want check validation in this URL - system report these errors:
http://www.openarchives.org/Register/ValidateSite

WARN Malformed response: mismatched tag at line 62, column 2, byte 4111 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187. . The most common reason for malformed responses is illegal bytes in UTF-8 streams (e.g. the inclusion of Latin1 characters with codes>127 without creating proper UTF-8 mutli-byte sequences). You might find the utf8conditioner, found on the OAI tools page helpful for debugging.

FAIL Failed to parse Identify response

FAIL ABORT: Failed to parse Identify response from server at base URL

Hi @mbabaei,

Would you have a plugin or modification that could be adding meta tags where they shouldn’t appear?

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

I don’t know exactly, i want check validation in Openarchives but i faced the above error,

I want just a way to solve this problem

Thank you very much

Hi @mbabaei,

Are you using any plugins like OpenAIRE or DRIVER?

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

Yes i use OpenAIRE plugin
but i faced above error !
what can i do for solving this problem

Hi @mbabaei,

What version of the plugin are you using?

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

<application>openAIRE</application>
<type>plugins.generic</type>
<release>1.2.0.0</release>
<date>2016-08-25</date>
<lazy-load>1</lazy-load>
<class>OpenAIREPlugin</class>

Hi @mbabaei,

Can you confirm whether disabling that plugin fixes the issue? There are newer releases of the OpenAIRE plugin in the Plugin Gallery that you might try. Note that we don’t maintain that plugin, however, and can only provide limited help. If you can confirm whether disabling that plugin fixes the issue (i.e. that the problem is caused by that plugin), I’d suggest contacting the author.

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

Are you sure that there is a new version of OpenAir! because i check the latest OJS version on PKP website (ojs-3.1.2-4) and that has the same version of me.

No, my problem was not solved
I disabled this plugin but the result was no different.

Hi @mbabaei,

The new version of OpenAIRE is in the Plugin Gallery.

So to confirm, disabling this plugin does not change the validation error message?

Thanks,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

At the first steps i updated the OpenAir plugin to 2.0.1.5
But i faced the same error after that i disabled the plugin but the result not changed.

Please help me

Hi @mbabaei,

I note that you seem to be having trouble with character sets, e.g. the warning:

[Tue Jan 14 14:35:34.197451 2020] [php7:notice] [pid 25174] [client 127.0.0.1:58942] PHP 13. unserialize() /home/xyz/project/ojs/lib/pkp/classes/db/DAO.inc.php:352, referer: http://ojs/index.php/index/admin/index

This means that the data in your database has changed encodings, which is usually caused by either a change to the encoding settings in config.inc.php or a backup/restore/migration process that modified the character set information in the database. It likely explains the problem here.

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

Your right, but i want find this record and solve that, do you have any idea?

Hi @mbabaei,

I would suggest looking at the output of the “Identify” request in your browser to see if you can identify the broken characters. I would definitely not recommend fixing them one at a time – in a large database you will never finish that work – but trying to find a way to process the entire database in a way that corrects the broken characters all at once. That’s more of a MySQL question than an OJS question, and the best way to figure it out is to determine how the bad characters got introduced (so that can be reversed).

Thanks,
Alec Smecher
Public Knowledge Project Team