dataset display issue caused by duplicated submitter id #45
Description
There may be multiple projects exist in Gen3. Two Gen3 dataset display modes are provided by the backend:
- One public project and multiple private projects
- Multiple public projects
The issue happens in mode 2 - display multiple public project datasets at the same time. As the query API requires the dataset submitter id to query the dataset, it will be difficult to distinguish which dataset the portal is looking for if there exist multiple datasets with the same submitter id.
Is there a good way to distinguish which project it belongs to instead of passing the project id directly as request payload?