- Issue created by @fishfree
- πΊπΈUnited States jrockowitz Brooklyn, NY
As note in the README.md features, it 'allows dedicated 'Role' fields to be created for a Schema.org type.'
https://git.drupalcode.org/project/schemadotorg/-/tree/1.0.x/modules/sch...Right now, it is only configured for Podcasts.
The module may be deprecated and replaced with the schemadotorg_entity_reference_override.module which allows a Role value to be added to an entity reference.
- π¨π³China fishfree
I still cannot figure out, neither schemadotorg_entity_reference_override.
@jrockowitz Would you pls record some short videos to demo these confusing sub-modules? - πΊπΈUnited States jrockowitz Brooklyn, NY
I don't have time to start recording videos while the module is still in alpha releases. I am very open to improving the README.md files for each sub-module. We could add a 'Use case' for each module.
For example, the use case for the schemadotorg_entity_reference_override.module is to
Allow entity reference fields that relate a https://schema.org/Person to an https://schema.org/Organization to include a https://schema.org/Role with the entity reference using the Entity Reference _Override module.
A considerable contribution would be to define the use case for each sub-module.
- πΊπΈUnited States jrockowitz Brooklyn, NY
I just want to note here that I am tending to recommend using the Schema.org Blueprints Entity Reference Override module to add a https://schema.org/Role
to entity references. - π¨π³China fishfree
@jrockowitz Thank you! I think I can understand it now by your example.
- Status changed to Closed: works as designed
3 months ago 4:47pm 14 August 2024