[OJS] | Native XML - Import Errors

Software Support
, , ,
1

Describe the issue or problem

We have tried to upload with both the OJS interface, and with commands in the command line. After both methods, on the surface, issue galleys were not shown. Errors were not reported in the interface, but were reported in the log when using command line (see picture attached below). We have also tried to import with exported XML files from older issues already imported previously, and on a new OJS installation. The same errors were seen.

Here is a list of things we have tried, which consistently produced the same results:
In our production installation

  1. Import new XML file
  2. Import new XML file without galleys
  3. Export an older issue with Native XML, re-import the file

In a brand new OJS installation

  1. Import new XML file
  2. Import new XML file without galleys

Steps I took leading up to the issue
With OJS interface

  1. Login with User/Role ‘Journal Manager’
  2. Navigate to ‘Tools’ then ‘Native XML Plugin’ for import
  3. Upload your XML file
  4. Import

With command line

  1. In ‘tools’ folder of the journal
  2. use command: php importExport.php NativeImportExportPlugin import <xml_file_path> <journal_path> <user_name>

What application are you using?
OJS 3.3.0.20

Additional information
When importing using the interface, no error was reported and the import was shown as successful. However galleys for the issue are not showing.

When importing using command line, an exception was reported multiple times: (also see attached image)
Exception: Filter output validation failed, expected “classes.publication.Publication”, but found “array” in /var/www/html/lib/pkp/classes/filter/Filter.inc.php:459\nStack trace:\n#0 /var/www/html/lib/pkp/plugins/importexport/native/filter/NativeXmlSubmissionFilter.inc.php(185): …

Results were consistent when attempting to import an XML file of previous issues exported from Native XML itself. We have attempted on a fresh OJS installation and the same issues remained.

ojs_bug_report
ojs_bug_report1141×296 202 KB

2

Hi @c.ho, what version of OJS was the XML file you are trying to import into 3.3. generated by? The Native XML format changes with each major version; for example, you can not import an XML file generated with 3.2 into a 3.3 install without editing the XML. Here’s a sample of the XML format expected for 3.3 for reference.

3

Thanks for the reply.
The file was generated for 3.3. Previously before the latest update to 3.3.0.20, the version was 3.3.0.16 though the same error showed up.
The XML file was also validated against the XSD files that came with 3.3.0.20.

Do you have other suggestions for things we can check?

4

Hi @c.ho, thanks for your patience - I was able to reproduce the issue you had using our sample data (with an added issue galley), and found it did not import the issue galley in 3.3 (but did work correctly in 3.4). I’ll look into this further and try to find a solution, but it may take some time as our team is busy preparing for our upcoming 3.5 release.