[BUG] Aggregate API responses always contain empty dict for available_pipelines

[alyssadai]

Is there an existing issue for this?

• I have searched the existing issues

Expected Behavior

When subject data in the graph contains pipeline metadata, an aggregate mode query response for the dataset should include a non-empty dictionary for available_pipelines.

Current Behavior

available_pipelines is always an empty dictionary {}.

This is because the aggregation statement in the SPARQL query template has not yet been updated to return pipeline variables, and similarly, the API-side handling of the graph response for an aggregate query currently does not consider these variables.

api/app/api/utility.py

Lines 306 to 315 in c150b37

	if return_agg:
	query_string = (
	textwrap.dedent(
	"""
	SELECT ?dataset_uuid ?dataset_name ?dataset_portal_uri ?sub_id ?image_modal
	WHERE {"""
	)
	+ textwrap.indent(query_string, " ")
	+ "} GROUP BY ?dataset_uuid ?dataset_name ?dataset_portal_uri ?sub_id ?image_modal"
	)

At the same time, the value of available_pipelines is always initialized as an empty dict:

api/app/api/crud.py

Line 171 in c150b37

dataset_available_pipeline_info = {}

api/app/api/crud.py

Line 290 in c150b37

available_pipelines=dataset_available_pipeline_info,

And so this is what is currently always returned in aggregate mode.

Error message

No response

Environment

• OS:
• Python/Node version:

How to reproduce

Install and launch the API from source, in aggregate mode, and point it to a graph containing data from fhttps://github.com/neurobagel/neurobagel_examples/tree/main/data-upload/pheno-bids-derivatives-output.

Anything else?

No response

[neurobagel-bot]

🚀 Issue was released in v0.4.0 🚀