Making an Arabic version of research published in another language publicly available

This guide is for the Scientific Translation into Arabic track. Participants submit their own peer-reviewed research originally published in another language and must be its sole author or first author when there are multiple authors. They prepare a complete Arabic version of their research, have it reviewed scientifically and linguistically, and make it legally available in a public scholarly repository before final submission.

1. Check translation rights first

A translation is an adaptation of the original article. The licence or rights holder must permit preparing and publishing a translated version.

Examples of licences permitting adaptations include CC BY and CC BY-SA, subject to their respective conditions. CC BY-ND and CC BY-NC-ND do not permit publishing an adaptation such as a translation without separate permission.

When relying on a noncommercial licence, the intended use must comply with that restriction. Evidence may also include written rights-holder permission, publisher terms permitting translation, or proof that the author retained the necessary rights.

Read the official Creative Commons licence guide.

This guide provides general procedural information, not legal advice tailored to an individual case.

2. Prepare a complete scholarly Arabic version

The Arabic version must preserve the work’s content and scientific data, use precise terminology, and handle tables, figures, equations and references correctly.

Translation tools may assist preparation, but the final version must undergo complete human review. Unedited machine translation or substantial scientific or language errors do not meet the track’s requirements.

Peer review of the original article and the remaining cycle requirements still apply. The Arabic version does not require a second journal peer review merely because it is a translation.

3. Link the Arabic version to the original

The public record must include:

The Arabic title.
The authors’ names.
A clear statement that it is an Arabic translation of the original article.
The original title and DOI or official URL.
A sufficiently detailed citation of the original publication for verification.
A rights and licence statement permitting publication of the Arabic version.

Include the deposit date, make the Arabic file publicly accessible, and use a stable URL and persistent identifier where available.

4. Where can you deposit it?

Zenodo

Zenodo is the general recommended option for a public research record and file with a persistent page and DOI. Record owners can delete a record within 30 days of publication; a tombstone page retains its citation. Later deletion requests are subject to justified cases and repository policy.

Visit Zenodo, Record-management policy

Figshare

Figshare provides public scholarly records with persistent identifiers and links. Ordinary users cannot directly delete a public record; deletion requires Figshare or the institutional repository administrator, depending on the account.

Visit Figshare, Editing and deleting records

OSF Preprints

An appropriate specialist service is acceptable when it uses pre-moderation and its policies and scope admit the work. Accepted records receive persistent identifiers and links; withdrawal leaves basic metadata and a withdrawal record.

The generalist service currently does not accept new submissions. Check the specialist service’s requirements before depositing; acceptance of a translation is not automatic.

Browse preprint services, Deposit and withdrawal guide

Institutional repository

A repository is acceptable when it provides a persistent public record, a stable URL or identifier such as a DOI or Handle, author metadata, a publicly accessible Arabic file and a clear rights statement.

These repositories are independent. Naming them does not imply a partnership with Nashr Arabi.

5. What is insufficient?

The following are not accepted as the sole scholarly record:

Google Drive.
Dropbox.
OneDrive.
An editable cloud document.
A personal website alone.
A temporary sharing link.
A social-media post.

6. What do you submit to Nashr Arabi?

At final submission, the application records the deposit URL or identifier and the participant also uploads the same Arabic version to the application. The platform retains the submitted copy and its record for eligibility, evaluation and auditing. This does not make the file public through Nashr Arabi.

7. Before submission

I am the original research's sole author or its first author when there are multiple authors.
I have verified the right to publish the translation.
The Arabic version is complete and reviewed.
The public record is accessible.
The original publication details and DOI or official URL are correct.
The application file is the exact version I intend to enter.

All resources Scientific Translation into Arabic Current cycle

Name	Provider	Purpose	Retention
`cids`	Nashr Arabi	Retains the authorised company context when administration starts; it does not grant additional permissions.	365 days from the latest write, or until deleted or replaced.
`current_action`	This website	Retains navigation or the current action state within the administration tab.	Tab session; browser session restoration may restore it.
`current_state`	This website	Retains navigation or the current action state within the administration tab.	Tab session; browser session restoration may restore it.
`frontend_lang`	Nashr Arabi	Remembers the selected interface language. Arabic remains the default before an explicit choice.	365 days from setting or changing it, unless removed earlier by the browser.
`menu_id`	This website	Retains navigation or the current action state within the administration tab.	Tab session; browser session restoration may restore it.
`muk_cookie_consent`	Nashr Arabi	Stores cookie choices and the disclosure version when a decision is saved; a changed version or service registry may require a new decision.	180 days from saving the decision; disclosure changes may invalidate it earlier.
`redirect_menuId`	Nashr Arabi	Supports navigation between administration apps. Written or emptied when the apps menu is used.	No automatic expiry is set in source; the value may be replaced or emptied and the key remains until site data are cleared.
`session_id`	Nashr Arabi	Links the browser to its server session for sign-in and request security. It may be created for a visitor without an account.	Browser max-age is 7 days when written; the server inactivity limit is 7 days. Logout ends the authenticated session.
`td_id`	Nashr Arabi	Created only after successful two-factor authentication and choosing to trust the device; ordinary visits or password sign-in do not create it.	90 days when the trusted device is created; trust can be revoked earlier.
`tz`	Nashr Arabi	Written by JavaScript when absent, using the timezone reported by the browser.	Browser session; the writer sets no expiry or persistent max-age. Session restoration may restore it.
`web.lastConnectedUser`	This website	When the user module loads for a signed-in account, quick login may retain up to five account names/logins, user/partner IDs and partner update dates. It contains no passwords.	No automatic expiry; until cleared or displaced from the list. It can also affect the login screen after logout.
`webclient_menus`	This website	Local cache of permitted administration menus.	No fixed time expiry; replaced on menu updates or cleared with site data.
`webclient_menus_version`	Nashr Arabi	Version marker for the administration menu cache.	No fixed time expiry; replaced or cleared with site data.
`website_cookies_bar`	Nashr Arabi	Keeps native necessary/optional gating aligned with the consent decision. Written when the decision is saved; its fields do not imply enabled optional categories.	180 days from saving the decision, or until deleted or replaced.