Split multi-inventory datasets into their constituent parts #53
Description
This is as much a database and api based issue as a front-end enhancement here. We need to establish a parent-child relationship within our dataset registry, and re-register components of large datasets to have their own dataset ids, with a parent id referencing the larger collection that came from. This could also be applied to very large aggregate datasets like GBIF.
In the datasets UI, in order to keep the full dataset table list from needlessly exploding, we would expose these as individual datasets via an overall view of their parent (such as https://mol.org/datasets/325306dd-4fde-4c21-8518-16d9d916cee9) with yet to be determined selectors and map controls.