XML import feature issues/suggestions

Are you an Editor, Author, or Journal Manager in need of help? Want to talk to us about workflow issues? This is your forum.

Moderators: jmacgreg, michael, vgabler, John

Forum rules
The Public Knowledge Project Support Forum is moving to http://forum.pkp.sfu.ca

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.

XML import feature issues/suggestions

Postby asmecher » Mon Jan 03, 2005 12:24 pm

Hello OJS team,

I'm working on converting some paper journals to the OJS using the XML import feature, and had a few comments about the import process that might be helpful:

- The DTD isn't valid. The <section>, <number>, and <title> tags each have two separate definitions -- particularly <section>, which is once defined as a #PCDATA and once as being able to contain tags.

- The DTD could match the OJS's requirements more accurately. For example (correct me if I'm wrong) the DTD specifies that the author email is a required tag, while the OJS doesn't seem to require it. This applies to many of the required tags -- <date_submitted>, <date_published>, <abstract>, etc., all of which are nullable in the OJS database.

- In your XML example, one tag contains the text "N/A", but I think it would be much more conceptually clean if this tag were just omitted entirely. (I might have misunderstood why N/A is used.)

- The XML document structure would benefit from the use of attributes rather than just tags with #PCDATA contents. For example, <section order="2">...</section> rather than <section><section_order>2</section_order>...</section>.

Alec Smecher
alec (lives at) smecher (a dot) bc (another dot) ca


Another couple of notes

Postby asmecher » Thu Jan 06, 2005 12:16 am


Another couple of notes on the import feature...

If the path supplied in the <pdf>/path/to/file.pdf</pdf> (same for <html> etc) is a path on the server rather than a fully-qualified URL, as described in the sample XML, the preview feature will display bad links to PDFs. I'd suggest adding a quick check to see if it's a path or a remote URL, and if it's a path, just display it rather than providing a link.

Also, it would be nice to have some error checking on the import feature in case of a bad URL or path or some other error, such as creating the target file. Right now it's a little tough to track down the cause of something going wrong when the program carries cheerfully along.

Sorry to carp on about this or that little gripe -- the system's very impressive and I'm looking forward to exploring it more. Excellent work!

Alec Smecher

Return to “OJS Editorial Support and Discussion”

Who is online

Users browsing this forum: No registered users and 1 guest