Refering to the title, I think entity reference is potential and support reference not only to taxonomy but also others e.g. users, comment, content, etc.: It is good to have support for entity reference, just imho.

Members fund testing for the Drupal project. Drupal Association Learn more


linclark’s picture

Title: Support for Entity reference » Microdata support
Project: Microdata » Entity reference

Yeah, it's a top-10 field type defining module, so I agree. It shouldn't be hard to support, either.

I'm going to move this to the Entity Reference queue, and I have also listed the issue in the table of field formatter support issues.

klonos’s picture

Title: Microdata support » Microdata support for Entity Reference

...following. A less vague title for our dashboards ;)

Damien Tournoud’s picture

Can anyone describe what needs to happen?

linclark’s picture

I expect to have a student for GSOC who could take a look at what needs to happen for this field. If you like, you can postpone the issue until then.

silkogelman’s picture

There are several usecases this should solve (please correct or add to this)

Taking Recipe as an example.

Basic usecase:
A Recipe node may entityreference several ingredient nodes.
The recipe node page should output the ingredient node names as Microdata ingredients.

Advanced usecase:
A Recipe has nutritional information (outputted as Microdata and/or as information presented to the user)
The ingredients (ingredient nodes) have nutritionalinformation.
The nutritional information from the Recipe can be calculated by looking at the nutritionalinformation of the ingredients and the amount used of those ingredients.

SurajHo’s picture

For those still interested. I've uploaded a patch that enables microdata configuration for the Entity Reference field based on these instructions.