Bringing over KM-13 from JIRA, because another member reported the same issue recently. ______________________ The Crossmark box displays the print publication date, and leaves it blank if there isn't one. We should probably display both, but as an interim I suggest we switch to online publication date. This is likely to be the earlier date, and therefore more relevant. ______________________ Example from user. DOI: 10.1128/mBio.02819-18 Published field is blank in Crossmark: [https://crossmark.crossref.org/dialog/?doi=10.1128/mBio.02819-18&domain=asm.org ](https://crossmark.crossref.org/dialog/?doi=10.1128/mBio.02819-18&domain=asm.org) Metadata only includes an 'online' publication date ``` <publication_date media_type="online"> <month>03</month> <day>05</day> <year>2019</year> </publication_date> ``` as compared to DOI: 10.1128/jvi.01824-18 Published field in Crossmark contains the date 2019-02-13 [https://crossmark.crossref.org/dialog/?doi=10.1128/jvi.01824-18&domain=asm.org ](https://crossmark.crossref.org/dialog/?doi=10.1128/jvi.01824-18&domain=asm.org) Metadata includes both 'online' and 'print' publication dates ``` <publication_date media_type="online"> <month>04</month> <day>03</day> <year>2019</year> </publication_date> <publication_date media_type="print"> <month>02</month> <day>13</day> <year>2019</year> </publication_date> ``` [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: @mrittman - [ ] Tech lead: - [x] Service:: or C:: label applied - [x] Definition of done updated - [x] Acceptance testing plan: screenshot or demo - [x] 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 - [x] Code reviewed - [x] 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 - [x] Public documentation reviewed and updated - [x] Acceptance criteria met - [x] Use online publication date in Crossmark by default - [x] If there is no online publication date in metadata, use the print publication date - [x] Acceptance testing passed - [x] Deployed to production # Notes [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)