Clarify what "sample" means across pages

[ljohnson09]

Sample numbers are not consistent across pages, users were confused by what a "sample" is.

Example: GROW page - Study landing page shows 430 samples for sample count under NMDC Study Details section, but this does not align w/ the omics sample type counts underneath the title

NOTE: Alicia - Tooltip that pulls from schema

[naglepuff]

I believe this screenshot highlights the issue being described. I can see how it could be confusing to users for the counts in the omics chips to not line up with the stated sample count. This is due to there being more than one analysis per sample. Perhaps we could update the labels in the chips or add tooltips to clarify what all of the number means (maybe we could use schema definitions here - I would need to be pointed in their direction). Any thoughts @aclum?

[aclum]

This primarily pertains to the main search page. The 'results in the faceted search returns number of biosamples but it is not labeled. Things get confusing if the number of samples doesn't match the number of omics records. For example with the neon soil study there are approximately 3 samples per 1 metagenome omics record.

I will check with Mark on what schema slots should be used to populate tools tips.

[ssarrafan]

I'll move this to the new sprint based on the recent comment from @aclum. Can this be assigned to one person once you get clarification from Mark?

[aclum]

see #750, i linked this issue in slack to get clarification on what slot we should populate to be able to provide a tool tip.

[aclum]

My suggestion here is that for the image posted on last week we update 'Found 4475 results' to 'Found 4475 samples' where hovering over the word samples pops up a tool tip populated with the description for Class Biosample.
Assigning to just @marySalvi since we have a path forward.

[naglepuff]

Here's an example of us pulling descriptions out of the schema (could be a helpful reference when making the change to pull out annotations for classes):

nmdc-server/web/src/components/MenuContent.vue

Lines 60 to 70 in 94413ba

	const description = computed(() => {
	const fieldSchemaName = getField(props.field, props.table);
	const { schemaName } = types[props.table];
	if (schemaName !== undefined) {
	// @ts-ignore
	const schema = NmdcSchema.$defs[schemaName];
	// @ts-ignore
	return schema.properties?.[fieldSchemaName.schemaName || props.field]?.description || '';
	}
	return '';
	});

[ssarrafan]

Looks like the linked PR still needs to be reviewed so I’ll move to the next sprint.

[aclum]

Looks good on dev.