Thanks @IFarley !
WRT the second reply from @tmrozewski, the water may be somewhat muddied by the terminology for sure. In this case a pre-print would be synonymous with “submitted manuscript” and a post-print would be the “accepted manuscript”. That version is after peer review but before copyediting. That’s likely the “electronic first” version you’re talking about.
Accepted manuscripts are often also allowed in so-called preprint repos like Arxiv by publishers, so this use-case makes sense. But they’re often an updated version of an existing pre-print/submitted manuscript.
In a way, we’re sort of talking about when something is actually published.
In this case, things are more complicated. OJS can tell you what a DOI is going to be based on the existing patterns in the DOI settings. If something is “in press” or “forthcoming” but not yet published and you want to use OPS specifically to host accepted manuscripts, I would probably use the DOI you know the article is going to have on publication. Then, when you publish, the record should update (via OJS) with the new metadata/URL. Working backwards from the publishing workflow in OJS will be easier than trying to force OJS’ hand with what’s entered in OPS.
This is sort of an in-between. And I don’t have an elegant answer about what to do with an accepted manuscript in OJS that isn’t as inelegant. Pre-print servers aren’t run by journals as part of their workflow, so I’m not sure I’d go that route in the first place. Nor do folks often upload preprints to preprint servers on an author’s behalf. I might be more likely to find a workaround in OJS for this specific instance, unless York is thinking of running a preprint server for all York scholars and they’re self-submitting.
How’s that for conjecture?! That’s a lot of conjecture!