Special handling for datasets with a large number of direct ancestors

[yuanzhou]

As a result of https://github.com/hubmapconsortium/search-api/issues/788, we'll have Datasets with a large number (hundreds or even thousands) of direct ancestors. The button to edit the sources and the delete action (trash bin icon) on each source should be disabled. When editing other fields and submit the updates, direct_ancestor_uuids field should NOT be included in the request payload either.

For example: https://ingest.dev.hubmapconsortium.org/dataset/9dc2de0838a4fd3e960b35424788950d has 2500 direct ancestors.

Questions:

• Cases like this, all the direct ancestors will be Datasets and none has "Submission ID", can we remove that column?
• Is there a way that we can identify such datasets by type?
• Can we use some special UI theme to make such datasets obvious to the users?

[shirey]

We won't do this right now, closing