# Background Pending publication is a way of creating a DOI and depositing metadata for a content item any time after a manuscript has been accepted but before it is published online. This is possible for all standard content types (such as articles, books, conference proceedings). Because a pending publication has not yet been published, its DOI will resolve to a publicly-available Crossref-hosted landing page. Once the work is published online, this same DOI will resolve to the URL for that content. Linking should always be by DOI, e.g. https://doi.org/10.1084/jem.20190086 Once the work has been converted to a journal article, for example, the Crossref system no longer sees the DOI as being, or ever being, a Pending Publication type, therefore the pending publication page shows an error message. # Observed behavior DOI 10.1084/jem.20190086 was initially registered as a Pending Publication. It was then updated to a journal article. On being updated the Crossref landing page ceases to recognise the DOI as a pending publication (correctly) but the page shown to users is not helpful  # Expected behavior Best case: recognise that the DOI used to be a Pending Publication and explain that it has been updated Next best case (quick solution): link the DOI from the error page, so the user can quickly access the content - for the case that the DOI doesn't exist, the user would see an error message from doi.org # How urgent [comment]: # (There are myriad factors that go into prioritizing and scheduling development work, but any information you can provide to help us understand severity, urgency, relative priority, or deadlines, is much appreciated.) [comment]: # (No need to update the Definition of ready when filing issues, but feel free to have a go if you're familiar with the territory.) # Definition of ready - [x] Product owner: @bvickery1 - [ ] Tech lead: - [x] Service:: label applied - [ ] Definition of done updated - [ ] Acceptance testing plan: - [ ] Weight applied [comment]: # (Feel free to leave this as is, or suggest changes. We'll update these during Backlog Refinement, prior to bringing this into a sprint.) # Definition of done - [ ] Unit tests identified, implemented, and passing - [ ] Code reviewed - [ ] Available for acceptance testing via a staging URL, or otherwise - [ ] Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed - [ ] Knowledge base reviewed and updated - [ ] Public documentation reviewed and updated - [ ] Acceptance criteria met - [ ] AC 1 - [ ] AC 2 - [ ] Acceptance testing passed # Notes [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)