Error importing XML files

Nardusg · January 29, 2018, 8:23am

Hi,

I am currently migration a system between servers, I have created a new install of OJS 2.4.8. From my understanding the origin server was running the same version.

When trying to import the XML files for the articles I get the following error.

An article title was missing for the issue "Vol 4, No 1 (1985)" in the section "Subject Terminology". Please ensure that the XML document conforms to the appropriate DTD, and that a title has been supplied for the journal's locale.

How do I go about looking for the cause and fixing it?
Regards
Nardus

ctgraham · January 29, 2018, 1:29pm

In OJS 2.4.8, each article element should have at least one title element.

github.com

pkp/ojs/blob/143e794ad8c671ab3c20bf501c75069863dc1902/plugins/importexport/native/native-sample.xml#L25


  </image>
</cover>
<date_published>date_published</date_published>
<access_date>access_date</access_date>
<section>
  <title locale="">title</title>
  <abbrev locale="">abbrev</abbrev>
  <identify_type locale="">identify_type</identify_type>
  <policy locale="">policy</policy>
  <article language="en" public_id="">
    <title locale="">title</title>
    <abstract locale="">abstract</abstract>
    <indexing>
      <discipline locale="">discipline</discipline>
      <type locale="">type</type>
      <subject locale="">subject</subject>
      <subject_class locale="">subject_class</subject_class>
      <coverage>
        <geographical locale="">geographical</geographical>
        <chronological locale="">chronological</chronological>
        <sample locale="">sample</sample>

The error message indicates that a title element with a locale attribute matching the journal’s default locale could not be found.

If you open the XML file and look at each article within the issue “Vol 4, No 1 (1985)” under the section “Subject Terminology”, do they all have titles? If they all have titles, what locales are referenced for each title?

Nardusg · January 30, 2018, 10:44am

@ctgraham

Thank you very much. One of the export files a received is over 400MB, importing that through the web interface will be problematic, do you have a cli import tool?

Regards

ctgraham · January 30, 2018, 3:03pm

The CLI tool is in the “tools” directory under your OJS install.

$ sudo su apache -s/bin/bash -c 'php tools/importExport.php NativeImportExportPlugin'
Usage: tools/importExport.php NativeImportExportPlugin [command] ...
Commands:
        import [xmlFileName] [journal_path] [user_name] ...
        export [xmlFileName] [journal_path] articles [articleId1] [articleId2] ...
        export [xmlFileName] [journal_path] article [articleId]
        export [xmlFileName] [journal_path] issues [issueId1] [issueId2] ...
        export [xmlFileName] [journal_path] issue [issueId]

Additional parameters are required for importing data as follows, depending
on the root node of the XML document.

If the root node is <article> or <articles>, additional parameters are required.
The following formats are accepted:

tools/importExport.php NativeImportExportPlugin import [xmlFileName] [journal_path] [user_name]
        issue_id [issueId] section_id [sectionId]

tools/importExport.php NativeImportExportPlugin import [xmlFileName] [journal_path] [user_name]
        issue_id [issueId] section_name [name]

tools/importExport.php NativeImportExportPlugin import [xmlFileName] [journal_path]
        issue_id [issueId] section_abbrev [abbrev]

Nardusg · February 1, 2018, 9:02am

Hi @ctgraham

Apologies, but how do I get the “journal_path”?

php importExport.php NativeImportExportPlugin import /home/files/2017-SATNT-Issues.xml journal_path tcd-ecs

Dos this format look correct ?

Regards

ctgraham · February 1, 2018, 1:15pm

Your parameters look correct for the import file, “journal_path” to be determined, and a user of “tcd-ecs”.

The journal path is the journal’s “short name”. It is configured under User Home → Site Administrator → Hosted Journals → Edit → Path. It probably appears in the URL as: http://hostname.tld/ojs/index.php/journalpath/index/

Be sure to run the command as your webserver user to ensure any files imported are written with the permissions of the web user. This will also mean that your web user will need access to read the source xml file.