Carlo Minotti

I am pretty sure our ingestors use for historical reasons the headers in many places rather than the query params. Could the BE change wait until all facilities have rollout...

yes, indeed. I have nothing against changing the FE, but the PR description mentions a change in the BE

ah ok, thanks, I must have missed that. I support Bjorn's point, let's discuss it in the meeting if time allows

as much as I like 3, I think it requires a huge amount of work and it's personally not what I would start with. IMO, a solution in between, especially...

> I vote option 1 for the Web Ingestor. It's a feature that already exists in the scicat core (create dataset form) with a greater enhancement. I very much agree...

is ScientificMetadata display also intended to be customisable? why not checking [iframes](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe)? I like the idea anyway

I think something to look into is custom scripts loading/execution for custom visualisation in the dataset details page. The datasetDetail page could send data to these scripts that will render...

> @minottic I have in the past floated the idea of a rules-based link configuration (https://github.com/SciCatProject/frontend/issues/960). If we had a mechanism to configure links to display based on a set...

but what if these scripts can only come from a maintained registry (that we manage inside the scicatproject org on github) or from the /assets folder only?

@Junjiequan shall we ignore this? I would be in favour of ignoring it... > An action sourced from a third-party repository on GitHub is not pinned to a full length...