Microdata

[rudolfbyker]

Use proper microdata on all content types managed by the rsc_library module. See http://schema.org/docs/gs.html

The following issues should probably be completed first:

• Use HTML for articles #12
• Move library articles with external links to a separate content type? #13
• Restructure content types #14

A broken implementation of this exists in:

• rsc_rc.module
• rsc_library.template.inc
• Use something like if (substr($field_name, strlen(RSC_LIBRARY_PREFIX), 12) === '_difficulty_') { … } to determine which field we are working with, regardless of the precise field name.
• Decide on a mapping between
  • Drupal fields and schema itemprops (e.g. rscl_summary => description)
  • Drupal content types and schema itemtypes (e.g. rsc_library_article => article)
• Add the relevant microdata attributes to the fields and nodes using preprocess functions and/or templates.

Apparently, items may be nested. Look into this, too.

[rudolfbyker]

A few remarks:

• Related discussion: http://stackoverflow.com/questions/10421334/microdata-schema-org-how-to-mix-together-schemas
• URL = canonical URL to the Drupal node page, not the url to the attached file (we are moving away from having most of our content in PDF files)
• If we have microdata, are things like RDF and description tags unnecessary? (I think so...)
• Related BUG: When sharing a page via the AddToAny share link (say, to Google+)
  • from the search results page: The wrong title and picture is used
  • from the node page: The wrong picture is used (presumably one from the sidebar...)

[rudolfbyker]

Test using Google's Structured Data Testing Tool.