Assigning a DOI inside OJS is not the same as registering it with Crossref. Backfiles usually need both: preserve identifiers that already exist, mint new ones where they are missing, then deposit and test resolution.
For a full archive project, see back-issue & archive import.
Assignment vs registration
- Assignment — the DOI string is stored on the article (prefix + suffix pattern).
- Registration — the metadata deposit is accepted by Crossref (or your agency) and the DOI resolves to your landing page.
An article can look “done” in OJS while still returning 404 at doi.org if deposit never succeeded.
Configure prefix and suffix pattern
In the DOI / Crossref plugin settings, set your member prefix and a suffix pattern that will stay unique for the life of the journal (issue and article identifiers are common). Test on a staging copy before minting hundreds of new DOIs on production.
Batch deposit sizes
Retrospective deposits work best in batches you can review — often by issue or by a few hundred DOIs — rather than one giant dump. After each batch, read the Crossref submission log: accepted, warning, and failure rows.
Reading submission logs
Failures are usually metadata problems (missing title, bad date, conflicting DOI already owned elsewhere). Fix the record, resubmit only the failed items, and keep the log with your reconciliation report.
Articles published before you had a prefix
Older volumes often have no DOI. Mint new DOIs for those articles under your current prefix, deposit them retrospectively, and leave any pre-existing DOIs untouched so you do not create duplicates.
Resolution testing
Before handover, check that each DOI resolves to the correct OJS article page. Spot-check is not enough on a multi-year archive — automate or systematically walk the reconciliation list.
Need the archive imported for you?
Galleys.pub runs back-issue and archive imports into OJS with metadata mapping, staging verification, and Crossref deposit. Reply within 24 hours.
Back-issue & archive import Scope my archive