issue
If an item belongs to a collection, the Related row on its page no longer displays.
There are currently no means to allow both rows to display together.
You are thus forced to choose between either being able to group a series / curatorial theme, or, preserve discoverability based on that title.
This also heavily penalizes lesser-known titles, where discoverability becomes most important.
Titles in collections will still show additional rows of actor/director groups etc., so it’s also just interactively/experientially very weird to not have the “main” associative thing there too.
feature suggestion
-
Create a checkbox option at the library level to
Also show related titles row for items which are in a collection& downstream implementation thereof. -
Modify the relevant callstack to exclude IDs in the collection from the related titles row.
complications/considerations
Currently, if an item is in multiple collections, only the first collection it was added to will show as the row.
Therefore, only the first element in that foreign key attr should be looked at (otherwise it’s overreaching in what it might exclude).
-
if you ever decide to show rows for all collections a title is in, this would create a future bug where titles in additional collections could also appear in the general Related row.
-
^ since the details of that implementation might not be fully predictable, a unit test that is designed to fail in this case (but currently succeed w/ the proposed case) would alleviate needing to remember to alter this behavior.
