How to create XSD format for Index Copernicus?


#41

Hi @a-vodka,

Great – I can help you get this ready for the plugin gallery!

Try uploading the plugin package to the “Releases” area in the github repository, rather than putting it into the repository itself in downloads. We tend to use branches to organize the code for each target version of OJS (e.g. ojs-stable-2_4_8 and ojs-stable-3_1_1), then upload a release for each.

Once that’s ready to go, write up a description and let me know what versions each release works with (e.g. 3.1.0-0, 3.1.1-1, 3.1.1-2, etc) and I’ll add entries to the plugin gallery. An example entry for the plugin gallery looks like this:

<plugin category="generic" product="customHeader">
	<name locale="en_US">Custom Header Plugin</name>
	<homepage>https://github.com/asmecher/customHeader/</homepage>
	<summary locale="en_US">Permits the addition of custom headers to the website.</summary>
	<description locale="en_US"><![CDATA[<p>This plugin permits the addition of custom headers to the website. This can be used e.g. to add arbitrary Javascript to the front-end.</p>]]></description>
	<maintainer>
		<name>Alec Smecher</name>
		<institution>Public Knowledge Project</institution>
		<email>alec@smecher.bc.ca</email>
	</maintainer>
	<release date="2018-02-19" version="1.0.0.0" md5="84d55e711ee08c948d69dc37d6075ef1">
		<package>https://github.com/asmecher/customHeader/releases/download/ojs-3_1_0-0/customHeader-ojs-3_1_0-0.tar.gz</package>
		<compatibility application="ojs2">
			<version>3.1.0.0</version>
			<version>3.1.0.1</version>
			<version>3.1.1.0</version>
			<version>3.1.1.1</version>
			<version>3.1.1.2</version>
			<version>3.1.1.4</version>
		</compatibility>
		<compatibility application="omp">
			<version>3.1.0.0</version>
			<version>3.1.1.0</version>
			<version>3.1.1.1</version>
			<version>3.1.1.2</version>
			<version>3.1.1.3</version>
			<version>3.1.1.4</version>
		</compatibility>
		<certification type="official" />
		<description>Initial release of the custom headers plugin.</description>
	</release>
</plugin>

Thanks for contributing!

Regards,
Alec Smecher
Public Knowledge Project Team


#42

You problem with plugin installation has been solved. Please, try to install

https://github.com/a-vodka/ojs_copernicus_export_plugin/releases/download/0.0.2-ojs3/copernicus-ojs3-0.0.2.tar.gz


#43

Installed, exported XML file and Imported into ICI successfully as well. Just one problem, each article is imported thrice in the ICI. So, it is showing three entries of each and every article. Anyone experiencing this issue?

I have figured it out.
Before, I had three installed local languages, so XML has triplicate the each article in metadata for those languages as well. But, I had removed the two other local languages and currently, only one language is available (English)Then why it is still creating the entries in XML file for the deleted languages?


#44

Hello, @seisense!

This Plug-in exported metadata for at all available in OJS languages. May be we should ask about this issue @asmecher or @Ph_We. They can help to remove unused languages.

For your case, I propose to remove all unnecessary items manually.


#46

@a-vodka i can help with testing for 3.1.1.2 version of OJS


#47

Thank you. if you find a problem, please create an issue on github.


#48

first problem, - it doesn’t save formatting. it put’s all in one string. if you can give you’r email i will send file to you


#49

It worked in mine. Ojs 3.1.1.2 and 3.1.1.4 both.


#50

how? i have multilanguage submissions and copernicus import says, that i have bad file


#51

Yep, it’s OK now, thank you!