There might be some cases we can semi-automatically fix, but not all of these relationships will have an accompanying Work we can automatically infer from relationships (Edition Group has an Edition which contains a Work).
As The Lord of the Rings was originally published as three separate volumes: The Fellowship of the Ring (19 July 1954), The Two Towers (11 November 1954), and The Return of the King (20 October 1955) should The Lord of the Rings be treated as a collection with an Edition Group and no Work?
Weirdly enough, those 5 editions that appear on “The Lord of the Rings” work seem to be 5 times the same, on top of the ID being that of this same work. No wonder it can’t find an edition with that ID.
I’ll clean that up as needed.
And there’s definitely a bug with the unnamed edition, which I’ll investigate.
The Lord of the Rings work has been fixed.
The weird editions were malformed relationships with the parts of the work (the relationship wrongly used was “Edition contains Work”).
I replaced them with the appropriate relationships: https://bookbrainz.org/work/4c2b172f-7b23-4bda-9ce5-04bce3f4a7d4
Now this LOTR work should eventually be replaced with a Series entity (once we’ve implemented those), but for no I think it will do.
Where did you find the link to that first 404, so I can fix the issue?
It’s an Edition Group rather than an Edition, and must have been erroneously added as an Edition relationship back when BookBrainz allowed users to enter any entity. https://bookbrainz.org/edition-group/3fd89055-b250-426b-9b74-6d43d8ec38d8
As for the relationship remaining on one side, that’s related to this issue which I’m about to deploy a fix for: https://tickets.metabrainz.org/browse/BB-545
Once it’s deployed we’ll be able to remove that remaining relationship.