Testing your XML
Our test version of the admin tool allows members and service providers a sandbox to test their XML submissions, before depositing in the production (live) system. You can use the test system for deposits via the admin tool and HTTPS POST, but not for deposits via the web deposit form.
The test environment mirrors the production admin tool, except that submissions to the test system do not result in content registrations.
You can also use our metadata quality check parser to check your XML before submission. The parser quickly identifies errors in the XML you uploaded.
Any deposits you make in the test system have no effect on your resolution reports and conflict reports, which relate only to content you register in the production system. Learn more about reports.
Differences between test and production systems
VoR/preprint match notifications: in the production system, a notification feature alerts preprint creators of any matches with journal articles, so they can link to future versions from the preprint. In the test system, you won’t be notified of matches.
Accessing the test system
We don’t automatically set up new accounts with access to the test system, but we are happy to give you this access at any time, whether during your membership application, or at any time after joining. Just contact us to request access.
Carrying out a platform migration?
Please let us know so we can update both your production and test accounts. Learn more about planning a platform migration.