"Invalid document end"

[josipkp]

Hi,

Trying to register the URL OAI
http://www.portalseer.ufba.br/index.php ... poscom/oai (an OJS journal)
in our harvester2, we receive the message "Invalid document end" and the "Metadata Format" combobox is empty.
What could be wrong?

Executing the ListMetadataFormats verb, comes the usual answer for OJS journals: oai_dc, oai_marc, marcxml and rfc1807.
In plugins/harvesters/oai/OAIHarvester.inc.php, function getMetadataFormat, $aliases shows [0] => oai_dc, but $supportedFormats gives error:
Warning: array_intersect(): Argument #2 is not an array in /var/www/harvesterTeste/plugins/harvesters/oai/OAIHarvester.inc.php on line
and I can't see the metadataformtsXMLNode.

What I need to do to harvester this source?
Thanks in advance,
Josi Perez
http://www.univerciencia.org/

[asmecher]

Hi Josi,

It sounds like the data source is serving XML containing invalid characters. Try specifying the Identify and ListMetadataFormats verbs manually and validating the result -- you probably have to correct some invalid UTF8.

Regards,
Alec Smecher
Public Knowledge Project Team

[josipkp]

Hi,
No, manually no problem - I got answer for all questions, including:
http://www.portalseer.ufba.br/index.php ... fix=oai_dc

By the way, this source was harvested during a crontab script execution of "tools/php harvester"; all records, but the form continues to point null to the metadata formats and the script ends with the message "invalid document end".

Now I have problems to harvester two OCSs sites - sorry, looks like just me have problems to harvester... :
http://conferencias.ulusofona.pt/index. ... fix=oai_dc AND
http://eventos.univerciencia.org/turism ... fix=oai_dc

in both I received the following message:
for ListRecords verb:
DB Error: Unknown column 't.identify_type' in 'field list'

for ListSets verb:
Fatal error: Call to undefined method TrackDAO::getConferenceTracks() in /home/lcm/public_html/conferencias.ulusofona.pt/classes/oai/ocs/OAIDAO.inc.php on line 515

Could you help?
Thank you,
Josi Perez
http://www.univerciencia.org/

[asmecher]

Hi Josi,

The patch for bug #4900 at http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=4900 should help you with part of this, but only part. What version of OCS are you using?

For the earlier problem, the tip-off that something is generating invalid XML is the "Invalid document end" error. This comes from the XML parser. If you haven't tried yet, I'd suggest running a few OAI request results through an XML validator to make sure they can be parsed (even if they look OK).

Regards,
Alec Smecher
Public Knowledge Project Team