Consider a Stylesheet to translate EML <-> Google Structured Data Dataset?

[cboettig]

That is, https://developers.google.com/search/docs/data-types/datasets , which is basically http://schema.org/Dataset with some required fields.

Suggesting this mostly as a trial balloon to see what people think; my impression is that if this data were embedded into the metacat webpage for such a dataset (are those actually crawled by Google and returned in search results anyway or do you have to access those pages only by DOI or from the metacat search interface?) that it would (maybe one day) increase their discoverability / placement in Google searches, but maybe that's all nonsense, I dunno.

[mobb]

some of us have talked about this -- e.g., adding schema.org tags to the web rendering. I'd have to dig up some notes. Margaret O'Brien ORCID: 0000-0002-1693-8322 Information Management Marine Science Institute, UCSB Santa Barbara, CA 93106 805-893-2071 (voice) http://environmentaldatainitiative.org http://sbc.marinebon.org http://sbc.lternet.edu

…

On Mon, Jul 17, 2017 at 1:27 PM, Carl Boettiger ***@***.***> wrote: That is, https://developers.google.com/search/docs/data-types/datasets , which is basically http://schema.org/Dataset with some required fields. Suggesting this mostly as a trial balloon to see what people think; my impression is that if this data were embedded into the metacat webpage for such a dataset (are those actually crawled by Google and returned in search results anyway or do you have to access those pages only by DOI or from the metacat search interface?) that it would (maybe one day) increase their discoverability / placement in Google searches, but maybe that's all nonsense, I dunno. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#274>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEtBiYYQjrOX8TiIwMjY1pbfOUtUU8JHks5sO8OzgaJpZM4OafkL> .

[mbjones]

We've done more than talk about it -- I also implemented a prototype that inserted schema.org tags into the rendered HTML. The problem was that we moved primarily to a single page app for our display, which doesn't load at page load time, but rather afterwards during the JS execution phase. So, for most schema.org parsers, they didn't see them because they don't execute javascript. There are some elaborate ways to get around this, but we haven't dove in yet. This is more of a MetacatUI issue than an EML issue, so probably better to discuss it there (https://github.com/NCEAS/metacatui/issues), (and see our historical issue here: https://projects.ecoinformatics.org/ecoinfo/issues/6032).

[cboettig]

Very cool. Does that mean you have an XSLT stylesheet for this mapping already that you could share? If so, I think that would also be useful to drop into things like emldown.

(Also, opened a new issue in metacatui, as linked above, so feel free to close this one out)

[mbjones]

No XSLT -- this was done as a prototype by using JS to inject the DOM changes after the XSLT produced the HTML document. I'll have to poke around to find it. The limiting factor was that most clients that don't execute the JS from metacatui also don't see any of the tags.