Questions on DOAJ plugin exports

[obi]

Hi,
We are trying to use DOAJ Export plugin on OJS 2.3. When we run “Export Journal “, it exports both "Future issues" and “Published issues”. We want to export only Published Issues and not Future Issues. How can we filter out Future Issues”?

Any help or suggestion on how we can go around so that Future Issues are not exported? I have tried to edit the plugin script but no success.

Thanks in advance.
- Obi

[jmacgreg]

Hi Obi,

I can't replicate this: my DOAJ plugin appears to filter out articles assigned to future issues during export, so they aren't included. Which exact version of OJS are you using? Can you possibly try updating the plugin scripts from Git to see if that makes a difference (http://github.com/pkp/ojs/tree/master/p ... port/doaj/)? You can also see a history of each file from that URL, which might help.

Cheers,
James

[obi]

Hi James,
I tried to update the plugin scripts from Git, but it did not work. I recieved 28 errors matching the the number of articles assigned to future issues in our journal.
We are using OJS version 2.3.1.

Thanks
Obi

[jmacgreg]

Hi Obi,

Hrm, it looks like some fundamental changes have gone into a handful of those files since 2.3.1 has been released -- reverting to originals will at the very least return you to your original issue. But however, I still can't replicate it. You can always edit the XML file to remove any material to be published in the future. Could you also email me the XML file and point to the Future Published material? jmacgreg at gmail dot com.

Cheers,
James

[obi]

Hei James,
I could not get the future issues because the journal manager has published all the issues. They will soon start with a new future issue.

A new problem: I created an xml file of all published issues and tried to export to DOAJ - but getting error messages. This is something other than what we have in the past before updating the plugin scripts from Git.

See the error messages below:
warning: failed to load external entity "http://www.it.ojp.gov/jxdm/iso_639-2b/1.0/iso_639-2b.xsd"
/usr/local/doaj/schemas/doajArticles.xsd:7: element import: Schemas parser warning : Element '{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at location 'http://www.it.ojp.gov/jxdm/iso_639-2b/1.0/iso_639-2b.xsd'. Skipping the import.
/usr/local/doaj/schemas/doajArticles.xsd:41: element element: Schemas parser error : element decl. 'language', attribute 'type': The QName value '{http://www.it.ojp.gov/jxdm/iso_639-2b/1.0}LanguageCodeType' does not resolve to a(n) type definition.
/usr/local/doaj/schemas/doajArticles.xsd:86: element attribute: Schemas parser error : attribute decl. 'language', attribute 'type': The QName value '{http://www.it.ojp.gov/jxdm/iso_639-2b/1.0}LanguageCodeType' does not resolve to a(n) simple type definition.
/usr/local/doaj/schemas/doajArticles.xsd:131: element attribute: Schemas parser error : attribute decl. 'language', attribute 'type': The QName value '{http://www.it.ojp.gov/jxdm/iso_639-2b/1.0}LanguageCodeType' does not resolve to a(n) simple type definition.
/usr/local/doaj/schemas/doajArticles.xsd:155: element attribute: Schemas parser error : attribute decl. 'language', attribute 'type': The QName value '{http://www.it.ojp.gov/jxdm/iso_639-2b/1.0}LanguageCodeType' does not resolve to a(n) simple type definition.
WXS schema /usr/local/doaj/schemas/doajArticles.xsd failed to compile

Cheers
- Obi

[jmacgreg]

Hi Obi,

Have you reverted back to the files that shipped with your version of OJS? That might make the most sense for the moment.

Cheers,
James

[obi]

Hei,
I have reverted back to the files that were shipped with version 2.3.1 of OJS. I will test the script again when we have registered a new "Future Issues".

Cheers
Obi