Confusing display of child datasets nested under multiple parent versions #2689
Description
When a parent dataset is updated (e.g., to add authors), and the new version includes existing and unchanged child datasets, MetacatUI currently displays both the old and new parent datasets on the child dataset's landing page. This results in child datasets appearing to have multiple parents, which can be confusing to users, especially when the change to the parent was minor (like a metadata-only update).
Example: There is an old version of a parent dataset that was updated to a newer version of the parent dataset with more author names. And these 2 child data packages (child 1 and child 2) have 2 parent re-directs now.
This issue was encountered while assisting a PI who was confused about why her child datasets showed links to two versions of the parent dataset. Although technically accurate (since both parent versions included the same child at different times), the display could be improved.
If the title hasn't changed, then on first appearance it looks like the links are duplicated (like a bug), and there is no indication which parent version is the current one. If a parent dataset had 20 revisions, then MetacatUI would show 20 links to different versions of the parent which is excessive and not helpful.
The child dataset should ideally show a reference to only the most recent version of the parent dataset. We could consider also showing that it's included in n older versions as well.
Note: We've previous discussed moving away from supporting nested datasets, except for those that already exist, and supporting portals instead (e.g. Convert nested datasets to portals). However, they are still being presented as an option.