feat: add schema.org Dataset metadata to product pages

[jedsundwall]

Summary

• Fixes the existing ProductSchemaMetadata component (was unused and had a hardcoded yourdomain.com domain)
• Replaces hardcoded URL with dynamic getBaseUrl(), adds creator URL, DOI identifier, and sameAs links for ORCID/ROR
• Wires the component into the product layout so it renders on all product pages

Test plan

• Visit a product page and inspect the HTML source for a <script type="application/ld+json"> tag
• Verify url, dateCreated, dateModified, and isAccessibleForFree are correct
• Verify creator.url points to the account page
• On a product with a DOI, verify identifier is present
• On a product whose creator has an ORCID/ROR, verify creator.sameAs is present

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
source-cooperative	Ready	Preview, Comment	Apr 7, 2026 9:23pm

[jedsundwall]

@alukach @tylere this, #280 , and #281 are all of a piece. I probably didn't need to do them as three separate PRs, but I got nervous working with Claude Code on it. These are pretty straightforward changes to add optional ROR identifiers to organization profiles and then to insert DOIs, ORCID IDs, and ROR IDs along with other metadata into our profile and product pages. This will help with search engine optimization as well as any other bots making their way through Source.

Very open to feedback on how the metadata is being introduced. We can test this pretty easily against linters once we push it live.

[tylere]

this, #280 , and #281 are all of a piece.

Is the third issue that you refer to #282? (i.e. this PR is 281)

[jedsundwall]

@tylere yes. 🤦‍♂️