Question on publishing workflow, item 3 of Deconstruction

[mike-iris]

I am starting with a handcrafted sitemap which does not necessarily map directly to desired datasets or services. In the beginning, I want to disrupt the current sitemap as little as possible.

I am a bit fuzzy on the following...

• what defines a landing page?
• • is it an entry in a handcrafted sitemap(html)?
• • can I have an xml sitemap in parallel with an html sitemap?

Then to establish a workflow, I would a) define links in an xml or html sitemap that link to

• a desired service or dataset
• or group of services or group datasets (i.e. catalog) b) load the desired json-ld in respective target links (i.e. landing page)? c) iterate on a and b, adding links as needed until the desired granularity of data, services (and tools, etc.) are exposed?

[ashepherd]

Hi Mike,

I think we leave it up to the repositories to decide what is a landing page in their purview. I think one way to think about what to include there is what data products you would want to expose to the EarthCube Registry. But, we've also created a way to for repositories to describe data APIs on a repository level or at a dataset level. So, the definition of a Dataset isn't set in stone for P418 which is good for sites like IRIS to make that decision.

I'm not sure I follow your question about an HTML sitemap v. an XML sitemap. Could you clarify there what you have now and shoot me over some links? Google wants an XML sitemap which they defined here: https://www.sitemaps.org/protocol.html (there are some examples of some here: https://github.com/earthcubearchitecture-project418/p418Docs/blob/master/publishing.md).

For publishing the schema.org or your repository homepage and the dataset landing pages, the best, complete guide right now is at: https://github.com/earthcubearchitecture-project418/p418Vocabulary/blob/master/README.md

But, your workflow seems good! Hit us up with any questions!