# These two DOIs were registered for the same book: - 10.1093/oxfordhb/9780199578610.001.0001 - 10.1093/law/9780199578610.001.0001 I have aliased 10.1093/oxfordhb/9780199578610.001.0001 to 10.1093/law/9780199578610.001.0001, but both DOIs are resolving to the co-access interim page:  That doesn't make much sense. A) Co-access should never have been triggered for this content, since both DOIs are of the same prefix, and B) Now that the DOIs have been aliased, both should resolve directly to the content. Second example: 10.1017/9781316182109 and 10.1017/CBO9781316182109 are both resolving to a co-access interim page.  They are not aliased, but notably 10.1017/9781316182109 has asserted an isIdenticalTo relationship to 10.1017/CBO9781316182109 and the reciprocal relationship has been applied to 10.1017/CBO9781316182109. I do not know where that isIdenticalTo relationship metadata came from, because it's not in the metatadata deposits submitted by CUP for 10.1017/9781316182109 but it is in its metadata record in both APIs. # 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: - [ ] 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 - [ ] Respond to and close Zendesk 359430 - [ ] Acceptance testing passed # Notes [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)