-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way to set language for articles in OJS Export #21
Comments
you mean, the language is set only per author tag? that's what I've been able to confirm, e.g.: it's set in |
an easier solution would be to keep grabbing the metadata only in the submission primary language. then implementing support for setting the article's language attribute during the crossref export. currently, with language attribute unset, I'm afraid it might be assumed as English upstream. though the specification doesn't explicitly define a default value "en": if the editor/admin wants to change the submission primary language, they can always use the quicksubmit plugin (or wait for pkp/pkp-lib#5502). |
I've confirmed the language attribute can be set preferably at both journal level and article level, and possibly also at the title level (especially with multilingual metadata), as per CrossRef support forum, e.g.:
|
Currently the article metadata are exported in the article primary language. Thus, do I understand it correctly, that the goal/requirement here is to export all metadata, in all languages, but to define the article primary language using the |
@ajnyga, because this issue is assigned to CRAFT OA: is the issue maybe solved with pkp/pkp-lib#9126? And if not, what else would be needed? Thanks a lot! |
@ajnyga, now I saw/read the CRAFT OA document considering this issue. I would suggest to open a new issue for that part of the CRAFT OA package in pkp-lib/issues/ because this issue is only opened for Crossref (repository/plugin) and in the project it seems you will investigate also other services/places in the code. |
dear @bozana originally I had suggested a gradual approach: first to make more explicit in the metadata which single language is being exported; then, later, support exporting metadata containing multiple languages. but now I believe the present issue is already fully resolved, given the great work at pkp/pkp-lib#9126. |
Hello, as I have checked from the XML file exported from the plugin, the language is set only per tag, not per <journal_article> tag. Is there a way to set the article languages in the settings, so that the CrossRef XML Export Plugin
exports also the language of the article to Crossref, and to their partners through them.
The text was updated successfully, but these errors were encountered: