Olá a todos. Estamos tentando fazer o registro do OAI de nossa revista mas estamos enfrentando diversos erros na segunda etapa da validação. Validando via esse site e esse aparentemente está tudo OK. Mas recebemos um e-mail com diversos erros na validação. Verificamos que estamos com todos os plugins atualizados. OJS 3.3.0.13
1 curtida
Olá @Leonardo_Rodrigues ,
Uma coisa que não entendi em que site ou /e indexador que vc está tendo validar o oai da sua revista.
Quais são os erros que esse validador está apresentando?
Tem como partilhar esses logs?
1 curtida
Olá @diegojmacedo,
Estamos tentando fazer o registro de nossa revista via OAI-MPH. E estamos recebendo o seguinte log na segunda etapa do registro. Apesar da primeira etapa ocorrer sem nenhum erro. Verificamos e seguimos toda a documentação para configuração na revista. Constantemente temos problemas com comunicação externa, por conta de um protocolo de segurança do servidor onde a revista está. Porém, neste caso, não estamos encontrando mais nenhuma solução. Segue abaixo os logs de erro:
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Tried empty set, will look for set with items...
NOTE Trying set &set=cadernos:EXP
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:EXP GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:EDI
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:EDI GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:ART
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:ART GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:ARTREV
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:ARTREV GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:COMBREVE
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:COMBREVE GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:JURIS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:JURIS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:RES
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:RES GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:AP
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:AP GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:PERHIST
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:PERHIST GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:PERBIO
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:PERBIO GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:PERINOV
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:PERINOV GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:PERINTER
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:PERINTER GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:COL
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:COL GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DEC
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DEC GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:FOR
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:FOR GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:CAREDIT
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:CAREDIT GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:ANAIS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:ANAIS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DIS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DIS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:LSC
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:LSC GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DECL
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DECL GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:PDS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:PDS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DBR
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DBR GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:SCD
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:SCD GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:LS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:LS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:JDS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:JDS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:MST
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:MST GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:OPG
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:OPG GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:CSD
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:CSD GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:CTISDS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:CTISDS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:EM
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:EM GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DIDS
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DIDS GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DSI
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DSI GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:OUT
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:OUT GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:COMOR
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:COMOR GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:RES
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:RES GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:LEGCOM
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:LEGCOM GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:DJSC
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:DJSC GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=cadernos:Anais
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:Anais GET
WARN Malformed response: junk after document element at line 2, column 0, byte 7 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 response
NOTE Trying set &set=driver
REQUEST https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=driver GET
1 curtida
Prezado @Leonardo_Rodrigues ,
A princípio o problema está relacionado com display_errors configurado no servidor. O servidor está exibindo uma mensagem de notice no navegador.
Desse modo tem uma saída html misturada com o xml. No protocolo OAI a resposta tem que ser sempre em xml. Desse modo, o display_errors tem que está desabilitado para não exibir o NOTICE da página.
Para verificar o problema, acesse a url oai , por exemplo :
https://www.cadernos.prodisa.fiocruz.br/index.php/cadernos/oai?verb=ListIdentifiers&metadataPrefix=oai_dc&set=cadernos:ARTREV
aperte Ctrl + u, para acessar o código fonte da página e ver o problema.
1 curtida