The backend of the map, to account for the shape of data in the megastudy, is learning how to do weighted averages and things. This can only work if we have, for records which dont represent individuals but rather groups of them, a count of the number of individuals in the pool. My understanding is we do have this for sample, but not always for assay entities. The ux question then is what do we want to show users for those cases where we dont have the data required to incorporate that record into the visualizations? (Im assuming the backend should continue its work, after dropping that record, and maybe provide a warning as well.) related question, do we know how many assays this affects?
The backend of the map, to account for the shape of data in the megastudy, is learning how to do weighted averages and things. This can only work if we have, for records which dont represent individuals but rather groups of them, a count of the number of individuals in the pool. My understanding is we do have this for sample, but not always for assay entities. The ux question then is what do we want to show users for those cases where we dont have the data required to incorporate that record into the visualizations? (Im assuming the backend should continue its work, after dropping that record, and maybe provide a warning as well.) related question, do we know how many assays this affects?