It would be great to add Dataset support to this fantastic module.

The Dataset schema.org definition (https://schema.org/Dataset) promises to dramatically improve access to and semantic tagging of open datasets via standard search tools (ie. Google, Bing, DuckDuckGo etc.). To encourage implementation of this standard by search engines, we need to increase adoption. As Drupal is an important tool for data portal creation, support via this module would streamline tagging and encourage uptake in existing and new data portals.

Support has already been written by isangil in this issue for the Deims distribution: https://www.drupal.org/node/2322571. The patch is currently a git patch - we need to submit the patch along d.o lines, then review and test.

This issue is a candidate for the Science on Drupal Code Sprint at ESIP Winter 2015 this coming Thursday 8th January.

Is the idea of Dataset support within the scope of this schema.org module? If so, it would be great to move towards getting this integrated, using isangil's great work as a starting point.

Comments

scor’s picture

scor commented

Hi @dbassendine and thanks for your interest. The schema.org module isn't written for specific types only, so any type that is present on schema.org is in scope!

In fact you should the "Dataset" type should already be available in the dropdown (at least in the dev version of the module). Have you tried it? I would be curious to see how far you are able to go with the current version of the module.

dbassendine’s picture

dbassendine commented

Thanks Stephane, I appreciate the feedback. When I read the project description, I suppose I assumed it was designed for the three examples you give: Person, Recipe and Event. Now that I'm really trying out the module, I see that it's possible to select any type and properties - which is great!

I've been experimenting with setting up the Dataset mappings today for an example Dataset content type. I suppose my immediate question relates to hierarchies:

  • If I have a "Body" field, can I properly set it to About (http://schema.org/about) > Description (http://schema.org/description) all in one go by setting the Property field to "about:description"?
  • If I have a "Location" geofield, I can set the property of the field to "spatial", but how would I set the child properties of "Place" (eg. latitude and longitude) - I suppose this would need to be handled by the geofield module's field formatter, as "latitude" doesn't actually have a corresponding field
  • If I have a "Locations" term reference to a "Location" term entity - I suppose I can set the "spatial" property on "Locations" (as the parent), then set other properties on each of the "Location" entity fields independently (as the children) (although this still leaves the issue with the geofield latitude/longitude, unless "latitude" has a field and "longitude" has a field)

I think once I get a handle on some of these issues, it would be great to have an example Dataset module and tutorial that makes it easier to see how best to set up the mappings.

Let me know what you think - thanks, David