Parent dataset link in package view shows obsolete parent packages
I updated a parent package, https://arcticdata.io/catalog/#view/urn:uuid:25a6bbf5-e24a-4ec1-8da3-54a181ec4ac2, to include a new child. Somewhere down the rabbit hole I managed to incorrectly reference a child package, resulting in a few child packages appearing to be children of a package I didn't intend. I rectified this by updating the parent.
If you look at one of the children, like https://arcticdata.io/catalog/#view/resource_map_doi:10.18739/A28S8M, you see that MetacatUI is showing two parent packages. If you look at those two parent packages, doi:10.18739/A28S8M is only included as a child of one of them. So the parent looks correct while a few children look incorrect. I did not expect this.
I'm not sure what's going on but maybe the code that fills in the Parent dataset links doesn't respect obsoletion? If this is the case, could/should this behavior be changed?