Location for Google Dataset Search Markup

[floWetzels]

@gdoniparthi and I have been working on automatically generating the google markup for ARCs from the json/rocrate artifacts generated by the DataHub CI.
The plan was to create a landing page for each ARC in the arcregistry, which contains the markup in the header.
This has been tested for example ARCs and seems to work as expected.
The reason for this choice was that we do not have access to the header of a gitlab instance, meaning that the actual "website" of the ARC cannot contain the google markup.

However, after disussing this with @HLWeil, we found that it might be more sensible to replace this with a similar workflow for the new landing/publication pages which are created upon publication of an ARC.
This would also allow easier integration of FAIR signposting in the future, since FAIR signposting requires the DOI to point to the landing page (which is not the case using the arcregistry).

Any opinions on this? @muehlhaus @Freymaurer @j-bauer @HLWeil @gdoniparthi

[Freymaurer]

Seems good to me.

Just one question, is there no way to inject the meta tags to the gitlab page via smaller components?

[j-bauer]

We had that idea/inquiry a couple of months ago and while we could patch the HTML templates of gitlab, injecting a content-specific tag with the required metadata of a specific ARC might be more difficult. I'm not sure what is better: try to patch gitlab for this or just run another service for discovery purposes. Either way, we can have a look if injecting those tags in the HTML templates is feasible or not, in order to make a more informed decision.

Other opinions?

[Freymaurer]

It really depends, if you could add a small react component to a page. this way you could use the meta tag, to change the document header:
https://react.dev/reference/react-dom/components/meta

but i am not sure how this interacts with SEO. But React router recommends using this, so it should not be that bad