1.0.0.8-omp3.4

1.0.0.8 for OMP 3.4

1.0.0.8

1.0.0.8 for OMP 3.5

1.0.0.7-omp3.4

1.0.0.7 for OMP 3.4

1.0.0.7

1.0.0.7

1.0.0.6-omp3.4

Review 1.0.0.6: valid names and batch timestamp in the deposit XML, O…

1.0.0.6

Review 1.0.0.6: valid names and batch timestamp in the deposit XML, O…

1.0.0.5

Deposit edited volumes as edited_book with volume editors only; bump …

1.0.0.4-omp3.4

Deposit edited volumes as edited_book with volume editors only; bump …

1.0.0.4

Add the 38-locale PKP standard set and fix legacy locale codes

1.0.0.3-omp3.5

Fix Crossref export failing on non-production ORCID iDs (issue #1)

The Crossref schema type `orcid_t` only accepts
`https?://orcid.org/NNNN-NNNN-NNNN-NNNX`. The filter wrote the stored ORCID
straight into the `<ORCID>` element, so an ORCID Sandbox iD
(`https://sandbox.orcid.org/...`, which is what OMP stores when the ORCID
integration runs against the sandbox API) failed schema validation and took
the whole export down with "An XML validation error occurred and the XML
could not be exported".

Deposits now go through getDepositableOrcid():

- a production iD is deposited unchanged;
- a sandbox iD is rewritten to the production host while the plugin is in
  test mode, so the Sandbox -> OMP -> Crossref workflow can be tested against
  test.crossref.org, and dropped in production, so a sandbox iD is never
  deposited against a live DOI;
- any other malformed value is dropped instead of aborting the export.

Also set the `authenticated` attribute from the contributor's ORCID
verification status; it was missing, so every deposited iD fell back to the
schema default of false, including verified ones.

Bump to 1.0.0.3.