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